a11y-pass
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
$ npx -y skills add Archive228/loopkit --skill read-the-trace --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/read-the-traceContext preview
The summary Claude sees to decide when to auto-load this skill.
Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception.
name: read-the-trace description: Extract the actual cause from a stack trace instead of pattern-matching the error type. Use on any crash or exception. when_to_use: a stack trace, an exception, "TypeError/NullPointer/undefined", a crash log
LLMs love to see "TypeError" and generate a generic fix without reading the trace. Don't.
A TypeError can mean a hundred things. The trace tells you which one — read all of it, including the "caused by".
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…