Getting Started with Skills by aaaaqwq/agi-super-skills
npx skills add https://github.com/aaaaqwq/agi-super-skills --skill 'Getting Started with Skills'在声明使用技能前,务必使用 Read 工具。 会话开始的钩子不会自动为你读取技能。未调用 Read 就声明使用技能等于撒谎。
遵循强制性的工作流程。 编码前进行头脑风暴。执行任何任务前先检查相关技能。
为检查清单创建 TodoWrite 待办事项。 仅靠大脑记忆 = 步骤会被跳过。每次都如此。
1. 检查技能列表,可以在会话开始时进行,或者运行 find-skills [PATTERN] 来筛选。
2. 如果存在相关技能,你必须使用它:
${SUPERPOWERS_SKILLS_ROOT}/skills/category/skill-name/SKILL.md不要找理由:
原因: 技能文档记录了经过验证的技术,可以节省时间并防止错误。不使用可用的技能意味着重复解决已解决的问题并犯已知的错误。
广告位招租
在这里展示您的产品或服务
触达数万 AI 开发者,精准高效
如果存在针对你任务的技能,你必须使用它,否则你将无法完成任务。
如果一个技能包含检查清单,你必须为每一项创建 TodoWrite 待办事项。
不要:
原因: 没有 TodoWrite 跟踪的检查清单 = 步骤会被跳过。每次都如此。与遗漏步骤的代价相比,TodoWrite 的开销微乎其微。
示例: skills/testing/test-driven-development/SKILL.md, skills/debugging/systematic-debugging/SKILL.md, skills/meta/writing-skills/SKILL.md
在你使用 Read 工具阅读了一个技能后,声明你正在使用它:
"我已阅读 [技能名称] 技能,并正在使用它来 [你正在做的事情]。"
示例:
原因: 透明度有助于你的人类伙伴理解你的过程并及早发现错误。这也确认了你确实阅读了该技能。
每个技能都有相同的结构:
when_to_use 告诉你这个技能是否适用于你的情况许多技能包含严格的规则(TDD、调试、验证)。 请严格遵守。不要为了适应而放弃这些纪律。
有些技能是灵活的模式(架构、命名)。 根据你的上下文调整核心原则。
技能本身会告诉你它属于哪种类型。
你的人类伙伴的具体指令描述了做什么,而不是怎么做。
"添加 X"、"修复 Y" = 是目标,不是跳过头脑风暴、TDD 或 RED-GREEN-REFACTOR 的许可。
危险信号: "指令很具体" • "看起来很简单" • "工作流程太繁琐"
原因: 具体的指令意味着清晰的需求,而这正是工作流程最重要的时候。在"简单"任务上跳过流程,正是简单任务变成复杂问题的原因。
开始任何任务时:
技能有检查清单? 为每个项目创建 TodoWrite 待办事项。
找到相关技能 = 必须阅读并使用它。不是可选的。
每周安装
0
仓库
GitHub 星标
11
首次出现
1970年1月1日
安全审计
Use Read tool before announcing skill usage. The session-start hook does NOT read skills for you. Announcing without calling Read = lying.
Follow mandatory workflows. Brainstorming before coding. Check for skills before ANY task.
Create TodoWrite todos for checklists. Mental tracking = steps get skipped. Every time.
1. Check skills list at session start, or run find-skills [PATTERN] to filter.
2. If relevant skill exists, YOU MUST use it:
${SUPERPOWERS_SKILLS_ROOT}/skills/category/skill-name/SKILL.mdDon't rationalize:
Why: Skills document proven techniques that save time and prevent mistakes. Not using available skills means repeating solved problems and making known errors.
If a skill for your task exists, you must use it or you will fail at your task.
If a skill has a checklist, YOU MUST create TodoWrite todos for EACH item.
Don't:
Why: Checklists without TodoWrite tracking = steps get skipped. Every time. The overhead of TodoWrite is tiny compared to the cost of missing steps.
Examples: skills/testing/test-driven-development/SKILL.md, skills/debugging/systematic-debugging/SKILL.md, skills/meta/writing-skills/SKILL.md
After you've read a skill with Read tool, announce you're using it:
"I've read the [Skill Name] skill and I'm using it to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the skill.
Every skill has the same structure:
when_to_use tells you if this skill matches your situationMany skills contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some skills are flexible patterns (architecture, naming). Adapt core principles to your context.
The skill itself tells you which type it is.
Your human partner's specific instructions describe WHAT to do, not HOW.
"Add X", "Fix Y" = the goal, NOT permission to skip brainstorming, TDD, or RED-GREEN-REFACTOR.
Red flags: "Instruction was specific" • "Seems simple" • "Workflow is overkill"
Why: Specific instructions mean clear requirements, which is when workflows matter MOST. Skipping process on "simple" tasks is how simple tasks become complex problems.
Starting any task:
Skill has checklist? TodoWrite for every item.
Finding a relevant skill = mandatory to read and use it. Not optional.
Weekly Installs
0
Repository
GitHub Stars
11
First Seen
Jan 1, 1970
Security Audits
API文档生成与管理指南:OpenAPI规范、Swagger使用教程与团队协作
11,700 周安装