a11y-pass
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing.
$ npx -y skills add Archive228/loopkit --skill readme-audit --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/readme-auditContext preview
The summary Claude sees to decide when to auto-load this skill.
Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing.
name: readme-audit description: Check whether a README actually lets a stranger run the project. Use on any repo's README before publishing. when_to_use: publishing a repo, onboarding docs, "is the README good"
A README's only job: a stranger clones it and gets to "it works" without asking you. Check, in order: 1. **One sentence** on what it is and who it's for — above the fold. 2. **Install** — copy-paste commands that actually work on a clean machine. Test them mentally step by step. 3. **Run / quickstart** — the smallest end-to-end example. 4. **Config** — required env vars, where secrets go. 5. **No rot** — does it reference files/commands/flags that still exist? Stale README is worse than none. Cut: long philosophy, badges nobody reads, TODO sections. Output: the specific gaps + the fix.
33 battle-tested skills + minimal .claude harness for any coding agent (Claude Code, Cursor, Codex, Gemini CLI).
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt…
Review a diff against the goal spec assuming the code is BROKEN. The reviewer
Verify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything…