Is that skill safe? Look it up.
1,362 public agent skills with a security grade and content hash, rescanned every night.
- A
brainstorming
302kobra/superpowers
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).
1 low - A
diagnosing-superpowers
302kobra/superpowers
Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.
No security findings - A
dispatching-parallel-agents
302kobra/superpowers
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
No security findings - A
executing-plans
302kobra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
No security findings - A
finishing-a-development-branch
302kobra/superpowers
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
No security findings - A
receiving-code-review
302kobra/superpowers
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation
No security findings - A
requesting-code-review
302kobra/superpowers
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
No security findings - A
subagent-driven-development
302kobra/superpowers
Use when executing implementation plans with independent tasks in the current session
No security findings - A
systematic-debugging
302kobra/superpowers
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
1 medium - A
test-driven-development
302kobra/superpowers
Use when implementing any feature or bugfix, before writing implementation code
No security findings - A
using-git-worktrees
302kobra/superpowers
Use when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback
No security findings - A
using-superpowers
302kobra/superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
No security findings - A
verification-before-completion
302kobra/superpowers
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
No security findings - A
writing-plans
302kobra/superpowers
Use when you have a spec or requirements for a multi-step task, before touching code
No security findings - A
writing-skills
302kobra/superpowers
Use when creating new skills, editing existing skills, or verifying skills work before deployment
No security findings - A
ask-matt
297kmattpocock/skills
Ask which skill or flow fits your situation. A router over the skills in this repo.
No security findings - A
chief-of-staff
297kmattpocock/skills
Pursue a long-running goal in a single session by co-ordinating subagents.
No security findings - A
claude-handoff
297kmattpocock/skills
Hand the current conversation off to a fresh background agent that picks up the work immediately.
No security findings - A
code-review
297kmattpocock/skills
Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to "review since X".
No security findings - A
codebase-design
297kmattpocock/skills
Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.
No security findings - A
diagnosing-bugs
297kmattpocock/skills
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
No security findings - A
domain-modeling
297kmattpocock/skills
Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md, or recording or editing an ADR.
No security findings - A
git-guardrails-claude-code
297kmattpocock/skills
Set up Claude Code hooks to block dangerous git commands (push, reset --hard, clean, branch -D, etc.) before they execute. Use when user wants to prevent destructive git operations, add git safety hooks, or block git push/reset in Claude Code.
No security findings - A
grill-me
297kmattpocock/skills
A relentless interview to sharpen a plan or design.
No security findings - A
grill-with-docs
297kmattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
No security findings - A
grilling
297kmattpocock/skills
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
1 low - A
handoff
297kmattpocock/skills
Compact the current conversation into a handoff document for another agent to pick up.
No security findings - A
implement
297kmattpocock/skills
Implement a piece of work based on a spec or set of tickets.
No security findings - A
implement-spec
297kmattpocock/skills
Implement the result of /to-spec and /to-tickets in code.
No security findings - A
improve-codebase-architecture
297kmattpocock/skills
Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.
No security findings