metrics-dashboard
Tracks pipeline velocity, success rates, and cycle times. Use to view performance metrics, identify bottlenecks, and generate reports.
npx skills add majiayu000/claude-skill-registry --skill metrics-dashboard --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Metrics Dashboard Aggregates pipeline run data to track velocity, success rates, and identify improvement areas. ## Data Sources - `runs/*/status.json` - Phase timestamps, success/failure - `runs/*/ticket.json` - Ticket metadata - Git history - Commit and PR data - Notion - Ticket status transitions ## Workflow ### 1. Collect Run Data ```bash find runs/ -name "status.json" -type f | while read f; do jq -c '{ id: .ticketId, status: .status, started: .intakeAt, completed: .completedAt, phases: .phaseTimestamps }' "$f" done > /tmp/runs-data.jsonl ``` ### 2. Calculate Metrics **Cycle Time:** ```bash jq -s ' map(select(.completed != null)) | map(.cycleTime = ((.completed | fromdate) - (.started | fromdate)) / 3600) | { avgCycleTimeHours: (map(.cycleTime) | add / length), minCycleTimeHours: (map(.cycleTime) | min), maxCycleTimeHours: (map(.cycleTime) | max) } ' /tmp/runs-data.jsonl ``` **Success Rate:** ```bash jq -s '{ total: length, completed: (map(select(.status == "done")) | length), failed: (map(select(.status == "failed")) | length), inProgress: (map(select(.status | test("^(implementing|review|pr-created)$"))) | length) } | .successRate = (.completed / .total * 100)' /tmp/runs-d
- Data Sources
- Workflow
- 1. Collect Run Data
- 2. Calculate Metrics
- 3. Generate Dashboard
- 4. Save Dashboard
- Custom Queries
- Notion Integration (Optional)
- Output Artifacts
find runs/ -name "status.json" -type f | while read f; do
jq -c '{
done > /tmp/runs-data.jsonl
jq -s '
jq -s '{
echo "$DASHBOARD" > "$RUN_DIR/../metrics-$(date +%Y-%m-%d).md"
cat > runs/metrics-summary.json << EOF
Append to history
jq -c '{date: now | strftime("%Y-%m-%d"), metrics: .}' runs/metrics-summary.json >> runs/metrics-history.jsonl
Tickets by assigneeWhat does the metrics-dashboard skill do?
Tracks pipeline velocity, success rates, and cycle times. Use to view performance metrics, identify bottlenecks, and generate reports.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill metrics-dashboard --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 majiayu000/claude-skill-registry, a repository with 534 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.