skill-improve-qualitylisted

Audit and improve the quality of a single-file HTML explainer page (typically `index.html`) in the current repo without changing its purpose. Use whenever the user wants to QA, audit, fact-check, polish, sharpen, review, critique, validate, tighten, or improve an explainer, primer, one-pager, landing page, deep-dive, or single-file HTML — even when they don't use the exact phrase "improve quality". Triggers include "check this page", "is this accurate", "review the prose", "polish this", "audit this index.html", "fact-check this", "is the content correct", "is this clear enough", "sharpen this writing", "tighten this page", "QA the page", "is this professional", "is this any good", and "/skill-improve-quality". Skip when there is no HTML file to audit, when the user wants new content written rather than checked, or when they want visual-only feedback.
jamesbuckett/skill-improve-quality · ★ 0 · Data & Documents · score 72

Install: claude install-skill jamesbuckett/skill-improve-quality

# skill-improve-quality ## What this skill does Takes a finished `index.html` page in the current repo and improves its quality across four dimensions: 1. **Factual correctness** — every load-bearing claim (regulatory clause, version number, date, statistic, named entity) is verified against authoritative web sources. 2. **Clarity & comprehension** — undefined jargon, ambiguous pronouns, runaway sentences, dense paragraphs the reader can't parse on first pass. 3. **Professional prose** — AI-slop tells, marketing voice, tense and voice inconsistency, hedge phrases, tic words. 4. **Structural quality** — adherence to the `skill-style-guide` (visual chassis) and `skill-build-educational-site` (content architecture) patterns; failure modes those skills are explicitly trying to prevent. The output is a single inline report grouped by severity, then an interactive pass where you approve or reject each fix. Approved fixes are applied via `Edit` to `index.html`. Nothing is changed without consent. ## When to use this skill This skill exists because the user produces educational pages with two sibling skills (`skill-style-guide` and `skill-build-educational-site`) and wants a deliberate QA pass afterwards — separate from authoring, with its own discipline. Don't fold the checks into authoring; the page is too close to the author at that point. Treat this skill as a fresh pair of eyes. Use it when: - The user just finished a page and wants to ship it. - The user inherited an `in