By jerseycheese
Issue triage, TDD, CI fix-with-memory, design-system guard, PR review, dead-code cleanup, worktree setup, and session wrap-up skills.
Analyzes a single GitHub issue and produces a detailed technical specification ready for implementation. Fetches the issue, discovers existing patterns in the codebase, defines scope boundaries, and produces an implementation plan with MVP tests. Use before starting work on an issue to understand it fully. Trigger on "analyze issue
Inspect and debug live web pages using the Chrome DevTools Protocol via the `bdg` CLI. Use for targeted DOM queries, computed style checks, layout debugging, and CDP method calls without loading a full page snapshot. Prefer over chrome-devtools-mcp for token efficiency. Trigger on: "inspect element", "check computed styles", "query the DOM", "what does the DOM look like", "debug layout", "check the CSS on", "run a DevTools query", "what's the rendered style of", "inspect the page".
Automatically invoke when CI checks fail on a PR. Triggers on: any mention of CI failure, red checks, failed GitHub Actions, or "CI is broken/failing". Reads session handoffs and a known-issues log to avoid repeating failed fix attempts. Do NOT wait for user to ask — invoke as soon as a CI failure is confirmed.
Choose Your Own Adventure mode. Use when the user invokes /cyoa, asks for "cyoa mode", "choose your own adventure", or asks to make a development task feel like a game. Frames a real software task as a branching adventure where the user picks design decisions at every meaningful step. Produces real, working code — the adventure framing is purely a stylistic and decision-elicitation layer on top of normal development.
Identifies and removes dead/orphaned code, tests, and Storybook stories — including trivial tests that check only obvious behavior or rare edge cases with no real value. Always validates that code is truly unused before deleting anything. Trigger on: "remove dead code", "clean up unused files", "delete orphaned components", "find unused exports", "remove trivial tests", "clean up the codebase", "what code can we delete", "prune the repo", "remove stale stories".
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of agent skills usable across Claude Code, Codex, Gemini CLI, and any tool that reads a shared .agents/skills directory. Each skill lives in its own directory with a single SKILL.md whose frontmatter tells the agent when to invoke it and what to do.
bdg CLI. Token-efficient alternative to a full page snapshot.raw.githubusercontent.com URLs..agents/skills paths.<skill-name>/
SKILL.md # frontmatter (name, description) + body (the actual instructions)
The description field is what the agent reads to decide whether to invoke the skill — keep trigger phrases concrete and current.
Each agent looks for skills in a specific directory. Copy or symlink the skill folder (the whole thing, not just SKILL.md) into the right path for whichever tool you're using.
| Tool | User-level (available everywhere) | Project-level (this repo only) |
|---|---|---|
| Claude Code | ~/.claude/skills/<skill-name>/ | .claude/skills/<skill-name>/ |
| Codex | ~/.agents/skills/<skill-name>/ | .agents/skills/<skill-name>/ |
| Gemini CLI | ~/.gemini/skills/<skill-name>/ or ~/.agents/skills/<skill-name>/ | .gemini/skills/<skill-name>/ or .agents/skills/<skill-name>/ |
The .agents/skills path is the interoperable spot — Codex and Gemini both read from it, so it's the path to pick if you want one copy to cover both.
Quick install for a single skill in Claude Code:
cp -r kiss ~/.claude/skills/
Or symlink if you want updates to flow back to this repo automatically:
ln -s "$(pwd)/kiss" ~/.claude/skills/kiss
If you're juggling all three tools, the skill-parity skill handles copying, updating, and pruning across every provider path in one pass — that's the path worth taking if you're maintaining more than a couple of skills.
This repo is also a Claude Code plugin marketplace, so Claude can install every skill at once and pull updates with a git push instead of a manual copy:
claude plugin marketplace add jerseycheese/agent-skills
claude plugin install workflow-skills@jack-skills
npx claudepluginhub jerseycheese/agent-skills --plugin workflow-skillsA growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
Develop, test, build, and deploy Godot 4.x games with Claude Code. Includes GdUnit4 testing, web/desktop exports, CI/CD pipelines, and deployment to Vercel/GitHub Pages/itch.io.
Comprehensive feature development workflow with specialized agents for codebase exploration, architecture design, and quality review
Tools to maintain and improve CLAUDE.md files - audit quality, capture session learnings, and keep project memory current.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses