Every skill does one job. The -loop variants chain them.
A skill is a reusable instruction file that teaches Claude Code how to do one job well. Base skills do one step and stop. Loop variants keep going on their own — through code review and re-review — until the PR gets an LGTM.
Fact-check the issue against the real code, with file and line references.
Build the fix in an isolated git worktree; your main checkout stays untouched.
Open a PR that closes the issue and request an automated review.
Re-check each finding against the code — never blind-apply — fix, push, reply point-by-point.
Repeat until approved. Issue complete.
Issues carry a complexity score (C0–C100) right in the title — a rough rating of how hard the work is, used to decide when planning gets escalated.
Seventeen skills. Four jobs.
Issues, PR reviews, docs and releases, and Fable-driven planning — each with a base skill and, where it makes sense, a loop that runs to completion.
Issues that are never stubs.
Turn a bug, idea, or conversation into a complete GitHub issue — claims checked against the actual code first, complexity-scored, never half-empty. Then validate it, implement it end-to-end, and open the PR.
Reviews get re-checked, not rubber-stamped.
Reads all unaddressed PR feedback, re-validates every finding against the code — never blindly applies a suggestion — fixes what holds up, replies point-by-point, and requests a fresh review. The loop repeats until approval.
Docs and releases that match reality.
Update CLAUDE.md, AGENTS.md, SKILL.md, and README.md to match what recent commits actually changed, then cut a version tag and publish a GitHub release with generated notes — or both in sequence.
Plan with Fable 5. Build with anything.
Fable skills hand the high-stakes work — planning, drafting, fact-checking — to a subagent running on the Fable 5 model, while your main session does the building. Loops bring Fable in automatically for issues scored C50+ or touching safety-critical code.
Install in one command.
Three ways in — pick one. Each skill is just a directory with a SKILL.md, so you can also copy a single one straight from the repo.
npx
npx rk-skills
Copies every skill into your personal ~/.claude/skills/. Add --project to install into the current repo instead. Copy-based — re-run it to update.
Plugin · Auto-updates
/plugin marketplace add richkuo/rk-skills /plugin install rk-skills@rk-skills
The repo is a Claude Code plugin marketplace. Claude Code auto-discovers everything under skills/ and keeps it up to date. Restart the session, then trigger any skill by name.
Single skill
mkdir -p ~/.claude/skills/work-on-issue && curl -fsSL .../work-on-issue/SKILL.md -o ~/.claude/skills/work-on-issue/SKILL.md
Want just one? Copy its SKILL.md directly from the repo — no marketplace, no clone, no dependencies.
Review bot prerequisite: the PR-review loops need an automated reviewer that answers @claude review comments. The repo ships a ready-made GitHub Actions workflow — copy templates/claude-review.yml into .github/workflows/, add an ANTHROPIC_API_KEY secret, and the bot and skills speak the same format out of the box.