wyattowalsh/agents

skill-quality-dashboard

>- Aggregate generated maintainer reports into a skill-quality summary. Use when reviewing docs, link, and eval health. NOT for editing report sources.

First seen Jul 5, 2026

Installation

$ npx skills add wyattowalsh/agents --skill skill-quality-dashboard

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from wyattowalsh/agents · top by installs.

npx skills add wyattowalsh/agents

Browse all from wyattowalsh/agents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch main
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.0.0
LicenseMIT
More metadata
author
wyattowalsh
version
1.0.0

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,506 B
  • docs SUMMARY.md 179 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 35 installs

SKILL.md

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

$ARGUMENTS Action
Empty Default dashboard summary
--format json Machine-readable aggregate
reports List 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.