a11y-pass
Catch the accessibility failures that ship in almost every AI-built UI. Use after building any interactive component.
Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.
$ npx -y skills add Archive228/loopkit --skill secret-scan --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/secret-scanContext preview
The summary Claude sees to decide when to auto-load this skill.
Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials.
name: secret-scan description: Catch hardcoded secrets, keys, and tokens before they get committed. Use before any commit and on any file with credentials. when_to_use: before commit, files with API keys, .env handling, config, connection strings
Grep the diff for: `api[_-]?key`, `secret`, `token`, `password`, `BEGIN PRIVATE KEY`, `AKIA[0-9A-Z]{16}`, `sk-`, `ghp_`, bearer values, and long base64/hex blobs. For each hit: is it a real secret or a placeholder? Real secrets: 1. Must move to env / a secrets manager — never the repo. 2. If already committed, it is COMPROMISED. Rotate it, don't just delete the line. 3. Add the pattern to `.gitignore` / a pre-commit secret scanner. Output: file:line of every real secret + the rotation step. A deleted secret in git history is still leaked.
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…