RADAR SKILL · GITHUB / obra

obra · Agent Skills

14 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.

obra

Community

brainstorming

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).

installazioni: 387,6K
GitHub Stars: 297,7K
Aggiornato: 10 ott

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes

installazioni: 287,3K
GitHub Stars: 297,7K
Aggiornato: 10 ott

writing-plans

Use when you have a spec or requirements for a multi-step task, before touching code

installazioni: 269,7K
GitHub Stars: 297,7K
Aggiornato: 10 ott

using-superpowers

Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions

installazioni: 260,3K
GitHub Stars: 297,7K
Aggiornato: 10 ott

requesting-code-review

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

installazioni: 247,9K
GitHub Stars: 297,7K
Aggiornato: 10 ott

test-driven-development

Use when implementing any feature or bugfix, before writing implementation code

installazioni: 246,4K
GitHub Stars: 297,7K
Aggiornato: 10 ott

verification-before-completion

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

installazioni: 234,6K
GitHub Stars: 297,7K
Aggiornato: 10 ott

executing-plans

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

installazioni: 230,7K
GitHub Stars: 297,7K
Aggiornato: 10 ott

subagent-driven-development

Use when executing implementation plans with independent tasks in the current session

installazioni: 223,7K
GitHub Stars: 297,7K
Aggiornato: 10 ott

receiving-code-review

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

installazioni: 210,2K
GitHub Stars: 297,7K
Aggiornato: 10 ott

dispatching-parallel-agents

Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies

installazioni: 207,5K
GitHub Stars: 297,7K
Aggiornato: 10 ott

writing-skills

Use when creating new skills, editing existing skills, or verifying skills work before deployment

installazioni: 206,8K
GitHub Stars: 297,7K
Aggiornato: 10 ott

using-git-worktrees

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

installazioni: 206,3K
GitHub Stars: 297,7K
Aggiornato: 10 ott

finishing-a-development-branch

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work

installazioni: 203,7K
GitHub Stars: 297,7K
Aggiornato: 10 ott

MIT1 File

Vedi dettagli →