[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70MZQW4CC24HAWCDGAQDWRD":3,"skill-same:01M70MZQW4CC24HAWCDGAQDWRD":96},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70MZQW4CC24HAWCDGAQDWRD","opc-business-model-design",null,"Design a viable business model for a one-person company using Lean Canvas and a simplified Business Model Canvas. Use when Codex needs to explain the business-model concepts when needed, verify niche and value-proposition prerequisites, ask one question at a time, present multiple model choices, and write user-confirmed outputs into `opc-doc\u002F`.","shengdabai\u002FTony-Claude-Code-Skills","shengdabai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F116417419?v=4","01M70F6D2WY5PQV5A92BKYJQEW","Tony Sheng","01M70F6D3GAAAYZ5H4CC1G8VXM",3,"MIT","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"design","business","opc business model design","business model","model design","model","explain","ask","when","use","question","business model canvas","outputs","company","canvas","lean","time","for","value","business-model","2026-11-10 10:12:30",false,"---\nname: opc-business-model-design\ndescription: Design a viable business model for a one-person company using Lean Canvas and a simplified Business Model Canvas. Use when Codex needs to explain the business-model concepts when needed, verify niche and value-proposition prerequisites, ask one question at a time, present multiple model choices, and write user-confirmed outputs into `opc-doc\u002F`.\n---\n\n# 商业模式设计\n\n## 目标\n\n帮助用户把“这个生意如何成立”拆清楚，而不是直接替用户填完一张画布。\n\n## 核心原则\n\n- 默认读写当前工作目录下的 `opc-doc\u002F`\n- 教学模式下先解释 Lean Canvas 和轻量商业模式画布是什么\n- 一次只处理一个模块，不一次填完整张画布\n- 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个\n- 每个关键模块默认给 3 个可选方案，并附加 `4. 我有自己的方案`\n- 用户确认后再写入正式结果\n- 不直接给推荐结论，只做方案分析\n- **本阶段只做\"这个生意如何成立\"的结构分析，不进入执行层**\n\n## 本阶段边界\n\n### 本步做什么\n\n- 拆解商业模式核心模块（Problem \u002F Solution \u002F Channels \u002F Revenue 等）\n- 识别高风险假设\n- 确认当前商业模式方向\n\n### 本步不做什么（以下属于后续阶段，不要提前进入）\n\n- ❌ 不做 MVP 设计或产品原型（属于 opc-mvp-designer）\n- ❌ 不做获客流程或内容计划（属于转化闭环阶段）\n- ❌ 不做具体运营 SOP 或交付流程（属于资产沉淀阶段）\n\n**越界检测**：如果出现\"我先做哪个功能\"\"怎么开始第一单\"\"怎么发内容\"等话题，先记录，再说：\n> \"这属于后续 MVP 或执行阶段的范围。我们先把商业模式的假设确认清楚，再推进。\"\n\n## 本步骤必须完成什么\n\n优先完成 Lean Canvas 的核心模块：\n\n1. Problem\n2. Customer Segments\n3. Unique Value Proposition\n4. Solution\n5. Channels\n6. Revenue Streams\n7. Cost Structure\n8. Key Metrics\n9. Unfair Advantage\n\n在此基础上，再用 BMC Lite 做轻量校验。\n\n## 优先确认顺序\n\n1. Problem\n2. Customer Segments\n3. Unique Value Proposition\n4. Solution\n5. Channels\n6. Revenue Streams\n7. Cost Structure\n8. Key Metrics\n9. Unfair Advantage\n\n## 完成标准\n\n- Lean Canvas 核心模块已完成\n- 高风险假设已提炼\n- 用户已确认当前商业模式方向\n\n## 本步需要解释什么\n\n教学模式下先解释：\n\n- Lean Canvas 是创业假设的简表\n- 商业模式画布是看“价值如何创造、传递、获取”\n- 这一步的作用是防止在商模没想清楚时就盲目做产品\n\n## 输入\n\n必须优先读取：\n\n- `opc-doc\u002Foutputs\u002F02-niche-positioning\u002F*`\n- `opc-doc\u002Foutputs\u002F03-value-proposition\u002F*`\n\n如果前置结果不足，先建议回到对应前置 skill。\n\n## 执行步骤\n\n1. 先解释本步作用\n2. 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个，并按模块推进，例如：\n   - 这类用户最核心的问题是什么？\n   - 你打算先卖什么？\n   - 用户会通过什么渠道找到你？\n   - 你更想怎么收费？\n3. 每一轮回答后，给简短反馈，说明当前商模正在成形的哪一部分\n4. 对关键模块给 3 个候选方案，例如：\n   - 定价方式的 3 个版本\n   - 渠道路径的 3 个版本\n   - 收入结构的 3 个版本\n5. 默认增加 `4. 我有自己的方案`\n6. 让用户选、改、混合，或提出自己的版本\n7. 在关键模块被确认后，再整理为 Lean Canvas 与 BMC Lite\n8. 提炼高风险假设\n9. 用户确认后再落盘\n\n## 输出\n\n对话层必须包含：\n\n1. 本步解释\n2. 当前商模模块摘要\n3. 3 个关键方案候选 + `4. 我有自己的方案`\n4. 每个方案的适用情况、优点和代价\n5. 请用户确认或修改\n\n## 落盘检查点（阶段必须完成，不可跳过）\n\n用户明确确认核心商模方向后，**立即**使用 Write 工具在文件系统上创建以下文件，然后才能进入下一阶段。在对话中描述结论不等于落盘。\n\n**写入文件：**\n\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Flean-canvas.md`（Lean Canvas 核心模块填写结果）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Fbusiness-model-canvas-lite.md`（BMC Lite 轻量校验）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Fpricing-notes.md`（收费方式假设）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Frisky-assumptions.md`（高风险假设清单，供 MVP 阶段优先验证）\n\n**更新状态文件：**\n\n- `opc-doc\u002Fstate\u002Fcurrent-stage.json`（写入：`{\"stage\": \"04-business-model\", \"status\": \"completed\", \"next_stage\": \"06-mvp-designer\", \"summary\": \"一句话商模核心\"}`）\n- `opc-doc\u002Fstate\u002Fdecisions.json`（追加核心商模决策）\n- `opc-doc\u002Fstate\u002Fassumptions.json`（写入高风险假设列表）\n\n**落盘完成后，在对话中告知用户：**\n> \"✅ 商业模式结论已保存。下次对话可以从 MVP 设计继续。\"\n\n## gbrain 同步（可选，默认关闭）\n\n如果环境变量 `OPC_AUTO_SYNC=1`，落盘完成后**自动**调用：\n\n```bash\nOPC_TAG=\"$(basename \"$PWD\")\" ~\u002F.claude\u002Fscripts\u002Fopc-to-gbrain.sh \"$OPC_TAG\"\n```\n\n把本阶段产出同步到 gbrain，以后可跨项目用 `gbrain query \"\u003C项目代号> 商业模式\"` 检索回忆。\n未设置 `OPC_AUTO_SYNC` 时**不要**自动调，不要询问——用户可手动跑同样命令同步。\n\n**只有落盘完成后，才可以提示进入 `opc-mvp-designer`。**\n\n## 何时调用其他 skills\n\n只有在用户确认核心商模后，才进入 `opc-mvp-designer`。\n\n## 异常处理\n\n- 如果用户明显不理解画布类术语，必须用更通俗的说法替代\n- 如果收入方式和价值主张冲突，要指出冲突并给备选，而不是直接定案\n","# 商业模式设计\n\n## 目标\n\n帮助用户把“这个生意如何成立”拆清楚，而不是直接替用户填完一张画布。\n\n## 核心原则\n\n- 默认读写当前工作目录下的 `opc-doc\u002F`\n- 教学模式下先解释 Lean Canvas 和轻量商业模式画布是什么\n- 一次只处理一个模块，不一次填完整张画布\n- 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个\n- 每个关键模块默认给 3 个可选方案，并附加 `4. 我有自己的方案`\n- 用户确认后再写入正式结果\n- 不直接给推荐结论，只做方案分析\n- **本阶段只做\"这个生意如何成立\"的结构分析，不进入执行层**\n\n## 本阶段边界\n\n### 本步做什么\n\n- 拆解商业模式核心模块（Problem \u002F Solution \u002F Channels \u002F Revenue 等）\n- 识别高风险假设\n- 确认当前商业模式方向\n\n### 本步不做什么（以下属于后续阶段，不要提前进入）\n\n- ❌ 不做 MVP 设计或产品原型（属于 opc-mvp-designer）\n- ❌ 不做获客流程或内容计划（属于转化闭环阶段）\n- ❌ 不做具体运营 SOP 或交付流程（属于资产沉淀阶段）\n\n**越界检测**：如果出现\"我先做哪个功能\"\"怎么开始第一单\"\"怎么发内容\"等话题，先记录，再说：\n> \"这属于后续 MVP 或执行阶段的范围。我们先把商业模式的假设确认清楚，再推进。\"\n\n## 本步骤必须完成什么\n\n优先完成 Lean Canvas 的核心模块：\n\n1. Problem\n2. Customer Segments\n3. Unique Value Proposition\n4. Solution\n5. Channels\n6. Revenue Streams\n7. Cost Structure\n8. Key Metrics\n9. Unfair Advantage\n\n在此基础上，再用 BMC Lite 做轻量校验。\n\n## 优先确认顺序\n\n1. Problem\n2. Customer Segments\n3. Unique Value Proposition\n4. Solution\n5. Channels\n6. Revenue Streams\n7. Cost Structure\n8. Key Metrics\n9. Unfair Advantage\n\n## 完成标准\n\n- Lean Canvas 核心模块已完成\n- 高风险假设已提炼\n- 用户已确认当前商业模式方向\n\n## 本步需要解释什么\n\n教学模式下先解释：\n\n- Lean Canvas 是创业假设的简表\n- 商业模式画布是看“价值如何创造、传递、获取”\n- 这一步的作用是防止在商模没想清楚时就盲目做产品\n\n## 输入\n\n必须优先读取：\n\n- `opc-doc\u002Foutputs\u002F02-niche-positioning\u002F*`\n- `opc-doc\u002Foutputs\u002F03-value-proposition\u002F*`\n\n如果前置结果不足，先建议回到对应前置 skill。\n\n## 执行步骤\n\n1. 先解释本步作用\n2. 默认一次只问一个问题；如果几个问题都很轻、彼此紧密相关，可以合并成 2 到 3 个，并按模块推进，例如：\n   - 这类用户最核心的问题是什么？\n   - 你打算先卖什么？\n   - 用户会通过什么渠道找到你？\n   - 你更想怎么收费？\n3. 每一轮回答后，给简短反馈，说明当前商模正在成形的哪一部分\n4. 对关键模块给 3 个候选方案，例如：\n   - 定价方式的 3 个版本\n   - 渠道路径的 3 个版本\n   - 收入结构的 3 个版本\n5. 默认增加 `4. 我有自己的方案`\n6. 让用户选、改、混合，或提出自己的版本\n7. 在关键模块被确认后，再整理为 Lean Canvas 与 BMC Lite\n8. 提炼高风险假设\n9. 用户确认后再落盘\n\n## 输出\n\n对话层必须包含：\n\n1. 本步解释\n2. 当前商模模块摘要\n3. 3 个关键方案候选 + `4. 我有自己的方案`\n4. 每个方案的适用情况、优点和代价\n5. 请用户确认或修改\n\n## 落盘检查点（阶段必须完成，不可跳过）\n\n用户明确确认核心商模方向后，**立即**使用 Write 工具在文件系统上创建以下文件，然后才能进入下一阶段。在对话中描述结论不等于落盘。\n\n**写入文件：**\n\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Flean-canvas.md`（Lean Canvas 核心模块填写结果）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Fbusiness-model-canvas-lite.md`（BMC Lite 轻量校验）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Fpricing-notes.md`（收费方式假设）\n- `opc-doc\u002Foutputs\u002F04-business-model\u002Frisky-assumptions.md`（高风险假设清单，供 MVP 阶段优先验证）\n\n**更新状态文件：**\n\n- `opc-doc\u002Fstate\u002Fcurrent-stage.json`（写入：`{\"stage\": \"04-business-model\", \"status\": \"completed\", \"next_stage\": \"06-mvp-designer\", \"summary\": \"一句话商模核心\"}`）\n- `opc-doc\u002Fstate\u002Fdecisions.json`（追加核心商模决策）\n- `opc-doc\u002Fstate\u002Fassumptions.json`（写入高风险假设列表）\n\n**落盘完成后，在对话中告知用户：**\n> \"✅ 商业模式结论已保存。下次对话可以从 MVP 设计继续。\"\n\n## gbrain 同步（可选，默认关闭）\n\n如果环境变量 `OPC_AUTO_SYNC=1`，落盘完成后**自动**调用：\n\n```bash\nOPC_TAG=\"$(basename \"$PWD\")\" ~\u002F.claude\u002Fscripts\u002Fopc-to-gbrain.sh \"$OPC_TAG\"\n```\n\n把本阶段产出同步到 gbrain，以后可跨项目用 `gbrain query \"\u003C项目代号> 商业模式\"` 检索回忆。\n未设置 `OPC_AUTO_SYNC` 时**不要**自动调，不要询问——用户可手动跑同样命令同步。\n\n**只有落盘完成后，才可以提示进入 `opc-mvp-designer`。**\n\n## 何时调用其他 skills\n\n只有在用户确认核心商模后，才进入 `opc-mvp-designer`。\n\n## 异常处理\n\n- 如果用户明显不理解画布类术语，必须用更通俗的说法替代\n- 如果收入方式和价值主张冲突，要指出冲突并给备选，而不是直接定案\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fopc-business-model-design",1,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills","https:\u002F\u002Fzturnsgo.com","https:\u002F\u002Fgithub.com\u002Fshengdabai","https:\u002F\u002Fzturnsgo.com\u002F","AI × education creator — producer, not consumer. Taught 6,000+ learners; shipping learning tools & daily essays with Claude Code, practicing @xiaolai's way 🥋","2026-11-01 21:28:23",{"source":8,"skillName":5,"commands":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill opc-business-model-design",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill opc-business-model-design",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill opc-business-model-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002FSKILL.md",true,[78,84,88,92],{"path":79,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":82,"sourceHtmlUrl":83},"agents\u002Fopenai.yaml","REFERENCE","参考文档",319,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002Fagents\u002Fopenai.yaml",{"path":85,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fbmc-lite.md",175,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002Freferences\u002Fbmc-lite.md",{"path":89,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Flean-canvas-lite.md",205,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002Freferences\u002Flean-canvas-lite.md",{"path":93,"resourceType":80,"resourceTypeDesc":81,"sizeBytes":94,"sourceHtmlUrl":95},"references\u002Fpricing-checklist.md",231,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fopc-business-model-design\u002Freferences\u002Fpricing-checklist.md",[97,114,146,171,193,213],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":106,"publishedAt":49},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[107,108,109,110,111,112,113],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":126,"publishedAt":49},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[120,123],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":124,"categoryName":125,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师",[116,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,145],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":147,"name":148,"nameZh":6,"description":149,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":150,"categories":151,"keywords":156,"publishedAt":49},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[152,153],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者",[148,157,158,159,160,161,162,163,135,164,165,166,37,38,167,168,169,170],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":172,"name":173,"nameZh":6,"description":174,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":175,"categories":176,"keywords":178,"publishedAt":49},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[177],{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},[179,180,148,181,182,169,183,184,185,186,187,188,189,190,133,191,37,38,127,192],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":194,"name":195,"nameZh":6,"description":196,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":197,"categories":198,"keywords":203,"publishedAt":49},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[199,200,201,202],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":121,"categoryName":122,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":124,"categoryName":125,"taxonomyType":26,"taxonomyTypeDesc":27},{"categoryNo":154,"categoryName":155,"taxonomyType":26,"taxonomyTypeDesc":27},[204,112,205,206,207,208,143,37,38,209,210,211,212],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":221,"publishedAt":49},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[219,220],{"categoryNo":104,"categoryName":105,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":154,"categoryName":155,"taxonomyType":26,"taxonomyTypeDesc":27},[222,112,223,131,224,210,37,205,208,38,211],"Rules","writing rules","project rules"]