mcpbeat

Daily Standup

hoangsonww/daily-standup

> Generate a daily standup summary from recent Claude Code sessions — completed work grouped by project (cwd), session costs from the pricing engine, tool invocations, error/compaction/APIError events, and turn velocity metrics from session metadata (turn_count, total_turn_duration_ms).

537 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
867
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/hoangsonww/Claude-Code-Agent-Monitor --skill daily-standup

The instruction itself

8 sections, as written by the author

Daily Standup

Generate a daily standup report from Claude Code Agent Monitor data.

Input

The user provides: $ARGUMENTS

This may be:

  • "today" or empty (default: last 24 hours)
  • "yesterday" for the previous day
  • A specific date: "2025-04-10"

Procedure

  • Fetch recent session data from http://localhost:4820:
  • GET /api/sessions?limit=50 (default sort: most recently updated first)
  • Filter sessions that started within the target day
  • For each matching session: GET /api/events?session_id={session_id}
  • Compile standup sections:

✅ What I accomplished

  • List each completed session with:
  • Brief description (from session name or first tool's context)
  • Working directory (project context)
  • Key tools used and outcomes
  • Duration and model used
  • Group by project/working directory if multiple

⚠️ Issues encountered

  • Sessions that ended in error or abandoned status
  • Tools that failed (from error events)
  • Compaction events (hit context limits)
  • Unusually long sessions (>2x average duration)

📋 Key metrics

  • Total sessions: N
  • Total time spent: X hours Y minutes
  • Tools invoked: N (top 3 listed)
  • Estimated cost: $X.XX
  • Completion rate: N%

🔮 Suggested focus areas

  • Based on incomplete/error sessions, suggest what to revisit
  • Based on tool patterns, suggest workflow improvements
  • Format for standup:
  • Keep it concise — aim for a 2-minute read
  • Lead with accomplishments
  • Be honest about blockers
  • Make metrics scannable

Output Format

Present as a clean standup report with emoji section headers, bullet points for items, and a compact metrics table. Add a one-line summary at the top suitable for pasting into Slack or a team channel.

How to use it

Copy the folder

Take hoangsonww/daily-standup from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.