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).
按 GitHub 仓库热度看趋势,按能力分类找工具。每条 Skill 都能追溯到原始文件、所属仓库与许可信息。
搜索在浏览器内完成。分享筛选链接前,请检查其中的关键词。
探索 Skill
从真实的 SKILL.md提取名称与描述。分类为规则推断,适合作为探索入口。
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).
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.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
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
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work
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
Use when completing tasks, implementing major features, or before merging to verify work meets requirements
Use when executing implementation plans with independent tasks in the current session
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when implementing any feature or bugfix, before writing implementation code
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
Use when starting any conversation - establishes how to find and use skills, requiring skill invocation before ANY response including clarifying questions
Star 是仓库指标。一个仓库包含多个 Skill 时,每个 Skill 共享同一仓库的 Star 数。
这是一个可追溯的发现目录。热度、分类和许可各有独立含义,使用前请查看项目原文。
从公开 GitHub 仓库名单开始,扫描其中的 SKILL.md。当前目录不宣称覆盖全网。
Star 属于仓库,榜单只给仓库排位。Skill 展示继承的仓库 Star,不制造“单个 Skill Star”。
分类由名称、描述和路径规则推断;许可优先读取 GitHub 的 SPDX 信息。未确认的许可会明确标注。
卡片保留可用的中英文 README 链接;中文或英文界面优先采用对应语言摘要,其他界面保留原始 Skill 描述。公开数据定时更新。
本目录提供发现线索,不代表对 Skill 的安全性、兼容性或实际效果做过审计。运行第三方脚本前,请阅读原仓库代码与许可。 关于与数据方法 ↗