New Checked the same way as MCP servers
Agent Skills, and what they let an agent do
Read straight from each publisher's repository. For every skill: what it allows the agent to do, the scripts it ships, and what fixed checks matched. Nothing is run.
Skills from obra (Jesse Vincent)15
Clear filters- brainstormingobra (Jesse Vincent) · 4 scriptsYou 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).Destructive commandsReaches the networkRuns commands1 high finding
- diagnosing-superpowersobra (Jesse Vincent)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 repo…Instructions only
- dispatching-parallel-agentsobra (Jesse Vincent)Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesInstructions only
- executing-plansobra (Jesse Vincent)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 availableDestructive commands1 finding
- finishing-a-development-branchobra (Jesse Vincent)Use when implementation is complete, all tests pass, and you need to decide how to integrate the workInstructions only
- receiving-code-reviewobra (Jesse Vincent)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 implementationInstructions only
- requesting-code-reviewobra (Jesse Vincent)Use when completing tasks, implementing major features, or before merging to verify work meets requirementsInstructions only
- subagent-driven-developmentobra (Jesse Vincent)Use when executing implementation plans with independent tasks in the current sessionDestructive commands1 high finding
- systematic-debuggingobra (Jesse Vincent) · 2 scriptsUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesRuns commands1 high finding
- test-driven-developmentobra (Jesse Vincent)Use when implementing any feature or bugfix, before writing implementation codeInstructions only
- using-git-worktreesobra (Jesse Vincent)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 fallbackInstructions only
- using-superpowersobra (Jesse Vincent)Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questionsInstructions only
- verification-before-completionobra (Jesse Vincent)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 alwaysInstructions only
- writing-plansobra (Jesse Vincent)Use when you have a spec or requirements for a multi-step task, before touching codeInstructions only
- writing-skillsobra (Jesse Vincent) · 1 scriptUse when creating new skills, editing existing skills, or verifying skills work before deploymentRuns commands1 finding
Labels come from the skill's own files, read on the date shown: the tools its frontmatter allows and the scripts it ships. They are not a safety rating, and no finding is not a safety guarantee. How skills are checked.