Agent Skills by obra
There are 14 agent skills in our directory.
obra publishes 14 AI agent skills in our directory. Browse them below — each links back to its source repository.
Updated June 2026
- brainstormingYou MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
- executing-plansUse when you have a written implementation plan to execute in a separate session with review checkpoints
- finishing-a-development-branchUse when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- receiving-code-reviewUse 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
- requesting-code-reviewUse when completing tasks, implementing major features, or before merging to verify work meets requirements
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current session
- systematic-debuggingUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes
- test-driven-developmentUse when implementing any feature or bugfix, before writing implementation code
- using-git-worktreesUse 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
- using-superpowersUse when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
- verification-before-completionUse 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
- writing-plansUse when you have a spec or requirements for a multi-step task, before touching code
- writing-skillsUse when creating new skills, editing existing skills, or verifying skills work before deployment