SkillAgentSearch skills...

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

Install / Use

npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill productivity-score

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

85/100

Category

Automation

Supported Platforms

Universal

Our assessment of productivity-score

productivity-score scores 85/100 on our quality scale, 1959th of 2,758 Automation skills we index.

Its SKILL.md is 3.5 KB long, well organised into 11 sections with 1 code example: a solid amount of guidance for an agent.

With 1,015 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
17/20
Description
15/15
Adoption
13/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so productivity-score is actively maintained.
  • Our last check on 2026-11-05 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-07. Automated pattern scan on 2026-10-07. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

productivity-score compared with similar skills

All 4 of these similar skills score higher than productivity-score; compare them before choosing.

SkillScoreStarsUpdatedFormat
productivity-score (this skill)by hoangsonww851.0k2mo agoSKILL.md
Agent-Reachby Panniantong100114.0ktodayCLAUDE.md
rufloby ruvnet10082.3ktodayCLAUDE.md
headroomby headroomlabs-ai10080.5ktodayCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10040.6k12d agoCLAUDE.md

Frequently asked questions

How do I install productivity-score?
Run npx skills add hoangsonww/Claude-Code-Agent-Monitor --skill productivity-score. The install tabs above show the steps for each supported agent.
Which AI agents does productivity-score work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is productivity-score safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is productivity-score still maintained?
The repository was last updated about 2 months ago, so productivity-score is actively maintained.

name: productivity-score description: > 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.

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 ratio
  • Penalty for abandoned sessions (wasted work)

2. Token Efficiency (20% weight)

From analytics tokens (baselines are pre-summed into totals):

  • Cache hit rate: total_cache_read / (total_cache_read + total_input) × 100
    • Above 60% = excellent, below 30% = poor
  • Output concentration: total_output / total_input — 0.3–0.8 is balanced

3. Tool Effectiveness (20% weight)

From event_types:

  • Success ratio: Count PostToolUse / Count PreToolUse — should be ~1.0; gap = tool failures
  • API error rate: Count APIError / total events — should be near 0
  • From workflow effectiveness data: subagent completion rates, task success per type

4. Velocity (20% weight)

From session metadata:

  • Turns per session: average turn_count across sessions
  • Turn speed: average total_turn_duration_ms / turn_count — lower = faster
  • Events per session: from avg_events_per_session in analytics overview
  • Thinking depth: average thinking_blocks — more thinking = more thorough (neutral metric)

5. Cost Efficiency (20% weight)

From pricing:

  • Cost per completed session: total_cost / completed_sessions
  • Cost trend: comparing current period to previous (decreasing = improving)
  • Model optimization: sessions using expensive models (Opus) for tasks subagents handle with Haiku/Sonnet

Overall Score

Weighted sum → letter grade:

  • A+ (95-100), A (90-94), B+ (85-89), B (80-84), C+ (75-79), C (70-74), D (60-69), F (<60)

Output Format

═══════════════════════════════════════
  PRODUCTIVITY SCORE: 87/100 (B+)
═══════════════════════════════════════
  Completion Rate   ████████░░  80/100
  Token Efficiency  █████████░  92/100
  Tool Effectiveness████████░░  85/100
  Velocity          █████████░  88/100
  Cost Efficiency   █████████░  90/100
═══════════════════════════════════════

Then: top 3 strengths, top 3 improvement areas with actionable steps, and period comparison if available.

Related Skills

View on GitHub
GitHub Stars1.0k
CategoryAutomation
Updated2mo ago
Forks238

Languages

JavaScript

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions