Receber por email
← Voltar para o catálogo

Claude-Code-Agent-Monitor

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).

478estrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add hoangsonww/Claude-Code-Agent-Monitor

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/claude-code-agent-monitor-mpsjmw29/svg)](https://www.skillteca.com.br/skills/claude-code-agent-monitor-mpsjmw29)

Alerta por categoria

Receba novas skills de Design e Frontend toda segunda

1 email curto, só com as skills novas de Design e Frontend. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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:
  2. GET /api/sessions?limit=50 (default sort: most recently updated first)
  3. Filter sessions that started within the target day
  4. For each matching session: GET /api/events?session_id={session_id}
  1. 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
  1. Format for standup:
  2. Keep it concise — aim for a 2-minute read
  3. Lead with accomplishments
  4. Be honest about blockers
  5. 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.

Compartilhar X LinkedIn