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.
1---2name: productivity-score3description: >4 Calculate a productivity score using actual Agent Monitor metrics —5 session completion rates, cache efficiency (cache_read vs input),6 compaction pressure (baseline tokens), turn velocity (turn_count /7 total_turn_duration_ms), tool success ratio (PreToolUse vs PostToolUse),8 and the workflow intelligence API's complexity and effectiveness scores.9metadata:10 source: https://skillmd.com/skills/hoangsonww/productivity-score11---1213# Productivity Score1415Calculate a productivity scorecard from the Agent Monitor's real data.1617## Input1819The user provides: **$ARGUMENTS**2021Options: "today", "this week", "last 30 days", a session ID, or "compare" for period comparison.2223## Data Sources2425| Endpoint | Returns |26|----------|---------|27| `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 |28| `GET /api/sessions?limit=100` | Sessions with metadata JSON: `thinking_blocks`, `turn_count`, `total_turn_duration_ms`, `usage_extras` (service_tier, speed, inference_geo) |29| `GET /api/pricing/cost` | Total cost with per-model breakdown |30| `GET /api/workflows/{sessionId}` | 11 workflow datasets: stats, orchestration, toolFlow, effectiveness, patterns, modelDelegation, errorPropagation, concurrency, complexity, compaction, cooccurrence |3132## Score Components (each 0–100)3334### 1. Completion Rate (20% weight)35From `sessions_by_status`:36- `completed / (completed + error + abandoned) × 100`37- Bonus for high completed-to-active ratio38- Penalty for abandoned sessions (wasted work)3940### 2. Token Efficiency (20% weight)41From analytics `tokens` (baselines are pre-summed into totals):42- **Cache hit rate**: `total_cache_read / (total_cache_read + total_input) × 100`43 - Above 60% = excellent, below 30% = poor44- **Output concentration**: `total_output / total_input` — 0.3–0.8 is balanced4546### 3. Tool Effectiveness (20% weight)47From `event_types`:48- **Success ratio**: Count `PostToolUse` / Count `PreToolUse` — should be ~1.0; gap = tool failures49- **API error rate**: Count `APIError` / total events — should be near 050- From workflow `effectiveness` data: subagent completion rates, task success per type5152### 4. Velocity (20% weight)53From session metadata:54- **Turns per session**: average `turn_count` across sessions55- **Turn speed**: average `total_turn_duration_ms / turn_count` — lower = faster56- **Events per session**: from `avg_events_per_session` in analytics overview57- **Thinking depth**: average `thinking_blocks` — more thinking = more thorough (neutral metric)5859### 5. Cost Efficiency (20% weight)60From pricing:61- **Cost per completed session**: `total_cost / completed_sessions`62- **Cost trend**: comparing current period to previous (decreasing = improving)63- **Model optimization**: sessions using expensive models (Opus) for tasks subagents handle with Haiku/Sonnet6465## Overall Score6667Weighted sum → letter grade:68- **A+** (95-100), **A** (90-94), **B+** (85-89), **B** (80-84), **C+** (75-79), **C** (70-74), **D** (60-69), **F** (<60)6970## Output Format7172```73═══════════════════════════════════════74 PRODUCTIVITY SCORE: 87/100 (B+)75═══════════════════════════════════════76 Completion Rate ████████░░ 80/10077 Token Efficiency █████████░ 92/10078 Tool Effectiveness████████░░ 85/10079 Velocity █████████░ 88/10080 Cost Efficiency █████████░ 90/10081═══════════════════════════════════════82```8384Then: top 3 strengths, top 3 improvement areas with actionable steps, and period comparison if available.