Skill packages
Read the contents, pin a version, then import it for your Agent.
My skill packagesCapability IDs and tags match full values, e.g. data/analysis. Filters apply to the entire directory.
python-testing-patterns
Implement comprehensive testing strategies with pytest, fixtures, mocking, and test-driven development. Use when writing Python tests, setting up test suites, or implementing testing best practices.
Publisher name (self-declared): 社区样本 · 原作者 wshobson
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
Publisher name (self-declared): 社区样本 · 原作者 wshobson
using-superpowers
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Publisher name (self-declared): 社区样本 · 原作者 obra
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
Publisher name (self-declared): 社区样本 · 原作者 obra
dispatching-parallel-agents
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Publisher name (self-declared): 社区样本 · 原作者 obra
diagnosing-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.
Publisher name (self-declared): 社区样本 · 原作者 obra
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
Publisher name (self-declared): 社区样本 · 原作者 obra
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
Publisher name (self-declared): 社区样本 · 原作者 obra
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
Publisher name (self-declared): 社区样本 · 原作者 obra
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
Publisher name (self-declared): 社区样本 · 原作者 obra
requesting-code-review
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Publisher name (self-declared): 社区样本 · 原作者 obra
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code
Publisher name (self-declared): 社区样本 · 原作者 obra