agentsclimarketplace

Analytics

Skill seokan-jeong/team-shinchan/skills/analytics

Use when you need to analyze work tracker data for agent metrics or session stats.From its SKILL.md

Install
npx -y skills add seokan-jeong/team-shinchan --skill analytics

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.7 KB, as published. Nobody here has run it

Analytics Skill

Analyze work tracker events for observability insights.

Usage

/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

Arguments

ArgDefaultDescription
--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 tablejsonOutput as text table instead of JSON

Process

Step 1: Locate Tracker File

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.

Step 2: Run Analytics Script

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
  • Default (no args) → --format table

Step 3: Display Results

  • For --format table or default: display the text table output directly
  • For JSON output: format and display key sections with headers

Step 4: Interpret Results

After displaying raw output, provide a brief interpretation:

  • Highlight busiest agents
  • Note any agents with low success rates
  • Summarize delegation patterns
  • Flag anomalies (e.g. agents with 0 completions)

Metrics Computed

MetricDescription
Agent call countHow many times each agent was invoked
Avg durationAverage time from agent_start to agent_done
Success rateRatio of agent_done to agent_start
Session statsEvents, file changes, delegations per session
Event distributionPercentage breakdown of event types
Delegation graphWhich agent delegated to which, with counts

Important

  • Analytics script: src/analytics.js (Node.js, built-in modules only)
  • Data source: .shinchan-docs/work-tracker.jsonl
  • Trace IDs: generated per user prompt via trace-init hook

Keep looking

Skills are one crate of 610,677. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.