session-summary
Generate a comprehensive session summary
Best use case
session-summary is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate a comprehensive session summary
Teams using session-summary 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-summary/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How session-summary Compares
| Feature / Agent | session-summary | 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?
Generate a comprehensive session summary
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
Generate a comprehensive session summary: $ARGUMENTS
Follow these steps:
1. **Create session summary file**:
- Generate filename as `session_{slug}_{timestamp}.md` where:
- `{slug}` is a short description of the session topic
- `{timestamp}` is current date/time in YYYY-MM-DD-HHMMSS format
- If $ARGUMENTS provides a specific filename or slug, use that instead
2. **Gather session information**:
- Review the conversation history and actions taken
- Identify key accomplishments and deliverables
- Note any challenges encountered and how they were resolved
- Document tools and commands used during the session
3. **Analyze session metrics**:
- Count the total number of conversation turns
- Estimate the total cost of the session (if available)
- Assess the efficiency of the workflow
- Identify any performance bottlenecks or delays
4. **Document the session summary with**:
- **Session Overview**: Brief description of the session purpose and goals
- **Key Actions**: Bullet-point list of major actions taken
- **Deliverables**: Files created, modified, or analyzed
- **Tools Used**: List of Claude Code tools and external commands used
- **Metrics**:
- Total conversation turns
- Session duration (if available)
- Estimated cost
- **Efficiency Insights**: What went well and what could be improved
- **Process Improvements**: Suggestions for future sessions
- **Interesting Observations**: Notable patterns, discoveries, or highlights
5. **Save and organize**:
- Save the summary in the current working directory
- Include links to any files created or modified during the session
- Add timestamps for when major milestones were achieved
Remember: Focus on actionable insights and concrete outcomes rather than just listing activities.Related Skills
session-metrics
View detailed metrics about the current session
session-info
Display current session information and context
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.