Are obra skills safe?
We index 15 public skills from obra. 15 graded A. Each one is pinned to its content hash and rescanned nightly.
- 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