skill-hoangsonww-claude-code-agent-monitor-daily-standup · by Install
$ agentstack add skill-hoangsonww-claude-code-agent-monitor-daily-standup ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Links to your public security report.[](https://agentstack.voostack.com/security/report/skill-hoangsonww-claude-code-agent-monitor-daily-standup) Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
errororabandonedstatus - 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: hoangsonww
- Source: hoangsonww/Claude-Code-Agent-Monitor
- License: MIT
- Homepage: https://hoangsonww.github.io/Claude-Code-Agent-Monitor/
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.