Track GitHub repository popularity and discover skills by capability. Every listing links back to its source file, repository, and license information.
Stars belong to repositories. Skills in the same repository share its Star count.
Names and descriptions come from real SKILL.md files. Categories are rule-based discovery aids.
Browse all skills · paginated catalog
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).
skills/brainstorming/SKILL.md
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.
skills/diagnosing-superpowers/SKILL.md
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
skills/dispatching-parallel-agents/SKILL.md
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
skills/executing-plans/SKILL.md
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
skills/finishing-a-development-branch/SKILL.md
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
skills/receiving-code-review/SKILL.md
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
skills/requesting-code-review/SKILL.md
Use when executing implementation plans with independent tasks in the current session
skills/subagent-driven-development/SKILL.md
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
skills/systematic-debugging/SKILL.md
Use when implementing any feature or bugfix, before writing implementation code
skills/test-driven-development/SKILL.md
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
skills/using-git-worktrees/SKILL.md
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
skills/using-superpowers/SKILL.md
This is a traceable discovery directory. Popularity, categories, and licenses mean different things; review the source before using a skill.
We start with a named list of public GitHub repositories and scan their SKILL.md files. This is not a GitHub-wide index.
Stars belong to repositories. Skills display their source repository's Stars, never invented skill-level Stars.
Categories are inferred from names, descriptions, and paths. License labels use GitHub SPDX data when available; uncertainty stays visible.
Cards retain available Chinese and English README links. The Chinese and English interfaces prefer the corresponding source summary; other interfaces retain the original Skill description. Public data is refreshed on a schedule.
This directory helps you discover skills. It does not audit their security, compatibility, or effectiveness. Review source code and licenses before running third-party scripts. About & data methods ↗