Skip to content
Back to skills

Analytics

ASecurity

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

  • 8 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added May 28, 2026
ai-agentsbashnode

Works with

  • claude code

Security analysis

A100/100

Scanned May 28, 2026

npx -y skills add seokan-jeong/team-shinchan --skill analytics --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Analytics?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Analytics
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/seokan-jeong-analytics/badge)](https://www.skillsdirectory.com/skills/seokan-jeong-analytics)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: team-shinchan:analytics
description: Use when you need to analyze work tracker data for agent metrics or session stats.
user-invocable: false
---

# Analytics Skill

**Analyze work tracker events for observability insights.**

## Usage

```bash
/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

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

## 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:

```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

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

## 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

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.