progress-dashboard SKILL.md skillA
progress-dashboard from ymd38/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add ymd38/dev-skills/progress-dashboard@git:20260919.20d77cbPins git:20260919.20d77cb in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- ymd38/dev-skills
- Path
skills/progress-dashboard/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260919.20d77cb, committed Sep 19, 2026
- First version recorded
- Apr 11, 2026
- Size
- 4,930 bytes
- Repository stars
- 7
- License
- MIT
Generate an interactive HTML dashboard that visualizes improvement progress from software-evaluation and vulnerability-scan reports over time. Reads JSON summary files from docs/evaluation/ and docs/security-audit/, then produces a single self-contained HTML file with charts and trend analysis. Triggers on requests like "generate dashboard", "show progress", "visualize improvements", "/maruda:progress-dashboard", or when asked to see quality or security trends.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Role: Engineering Metrics Dashboard Generator You generate a self-contained, interactive HTML dashboard that visualizes code quality and security improvement progress over time. The dashboard reads JSON summary files produced by the `software-evaluation` and `vulnerability-scan` skills. --- ## Phase 1: Data Collection ### 1.1 Locate JSON Summary Files Scan for JSON files in: - `docs/evaluation/*.json` — software evaluation summaries - `docs/security-audit/*.json` — vulnerability scan summaries If no JSON files exist, inform the user that they need to run `software-evaluation` and/or `vulnerability-scan` first with JSON output enabled. ### 1.2 Parse & Validate For each JSON file, verify: - `schemaVersion` is `"1.0"` - `type` is either `"software-evaluation"` or `"vulnerability-scan"` - `date` is a valid ISO date string - Required fields are present (scores for evaluation, findings for vulnerability) Sort all entries by `date` ascending. Group by `target` if multiple targets exist. --- ## Phase 2: Dashboard Generation ### 2.1 Technology Generate a **single self-contained HTML file** with: - **Chart.js** via CDN (`https://cdn.jsdelivr.net/npm/chart.js`) for charts …
Read the whole file at its exact version.
How to install
mdr add ymd38/dev-skills/progress-dashboard@sha256:4b608a2bbfa6392cThe line at the top of this page pins the label git:20260919.20d77cb, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_whderzned4eq57sx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Apr 11, 2026 and Sep 19, 2026, about one every 161 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260919.20d77cb latest | 2026-09-19 | 20d77cb | 4,930 B | A | view · diff |
| git:20260411.6bfab75 | 2026-04-11 | 6bfab75 | 4,923 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4930 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
ymd38/dev-skills · 7 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_whderzned4eq57sx GET https://markdownregistry.com/api/v1/resolve?ref=ymd38/dev-skills/progress-dashboard GET https://markdownregistry.com/api/v1/blob/4b608a2bbfa6392c570e28cac3e7675f98d38178831ccf7fd116e21cbbbf0a7a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from ymd38/dev-skills
Every file in ymd38/dev-skills