sprint-summary
Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turn_count, turn_duration_ms), and tool diversity across the sprint.
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill sprint-summary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Sprint Summary Generate a sprint summary from Claude Code Agent Monitor data. ## Input The user provides: **$ARGUMENTS** This may be: - A sprint duration: "last 2 weeks", "last 10 days" - A date range: "2025-03-31 to 2025-04-13" - "current sprint" (default: last 14 days) ## Procedure 1. **Fetch sprint data** from `http://localhost:4820`: - `GET /api/sessions?limit=500` — all sessions in range (default sort: most recently updated first) - `GET /api/analytics` — aggregated metrics - `GET /api/pricing/cost` — total costs - For high-value sessions: `GET /api/events?session_id={id}` — event details 2. **Compile sprint summary**: ### 🎯 Sprint Overview - Sprint period: [start] to [end] - Total sessions: N (completed: N, errored: N, abandoned: N) - Total development hours with Claude Code: N - Total cost: $X.XX - Overall completion rate: N% ### 📦 Deliverables Group sessions by working directory (project): - **Project A** (`/path/to/project`) - N sessions, N hours, key activities - **Project B** (`/path/to/other`) - N sessions, N hours, key activities ### 📊 Velocity Metrics | Metric | Sprint | Previous Sprint | Trend | |--------|--------|-----------------|-------| | Sessions/day | N |
- Input
- Procedure
- Output Format
What does the sprint-summary skill do?
Summarize a sprint's worth of Claude Code activity — sessions grouped by project (cwd), per-model cost breakdown, token efficiency (cache hit rate, compaction baselines), subagent effectiveness from workflow API, velocity metrics (turn_count, turn_duration_ms), and tool diversity across the sprint.
How do I install it?
Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill sprint-summary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.