session-info
Display current session information and context
Best use case
session-info is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Display current session information and context
Teams using session-info should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/session-info/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How session-info Compares
| Feature / Agent | session-info | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Display current session information and context
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Session Info Command
Display current session context including git status, recent work, and development context.
## What to Display
Immediately show:
1. **Current Session State**
- Session ID
- Current branch
- Working directory status
2. **Git Status**
- Current branch
- Uncommitted changes count
- Recent commits (last 3)
3. **Context Files** (if they exist)
- `{{HOME_TOOL_DIR}}/CLAUDE.md` summary
- `{{HOME_TOOL_DIR}}/TODO.md` items
- `TODO.md` items
4. **Recent GitHub Issues** (if `gh` available)
- Last 5 open issues
## Format
Present as a clean, readable summary banner:
```
+============================================================+
| SESSION INFORMATION |
+============================================================+
Location: /path/to/project
Branch: main
Changes: 3 uncommitted files
Recent Work:
- feat: add session start hook improvements
- fix: combine git status and context output
- docs: update CLAUDE.md with comment directives
Active TODOs:
[ ] Fix session start visibility
[ ] Test hook output format
[x] Update hook logic
Recent Issues:
#123 - Session start hook not displaying
#122 - Improve git status formatting
```
Be concise but informative.Related Skills
session-summary
Generate a comprehensive session summary
session-metrics
View detailed metrics about the current session
recover-sessions
Recover crashed or orphaned agent sessions
workflow
Guide through structured delivery workflow with plan, implement, validate phases
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
validate
Verify implementation against specifications
ui-ux-pro-max
UI/UX design intelligence. 67 styles, 96 palettes, 57 font pairings, 25 charts, 13 stacks (React, Next.js, Vue, Svelte, Astro, Nuxt, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
tui-style-guide
TUI style guide for consistent terminal interface design
token-usage
Show Claude Code token usage across sessions — daily, weekly, per-project, and per-session breakdowns. Parses {{HOME_TOOL_DIR}}/projects/**/*.jsonl for consumption data. Use when the user asks about token usage, costs, how many tokens were used, session statistics, or wants a usage report.
tmux-status
Show status of all tmux sessions including dev environments, spawned agents, and running processes
tmux-monitor
Monitor and report status of all tmux sessions including dev environments, spawned agents, and running processes. Uses tmuxwatch for enhanced visibility.
tmux-message
Reliable peer-to-peer message delivery to other Claude Code instances via tmux send-keys. Use as a fallback when claude-peers MCP send_message fails to surface in the receiver's inbox (delivered server-side but receiver never picks it up — observed behaviour). Also use when sending a directive to a known Claude Code TUI session by tmux session name or fuzzy hint, or when injecting a multi-line directive into a peer's prompt and submitting it. Trigger phrases — "claude-peers fallback", "tmux send-keys", "send to peer via tmux", "inject directive", "deliver to nanoclaw/hermes peer", "peer message". Tmux-only — won't reach peers running outside tmux.