mcpField
S
skill-quality-dashboard

skill-quality-dashboard

github.com/wyattowalshTesting & quality535 installsUpdated 8w ago
Repository

About skill-quality-dashboard

A maintainer skill that aggregates committed JSON reports about skill and documentation quality gates into a dashboard. It is read-only and does not regenerate reports, helping teams review report counts and quality signals.

Key features

  1. 01Aggregate committed report files
  2. 02Summarize quality-gate reports
  3. 03List registered reports and counts
  4. 04Offer machine-readable output
  5. 05Read-only report handling

Use cases

  1. 01Review repository quality reports
  2. 02Check registered report files and counts
  3. 03Export an aggregate for automation

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/wyattowalsh/agents --skill skill-quality-dashboard

After installing, type/skill-quality-dashboardin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

evals/
evals.json
scripts/
aggregate_reports.py
check.py
scripts/asset_toolkit/
validate_hooks.py

Details

From the project README

Skill Quality Dashboard

Summarize maintainer ops reports for skill and docs quality gates.

Scope: Read-only aggregation of committed docs/public/generated-reports/*.json. Does not regenerate reports.

Dispatch

$ARGUMENTSAction
EmptyDefault dashboard summary
--format jsonMachine-readable aggregate
reportsList registered report files and key counts

Workflow

uv run python skills/skill-quality-dashboard/scripts/aggregate_reports.py
uv run python skills/skill-quality-dashboard/scripts/aggregate_reports.py --format json

Regenerate upstream reports with the repo docs-generation pipeline — do not hand-edit JSON.

Validation Contract

uv run python skills/skill-quality-dashboard/scripts/check.py

Critical Rules

  1. Treat generated report JSON as evidence, not authority to bypass validate gates.
  2. Never hand-edit docs/public/generated-reports/*.json.
  3. Pair dashboard output with skill-lifecycle-manager for per-skill readiness.
  4. Route broken-link remediation to docs-steward.
  5. Do not claim reports are fresh without checking generation timestamps when present.

Comments

Markdown supported