Skip to content
Development
Skill

/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,

From plugin
claude-code-agent-monitor
1k75 skills21 agents33 commands1 MCP
Install
$ npx -y skills add hoangsonww/Claude-Code-Agent-Monitor --skill daily-standup --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/daily-standup

Context preview

The summary Claude sees to decide when to auto-load this skill.

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,

SKILL.md

daily-standup.SKILL.md
name: daily-standup
description: >
  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).

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

1. **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}`

2. **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

3. **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.

Read more
Ships withclaude-code-agent-monitor

🚀 A real-time monitoring dashboard for Claude Code & Codex, built with SQLite3, Node.js, Express, React, Vite, TailwindCSS, & WebSockets. It tracks sessions, agent activity, tool usage, and subagent orchestration, providing live analytics, a Kanban status board, status notifications, a cute buddy, & an interactive web UI/MacOS/Windows native app.

Get the whole plugin

Other skills on claude-code-agent-monitor.