cyberneticlibrary

Calculate team productivity scorecard

productivity-scoreskillsetup L2364
hoangsonww/Claude-Code-Agent-Monitor
What it does

Calculate productivity scorecard from Agent Monitor with 5 component scoring

Best for

Monthly review of system health and team performance when you want a single 0-100 number with component breakdown and trend comparison.

Inputs
  • · Time period: 'today', 'this week', 'last 30 days'
  • · Optional: session ID for session-specific metrics
  • · Optional: 'compare' for period comparison
Outputs
  • · Overall productivity score (0-100 with letter grade A+/A/B+/B/C+/C/D/F)
  • · Five component scores (Completion Rate, Token Efficiency, Tool Effectiveness, Velocity, Cost Efficiency) each 0-100
  • · Top 3 strengths and top 3 improvement areas with actionable steps
  • · Period comparison if available
Requires
  • · Agent Monitor API: /api/analytics, /api/sessions, /api/pricing/cost, /api/workflows/{sessionId}
Preconditions
  • · Agent Monitor running with at least 7 days of data for meaningful score
  • · Pricing rules configured (for cost efficiency component)
  • · Sessions must have status field (completed, error, abandoned, active)
Failure modes
  • · Low completion rate (< 70%) indicates workflow design issue, not just productivity
  • · Cache hit rate only meaningful if cache is actually being used — young systems show 0% as normal
  • · Tool effectiveness metric depends on tool classification (some tools always succeed, some always fail)
  • · Cost efficiency can be gamed by using cheaper models on complex tasks (metric doesn't account for quality)
Trust signals
  • · Five weighted components (20% each): Completion Rate, Token Efficiency, Tool Effectiveness, Velocity, Cost Efficiency
  • · Completion rate = completed / (completed + error + abandoned) × 100
  • · Cache hit rate = total_cache_read / (total_cache_read + total_input) × 100
  • · Letter grade mapping: A+ (95-100), A (90-94), B+ (85-89), B (80-84), C+ (75-79), C (70-74), D (60-69), F (<60)
  • · Visual progress bars for each component
  • · Actionable improvement areas with specific steps per component