[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77TYFJECF8Q668H2JJET4JM":3,"skill-same:01M77TYFJECF8Q668H2JJET4JM":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77TYFJECF8Q668H2JJET4JM","skill-design-guide",null,"Skill 设计指南。在创建新 Skill、优化现有 Skill、或评审 Skill 质量时使用。包含核心设计原则、常见陷阱、最佳实践。","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fskill-design-guide\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-design-guide\ndescription: Skill 设计指南。在创建新 Skill、优化现有 Skill、或评审 Skill 质量时使用。包含核心设计原则、常见陷阱、最佳实践。\n---\n\n# Skill 设计指南\n\n> 核心思想：**Skills 的本质不是提示词增强，而是 Workflow 的迁移**\n\n## Skill 是什么\n\nSkill 是一个工程化的能力单元，不是高级 Prompt：\n\n```\nskill-name\u002F\n├── SKILL.md      # 核心：告诉 Agent \"怎么做\" 的调度入口\n├── references\u002F   # 知识层：API 文档、业务规则、历史案例\n├── assets\u002F       # 模板层：输出骨架、固定格式\n├── scripts\u002F      # 执行层：确定性任务的代码\n└── hooks\u002F        # 约束与观测：记录调用、控制权限\n```\n\n## Skill 解决的三大痛点\n\n1. **提示词臃肿** — 复杂任务需要几百上千字 Prompt，难维护，模型注意力分散\n2. **上下文窗口限制** — 完美 Prompt 也要占用宝贵上下文\n3. **能力复用困难** — 调教好的能力难以分享、难以保证执行一致\n\n## 核心设计原则\n\n### 1. 元数据要精准\n\n`name` 和 `description` 是模型判断何时调用的唯一窗口。\n\n❌ 差的写法：\n```\ndescription: 用于审查代码质量的 Skill\n```\n\n✅ 好的写法：\n```\ndescription: 在用户提交 Pull Request 后自动触发，对新增代码进行安全审查，输出审查报告并标注高风险问题\n```\n\n**要点**：告诉模型什么时候触发、干什么事、输出什么。\n\n### 2. 约束强度适中\n\n- **管太死**：每一步都写死 → 模型遇到超出预期的情况就乱来\n- **放太松**：只说目标 → 每次结果不一样\n\n✅ 正确做法：\n- 明确告诉模型\"要做什么\"\n- 给它留足推理空间\n- 明确告诉它\"不要做什么\"\n- 配上关键场景的例子\n\n### 3. 一事一 Skill\n\n单一职责原则。Skill 越简单，触发越精准，执行越稳定。\n\n### 4. 持续迭代\n\n发现问题 → 加评测用例 → 改 Skill → 继续观察\n\n## Skill 开发流程\n\n### Step 1: 先用裸模型跑一遍\n\n看它哪里出错，这些就是 Skill 要填的坑。\n\n### Step 2: 定标准\n\n什么算好？什么算不好？定义及格线。\n\n示例：\n- 输入：一段关于项目进度讨论的会议记录\n- 期望：明确列出\"下一步行动\"，包含负责人和时间节点\n- 及格线：漏掉任何一个行动项就算失败\n\n### Step 3: 先有再优\n\n写最小可用版本，别一上来就大而全。\n\n评测里暴露什么问题，就先解决什么问题，别的先别管。\n\n### Step 4: 补边界\n\n最小版本能用了，再慢慢往里加东西：\n\n- 把边界情况写清楚：能处理什么、不能处理什么\n- 定好输入输出格式\n- 每个关键场景配一个例子\n\n### Step 5: 持续观察\n\n上线后监控，迭代改进。\n\n## 脚本编写原则\n\n如果 Skill 需要跑脚本：\n\n- **错误要说人话**：别抛异常，告诉模型\"为什么错\"和\"怎么办\"\n- **输出要解释清楚**：不光说\"干了什么\"，还要说\"为什么\"和\"接下来可以干什么\"\n- **别用魔法数字**：`TIMEOUT_SECONDS = 30  # 服务启动一般 10-20 秒`\n\n## 常见陷阱\n\n### 陷阱 1：写成说明书了\n\nSkill 是给模型下的指令，不是给人看的文档。\n\n❌ 不要写：\n```\n本 Skill 基于敏捷开发方法论\n旨在通过结构化思维提升会议纪要的质量...\n```\n\n✅ 要写：\n```\n什么情况用我、怎么执行、做成什么样\n```\n\n### 陷阱 2：越写越复杂\n\n功能越多越不稳定，模型也有注意力限制。\n\n**Skill 越简单，触发越精准，执行越稳定。**\n\n## 优先级覆盖机制\n\n同名 Skill 按优先级覆盖：\n\n```\n工作区 > 项目 Agent > 个人 Agent > 用户 managed > 内置 > 额外目录\n```\n\n用途：官方提供默认版本，个人有常用版本，项目可覆盖成专属版本，彼此不冲突。\n\n## 三级预算降级\n\n防止上下文爆炸：\n\n1. **完整格式** — name + description + instructions\n2. **紧凑格式** — name + location only\n3. **二分截断** — 找最大可行前缀\n\n## 渐进式披露\n\n模型启动时只加载元数据（name + description），触发时才加载完整指令，按需加载脚本和资源。\n\n这平衡了灵活性和效率：\n- 元数据始终在上下文中 → 模型知道自己能做什么\n- 指令按需加载 → 节省上下文\n- 资源按需调用 → 无限扩展可能","# Skill 设计指南\n\n> 核心思想：**Skills 的本质不是提示词增强，而是 Workflow 的迁移**\n\n## Skill 是什么\n\nSkill 是一个工程化的能力单元，不是高级 Prompt：\n\n```\nskill-name\u002F\n├── SKILL.md      # 核心：告诉 Agent \"怎么做\" 的调度入口\n├── references\u002F   # 知识层：API 文档、业务规则、历史案例\n├── assets\u002F       # 模板层：输出骨架、固定格式\n├── scripts\u002F      # 执行层：确定性任务的代码\n└── hooks\u002F        # 约束与观测：记录调用、控制权限\n```\n\n## Skill 解决的三大痛点\n\n1. **提示词臃肿** — 复杂任务需要几百上千字 Prompt，难维护，模型注意力分散\n2. **上下文窗口限制** — 完美 Prompt 也要占用宝贵上下文\n3. **能力复用困难** — 调教好的能力难以分享、难以保证执行一致\n\n## 核心设计原则\n\n### 1. 元数据要精准\n\n`name` 和 `description` 是模型判断何时调用的唯一窗口。\n\n❌ 差的写法：\n```\ndescription: 用于审查代码质量的 Skill\n```\n\n✅ 好的写法：\n```\ndescription: 在用户提交 Pull Request 后自动触发，对新增代码进行安全审查，输出审查报告并标注高风险问题\n```\n\n**要点**：告诉模型什么时候触发、干什么事、输出什么。\n\n### 2. 约束强度适中\n\n- **管太死**：每一步都写死 → 模型遇到超出预期的情况就乱来\n- **放太松**：只说目标 → 每次结果不一样\n\n✅ 正确做法：\n- 明确告诉模型\"要做什么\"\n- 给它留足推理空间\n- 明确告诉它\"不要做什么\"\n- 配上关键场景的例子\n\n### 3. 一事一 Skill\n\n单一职责原则。Skill 越简单，触发越精准，执行越稳定。\n\n### 4. 持续迭代\n\n发现问题 → 加评测用例 → 改 Skill → 继续观察\n\n## Skill 开发流程\n\n### Step 1: 先用裸模型跑一遍\n\n看它哪里出错，这些就是 Skill 要填的坑。\n\n### Step 2: 定标准\n\n什么算好？什么算不好？定义及格线。\n\n示例：\n- 输入：一段关于项目进度讨论的会议记录\n- 期望：明确列出\"下一步行动\"，包含负责人和时间节点\n- 及格线：漏掉任何一个行动项就算失败\n\n### Step 3: 先有再优\n\n写最小可用版本，别一上来就大而全。\n\n评测里暴露什么问题，就先解决什么问题，别的先别管。\n\n### Step 4: 补边界\n\n最小版本能用了，再慢慢往里加东西：\n\n- 把边界情况写清楚：能处理什么、不能处理什么\n- 定好输入输出格式\n- 每个关键场景配一个例子\n\n### Step 5: 持续观察\n\n上线后监控，迭代改进。\n\n## 脚本编写原则\n\n如果 Skill 需要跑脚本：\n\n- **错误要说人话**：别抛异常，告诉模型\"为什么错\"和\"怎么办\"\n- **输出要解释清楚**：不光说\"干了什么\"，还要说\"为什么\"和\"接下来可以干什么\"\n- **别用魔法数字**：`TIMEOUT_SECONDS = 30  # 服务启动一般 10-20 秒`\n\n## 常见陷阱\n\n### 陷阱 1：写成说明书了\n\nSkill 是给模型下的指令，不是给人看的文档。\n\n❌ 不要写：\n```\n本 Skill 基于敏捷开发方法论\n旨在通过结构化思维提升会议纪要的质量...\n```\n\n✅ 要写：\n```\n什么情况用我、怎么执行、做成什么样\n```\n\n### 陷阱 2：越写越复杂\n\n功能越多越不稳定，模型也有注意力限制。\n\n**Skill 越简单，触发越精准，执行越稳定。**\n\n## 优先级覆盖机制\n\n同名 Skill 按优先级覆盖：\n\n```\n工作区 > 项目 Agent > 个人 Agent > 用户 managed > 内置 > 额外目录\n```\n\n用途：官方提供默认版本，个人有常用版本，项目可覆盖成专属版本，彼此不冲突。\n\n## 三级预算降级\n\n防止上下文爆炸：\n\n1. **完整格式** — name + description + instructions\n2. **紧凑格式** — name + location only\n3. **二分截断** — 找最大可行前缀\n\n## 渐进式披露\n\n模型启动时只加载元数据（name + description），触发时才加载完整指令，按需加载脚本和资源。\n\n这平衡了灵活性和效率：\n- 元数据始终在上下文中 → 模型知道自己能做什么\n- 指令按需加载 → 节省上下文\n- 资源按需调用 → 无限扩展可能",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fs\u002Fskill-design-guide",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill skill-design-guide",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill skill-design-guide",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill skill-design-guide","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fs\u002Fskill-design-guide\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]