daily-standup
The daily-standup skill generates a concise standup report from Claude Code Agent Monitor session data by fetching recent sessions from a local API, filtering by date (today, yesterday, or a specific date), and compiling accomplishments, issues, metrics, and suggested focus areas into a formatted report suitable for team communication. Use this skill to summarize daily coding agent activity, track productivity across projects, identify blockers, and communicate progress to team members in under two minutes.
git clone --depth 1 https://github.com/hoangsonww/Claude-Code-Agent-Monitor /tmp/daily-standup && cp -r /tmp/daily-standup/plugins/ccam-productivity/skills/daily-standup ~/.claude/skills/daily-standupSKILL.md
# 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.Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Understand this repository quickly before making changes. Use for architecture discovery, ownership mapping, command selection, and initial implementation planning.
Review backend route and hook logic for regressions, data integrity risks, and missing tests.
Review React UI changes for behavior regressions, state consistency, and UX breakage.
Review MCP server changes for tool safety, schema quality, and host integration correctness.
Debug production-like issues in this repository with disciplined evidence gathering. Use when fixing failing workflows, regressions, flaky behavior, or data inconsistencies across hooks, API, DB, websocket, and UI.
Operate and maintain the local MCP server for this project. Use when creating MCP host config, troubleshooting tool connectivity, modifying tool domains, or adjusting safety policy flags.