stats

Summarize squad-mcp run history into an ANSI-rendered observability panel.

4|3|Updated May 2, 2026
One-click install
npx skills add https://github.com/ggemba/squad-mcp --skill stats-ggemba
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: stats
Source: https://github.com/ggemba/squad-mcp/tree/main/skills/stats
Command: npx skills add https://github.com/ggemba/squad-mcp --skill stats-ggemba

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you understand what happened during your squad-mcp runs by turning the workspace journal into a clear, at-a-glance observability dashboard.

Core Features & Use Cases

  • Run outcomes at a glance: shows APPROVED / CHANGES_REQUIRED / REJECTED mix with proportions.
  • Risk and score visibility: presents score distribution buckets (90–100, 80–89, 70–79, <70).
  • Trend over time: renders a compact sparkline for verdict counts across recent days.
  • Cost and token estimation: estimates token usage from character counts and highlights per-invocation and per-agent spend.
  • Operational health (deep mode): surfaces in_flight, completed, and aborted/synthesized-aborted states for troubleshooting.

Quick Start

Run /squad:stats --quick to view the last 7 days of trends, outcomes, and score distribution in a single panel.

Frequently Asked Questions about stats

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I view squad run history and score distribution in an ANSI dashboard?

You can view squad run history by summarizing the .squad/runs.jsonl journal into an ANSI-rendered observability panel that displays score distribution buckets, outcome proportions, and token estimates.

What is the best way to analyze token usage and cost breakdown for agent runs?

The best way to analyze token usage is to estimate costs from character counts in the run history, highlighting per-invocation and per-agent spend within a structured observability dashboard.

How do I troubleshoot in_flight or aborted states in my squad-mcp workspace?

You can troubleshoot operational health states by running a deep mode analysis that surfaces in_flight, completed, and aborted or synthesized-aborted statuses from your workspace run journal.

Can I generate a trend sparkline for run verdicts over the last 7 days?

Yes, you can generate a compact sparkline for verdict counts across recent days by aggregating run history data with the list_runs tool and rendering trend outcomes in the panel.

Does the stats observability panel work without external dependencies or components?

Yes, the observability panel operates in a strict read-only workflow with safe empty-state handling and requires no external dependencies or components to render your workspace run analytics.

Why does my run observability panel show an empty state during an operational review?

An empty state appears when the .squad/runs.jsonl file contains no recent run records to aggregate, which the read-only workflow handles safely without rendering incomplete analytics data.