Menú
Use when you need to analyze work tracker data for agent metrics or session stats.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Use when you have a large-scale, multi-phase project requiring orchestrated execution.
Use when you need persistent looping until a task is fully complete.
Deterministic adversarial code review for high-stakes scope — independent per-dimension review, a non-skippable per-finding refutation, completeness + interaction critics, and a deterministic 3-lens rubric judge panel. Opt-in main-loop Workflow tier.
Use when the user wants to review accumulated skill feedback, verdict trends, or improvement candidates collected during Stage 4 retrospectives. Trigger on "show skill feedback", "스킬 피드백 보여줘", or finding which skills need /writing-skills work.
Deterministic competitive code tournament — N builders independently solve one task and return patches, an Action-Kamen judge scores them head-to-head, the winner is picked by score and applied. Opt-in main-loop Workflow tier.
Deterministic adversarial debate for high-stakes or irreversible decisions — mandatory refutation plus a scored judge panel. Opt-in main-loop Workflow tier.
| name | team-shinchan:analytics |
| description | Use when you need to analyze work tracker data for agent metrics or session stats. |
| user-invocable | false |
Analyze work tracker events for observability insights.
/team-shinchan:analytics # Current session summary
/team-shinchan:analytics --report full # Full analytics report
/team-shinchan:analytics --agent bo # Single agent detail
/team-shinchan:analytics --trace trace-xxx # Trace timeline
/team-shinchan:analytics --period 7d # Last 7 days only
| Arg | Default | Description |
|---|---|---|
--report full | (session) | Generate full analytics report |
--agent {name} | (all) | Detail for a single agent |
--trace {id} | (none) | Timeline for a specific trace ID |
--period {N}d | (all) | Filter events to the last N days |
--format table | json | Output as text table instead of JSON |
Use .shinchan-docs/work-tracker.jsonl as the data source.
If file does not exist:
No work tracker log found.
Events will be recorded automatically during Claude Code sessions.
Execute the analytics script via Bash:
node "${CLAUDE_PLUGIN_ROOT}/src/analytics.js" .shinchan-docs/work-tracker.jsonl [options]
Map user arguments to script flags:
--report full → no extra flags (full report is default)--agent <name> → --agent <name>--trace <id> → --trace <id>--period <N>d → --period <N>d--format table--format table or default: display the text table output directlyAfter displaying raw output, provide a brief interpretation:
| Metric | Description |
|---|---|
| Agent call count | How many times each agent was invoked |
| Avg duration | Average time from agent_start to agent_done |
| Success rate | Ratio of agent_done to agent_start |
| Session stats | Events, file changes, delegations per session |
| Event distribution | Percentage breakdown of event types |
| Delegation graph | Which agent delegated to which, with counts |
src/analytics.js (Node.js, built-in modules only).shinchan-docs/work-tracker.jsonltrace-init hook