a11y-pass
FreeCatch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
FreePublished on GitHub
my-new-skill
One sentence that describes WHEN to invoke this skill. Write it as a trigger phrase, not a summary — include the words a user would say ("fix bug", "add feature", "review diff"). The agent routes on this field.
The English summary is being prepared. Showing the original description.
See how to installFiles included (3)
- SKILL.md2.5 KB
- evidence/README.md527 B
- POST.md1.3 KB
SKILL.md (original)
Review the instructions the agent will receive before you install.
My New Skill
<!-- Anthropic-shaped SKILL.md template. Copy this folder to skills/<your-name>/ and edit. Keep the body under ~150 lines — long bodies are a context tax on every turn where this skill is loaded. Recommended structure: 1. One-paragraph statement of the failure mode this skill exists to prevent. 2. A short checklist or numbered procedure the agent should follow. 3. Red flags — the shortcuts an agent takes when it wants to skip this. 4. Evidence — a required before/after pair proving the skill actually changes behaviour. Ships in the sibling evidence/ folder. 5. (optional) `references/` sibling files with deeper material the skill lazy-loads only when needed. Do not include: - Marketing copy. - Duplicates of other skills (link, do not copy). - Project-specific rules — those belong in .claude/rules/. Frontmatter contract (validated by scripts/validate-skills + CI): - `name` — kebab-case, unique across the repo, matches the directory name. - `description` — one non-empty line, phrased as a trigger. - Anything else is optional and not currently enforced. -->Without this skill, the agent tends to <failure mode>. This skill enforces <the alternative>.
Steps
- <step>
- <step>
- <step>
Red flags — STOP
| Thought | Reality |
|---|---|
| "I've done this before, I don't need the checklist" | Skills evolve; re-read the current SKILL.md. |
| "This case is simple" | Simple cases become complex mid-task. |
| "The user didn't ask for this rigor" | The user asked for a working result. Rigor is how you get one. |
Evidence
Every skill ships with a real before/after pair proving it changes agent behaviour on a concrete task. Without this, the skill is a claim, not a tool.
evidence/before.md— a verbatim snippet of what the agent does on a representative task WITHOUT this skill loaded. Include the prompt, the agent's response, and what went wrong (or what got skipped).evidence/after.md— the same prompt with this skill loaded. Show the changed behaviour and why it is better.
If you cannot produce a before/after pair, the skill is not ready to ship. Land it as a draft in a branch, gather the evidence, then merge.
References
references/<topic>.md(only if needed; keep the body lightweight)
Reviews
No reviews yet. Tell others what you thought.
Comments
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
More skills from this repository
Before compaction Loopkit extracts decisions into claude-decisions.json (machine-readable). Read it alongside claude-progress.txt at session start — prose is for humans, JSON is for the loop.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Review a diff against the goal spec assuming the code is BROKEN. The reviewer that lives in the maker's head always agrees with itself — this pulls review into a hostile, separate pass. Invoke after every code change before marking work done.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
authz-check
FreeVerify that an endpoint checks ownership, not just authentication. Use on any handler that reads or mutates user data.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Find the exact commit that introduced a bug. Use when something worked before and broke, and you don't know which change did it.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026
Before picking new work, smoke-test the last "completed" feature. If it's broken, revert and re-open it before touching anything else. Kills the "looks shipped, isn't shipped" bug across sessions.
The English summary is being prepared. Showing the original description.
Archive228/loopkit755Updated Jul 15, 2026