Agent skill · Backend & API

productivity-score

Calculate a productivity score using actual Agent Monitor metrics — session completion rates, cache efficiency (cache_read vs input), compaction pressure (baseline tokens), turn velocity (turn_count / total_turn_duration_ms), tool success ratio (PreToolUse vs PostToolUse), and the workflow intelligence API's complexity and effectiveness scores.

hoangsonwwgithub.com/hoangsonwwGitHub ↗
claude-codeMIT
Install
npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill productivity-score --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: plugins/ccam-analytics/skills/productivity-score/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 869
Language: TypeScript

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Productivity Score Calculate a productivity scorecard from the Agent Monitor's real data. ## Input The user provides: **$ARGUMENTS** Options: "today", "this week", "last 30 days", a session ID, or "compare" for period comparison. ## Data Sources | Endpoint | Returns | |----------|---------| | `GET /api/analytics` | Token totals (`total_input`, `total_output`, `total_cache_read`, `total_cache_write` — baselines pre-summed), tool_usage top 20, daily_events/sessions, event_types, sessions_by_status, agents_by_status, avg_events_per_session, total_subagents | | `GET /api/sessions?limit=100` | Sessions with metadata JSON: `thinking_blocks`, `turn_count`, `total_turn_duration_ms`, `usage_extras` (service_tier, speed, inference_geo) | | `GET /api/pricing/cost` | Total cost with per-model breakdown | | `GET /api/workflows/{sessionId}` | 11 workflow datasets: stats, orchestration, toolFlow, effectiveness, patterns, modelDelegation, errorPropagation, concurrency, complexity, compaction, cooccurrence | ## Score Components (each 0–100) ### 1. Completion Rate (20% weight) From `sessions_by_status`: - `completed / (completed + error + abandoned) × 100` - Bonus for high completed-to-active rati

What's inside
Steps it walks through
  1. Input
  2. Data Sources
  3. Score Components (each 0–100)
  4. 1. Completion Rate (20% weight)
  5. 2. Token Efficiency (20% weight)
  6. 3. Tool Effectiveness (20% weight)
  7. 4. Velocity (20% weight)
  8. 5. Cost Efficiency (20% weight)
  9. Overall Score
  10. Output Format
More from Claude-Code-Agent-Monitor
All skills →
About this skill
What does the productivity-score skill do?

Calculate a productivity score using actual Agent Monitor metrics — session completion rates, cache efficiency (cache_read vs input), compaction pressure (baseline tokens), turn velocity (turn_count / total_turn_duration_ms), tool success ratio (PreToolUse vs PostToolUse), and the workflow intelligence API's complexity and effectiveness scores.

How do I install it?

Run `npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill productivity-score --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From hoangsonww/Claude-Code-Agent-Monitor, a repository with 869 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going