[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70FPHMPF993VV1RZN0R2Q9Z":3,"skill-same:01M70FPHMPF993VV1RZN0R2Q9Z":63},{"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":23,"publishedAt":34,"linkOnly":35,"markdownContent":36,"markdownBody":37,"frontMatter":38,"refName":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":46,"ownerDescription":47,"updatedAt":48,"install":49,"resources":62},"01M70FPHMPF993VV1RZN0R2Q9Z","agent-orchestration",null,"DO NOT invoke unless explicitly instructed. Core guidelines for orchestrating tasks with subagents.","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\u002F_collections\u002Fclaude-code\u002Fskills\u002Fagent-orchestration\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33],"orchestration","agent orchestration","guidelines","tasks","core","subagents","do","with","for","invoke","2026-11-10 10:12:30",false,"---\nname: agent-orchestration\ndescription: DO NOT invoke unless explicitly instructed. Core guidelines for orchestrating tasks with subagents.\n---\n\n\u003Ccore_principle>\n## Orchestration Role and Responsibility\n\n**Your role is management, not execution**:\n- You orchestrate and coordinate subagents, not implement tasks yourself\n- Your focus is on task planning, delegation, progress tracking, and quality assurance\n- Keep your context clean by delegating all implementation work to specialized subagents\n- Your value comes from effective coordination, not from doing the work directly\n\n**Key principle**: Delegate execution to subagents. Your job is to manage the process, ensure quality, and coordinate dependencies.\n\u003C\u002Fcore_principle>\n\n\u003Csubagent_collaboration>\n## Subagent Collaboration Principles\n\n\u003Cdelegation_guidelines>\n### Effective Delegation\n\n**Trust subagent expertise**:\n- Subagents are specialized for their domain\n- Provide necessary context but avoid over-specification\n- Let subagents exercise their judgment within their scope\n- Verify outcomes, not process\n\n**Avoid micromanagement**:\n- Do not dictate detailed procedures or perspectives\n- Focus on what needs to be achieved, not how\n- Allow subagents to apply their specialized knowledge\n- Review results after completion, not during execution\n\u003C\u002Fdelegation_guidelines>\n\n\u003Ccontext_management>\n### Context and Memory Management\n\n**Keep orchestrator context clean**:\n- Delegate detailed research to specialized subagents\n- Delegate design decisions to architect subagents\n- Delegate implementation to engineer subagents\n- Delegate quality verification to reviewer subagents\n\n**Session boundaries**:\n- Each subagent invocation is a separate session\n- Previous session context is not automatically available\n- Provide necessary continuity information in prompts\n- Use shared state mechanisms when available\n\u003C\u002Fcontext_management>\n\u003C\u002Fsubagent_collaboration>\n\n\u003Cerror_handling>\n## Error Handling and Loop Prevention\n\n\u003Cloop_detection>\n### Infinite Loop Prevention\n\n**Detection criteria**:\n- Track phase transitions and iteration counts\n- Define \"same error\u002Ffailure\": Same subagent fails with same\u002Fsimilar error message OR same issue remains unresolved across iterations\n\n**Intervention threshold**:\nIf same error\u002Ffailure occurs **3 consecutive times**:\n\n1. **Stop execution immediately**\n2. **Report to user**:\n   - Current phase\u002Fstep\n   - Repeated error description\n   - What has been attempted\n   - Task document path for reference\n3. **Request guidance**: Ask user how to proceed\n\n**Why 3 times?**:\n- First attempt: Initial try\n- Second attempt: Reasonable retry with adjusted approach\n- Third attempt: Pattern indicates fundamental blocker\n\n**Example situations**:\n- Subagent repeatedly fails with same error\n- Review keeps finding same issue after fixes\n- CI check fails on same test repeatedly\n- Same acceptance criterion remains unsatisfied\n\u003C\u002Floop_detection>\n\n\u003Crecovery_strategies>\n### Phase-Specific Recovery\n\n**Subagent failure**:\n- Log error details\n- Report to user with context\n- Request intervention (do not retry blindly)\n\n**Missing prerequisites**:\n- Document in task Memo section\n- Report to user with specific requirements\n- Wait for user to resolve\n\n**Ambiguous requirements**:\n- Return to requirements definition phase\n- Ask clarifying questions\n- Reach explicit agreement before proceeding\n\n**Unexpected state**:\n- Read task document to understand current state\n- Document unexpected condition in Memo\n- Report to user if recovery path unclear\n\u003C\u002Frecovery_strategies>\n\u003C\u002Ferror_handling>\n\n\u003Cbest_practices>\n## Orchestration Best Practices\n\n\u003Csession_planning>\n### Implementation Session Planning\n\n**Session granularity**:\n- Each session = functionally meaningful unit\n- Each session should be independently committable\n- Avoid sessions that are too small (single line changes) or too large (entire features)\n\n**Session ordering**:\n- Order by dependency (prerequisites first)\n- Consider logical progression for reviewer comprehension\n- Allow flexibility for discovered additional sessions\n\n**Parallel execution**:\n- Identify independent tasks that can run concurrently\n- Launch multiple subagents in parallel when tasks have no dependencies\n- Coordinate parallel sessions to maximize efficiency\n- Monitor all parallel sessions and aggregate results appropriately\n- Only serialize when dependencies require sequential execution\n\u003C\u002Fsession_planning>\n\n\u003Cflow_management>\n### Flow and Phase Management\n\n**Flexibility over rigidity**:\n- Phases are guidelines, not strict barriers\n- Allow backward transitions when issues are found\n- Continue iterations until all criteria converge\n- Adapt flow based on actual task complexity\n\n**Common phase loops**:\n- Review feedback → Implementation\n- CI failure → Implementation\n- Final verification failure → Relevant phase\n- Requirements unclear → Requirements definition\n\n**Termination conditions**:\n- All acceptance criteria satisfied\n- All review feedback resolved\n- All CI checks passed\n- User confirms completion\n\u003C\u002Fflow_management>\n\n\u003Cdecision_autonomy>\n### Autonomous Decision-Making\n\n**When orchestrating**:\n- Make phase transition decisions based on task document state\n- Skip unnecessary phases for simple tasks\n- Invoke additional subagents when complexity warrants\n- Balance efficiency with quality\n\n**Do not**:\n- Ask user for every minor decision\n- Rigidly follow phases when context suggests otherwise\n- Over-orchestrate simple tasks\n- Under-orchestrate complex tasks requiring design\n\n**Trust your judgment on**:\n- Is design phase needed?\n- Should this be multiple sessions?\n- Is review necessary for this change?\n\n**NEVER bypass subagent delegation**:\n- Implementation work ALWAYS goes to engineer subagent\n- PR creation ALWAYS goes to pr-creator subagent\n- CI monitoring ALWAYS goes to pr-checker subagent\n- \"Simple\" or \"Easy\" tasks do NOT justify direct execution\n\u003C\u002Fdecision_autonomy>\n\u003C\u002Fbest_practices>\n","\u003Ccore_principle>\n## Orchestration Role and Responsibility\n\n**Your role is management, not execution**:\n- You orchestrate and coordinate subagents, not implement tasks yourself\n- Your focus is on task planning, delegation, progress tracking, and quality assurance\n- Keep your context clean by delegating all implementation work to specialized subagents\n- Your value comes from effective coordination, not from doing the work directly\n\n**Key principle**: Delegate execution to subagents. Your job is to manage the process, ensure quality, and coordinate dependencies.\n\u003C\u002Fcore_principle>\n\n\u003Csubagent_collaboration>\n## Subagent Collaboration Principles\n\n\u003Cdelegation_guidelines>\n### Effective Delegation\n\n**Trust subagent expertise**:\n- Subagents are specialized for their domain\n- Provide necessary context but avoid over-specification\n- Let subagents exercise their judgment within their scope\n- Verify outcomes, not process\n\n**Avoid micromanagement**:\n- Do not dictate detailed procedures or perspectives\n- Focus on what needs to be achieved, not how\n- Allow subagents to apply their specialized knowledge\n- Review results after completion, not during execution\n\u003C\u002Fdelegation_guidelines>\n\n\u003Ccontext_management>\n### Context and Memory Management\n\n**Keep orchestrator context clean**:\n- Delegate detailed research to specialized subagents\n- Delegate design decisions to architect subagents\n- Delegate implementation to engineer subagents\n- Delegate quality verification to reviewer subagents\n\n**Session boundaries**:\n- Each subagent invocation is a separate session\n- Previous session context is not automatically available\n- Provide necessary continuity information in prompts\n- Use shared state mechanisms when available\n\u003C\u002Fcontext_management>\n\u003C\u002Fsubagent_collaboration>\n\n\u003Cerror_handling>\n## Error Handling and Loop Prevention\n\n\u003Cloop_detection>\n### Infinite Loop Prevention\n\n**Detection criteria**:\n- Track phase transitions and iteration counts\n- Define \"same error\u002Ffailure\": Same subagent fails with same\u002Fsimilar error message OR same issue remains unresolved across iterations\n\n**Intervention threshold**:\nIf same error\u002Ffailure occurs **3 consecutive times**:\n\n1. **Stop execution immediately**\n2. **Report to user**:\n   - Current phase\u002Fstep\n   - Repeated error description\n   - What has been attempted\n   - Task document path for reference\n3. **Request guidance**: Ask user how to proceed\n\n**Why 3 times?**:\n- First attempt: Initial try\n- Second attempt: Reasonable retry with adjusted approach\n- Third attempt: Pattern indicates fundamental blocker\n\n**Example situations**:\n- Subagent repeatedly fails with same error\n- Review keeps finding same issue after fixes\n- CI check fails on same test repeatedly\n- Same acceptance criterion remains unsatisfied\n\u003C\u002Floop_detection>\n\n\u003Crecovery_strategies>\n### Phase-Specific Recovery\n\n**Subagent failure**:\n- Log error details\n- Report to user with context\n- Request intervention (do not retry blindly)\n\n**Missing prerequisites**:\n- Document in task Memo section\n- Report to user with specific requirements\n- Wait for user to resolve\n\n**Ambiguous requirements**:\n- Return to requirements definition phase\n- Ask clarifying questions\n- Reach explicit agreement before proceeding\n\n**Unexpected state**:\n- Read task document to understand current state\n- Document unexpected condition in Memo\n- Report to user if recovery path unclear\n\u003C\u002Frecovery_strategies>\n\u003C\u002Ferror_handling>\n\n\u003Cbest_practices>\n## Orchestration Best Practices\n\n\u003Csession_planning>\n### Implementation Session Planning\n\n**Session granularity**:\n- Each session = functionally meaningful unit\n- Each session should be independently committable\n- Avoid sessions that are too small (single line changes) or too large (entire features)\n\n**Session ordering**:\n- Order by dependency (prerequisites first)\n- Consider logical progression for reviewer comprehension\n- Allow flexibility for discovered additional sessions\n\n**Parallel execution**:\n- Identify independent tasks that can run concurrently\n- Launch multiple subagents in parallel when tasks have no dependencies\n- Coordinate parallel sessions to maximize efficiency\n- Monitor all parallel sessions and aggregate results appropriately\n- Only serialize when dependencies require sequential execution\n\u003C\u002Fsession_planning>\n\n\u003Cflow_management>\n### Flow and Phase Management\n\n**Flexibility over rigidity**:\n- Phases are guidelines, not strict barriers\n- Allow backward transitions when issues are found\n- Continue iterations until all criteria converge\n- Adapt flow based on actual task complexity\n\n**Common phase loops**:\n- Review feedback → Implementation\n- CI failure → Implementation\n- Final verification failure → Relevant phase\n- Requirements unclear → Requirements definition\n\n**Termination conditions**:\n- All acceptance criteria satisfied\n- All review feedback resolved\n- All CI checks passed\n- User confirms completion\n\u003C\u002Fflow_management>\n\n\u003Cdecision_autonomy>\n### Autonomous Decision-Making\n\n**When orchestrating**:\n- Make phase transition decisions based on task document state\n- Skip unnecessary phases for simple tasks\n- Invoke additional subagents when complexity warrants\n- Balance efficiency with quality\n\n**Do not**:\n- Ask user for every minor decision\n- Rigidly follow phases when context suggests otherwise\n- Over-orchestrate simple tasks\n- Under-orchestrate complex tasks requiring design\n\n**Trust your judgment on**:\n- Is design phase needed?\n- Should this be multiple sessions?\n- Is review necessary for this change?\n\n**NEVER bypass subagent delegation**:\n- Implementation work ALWAYS goes to engineer subagent\n- PR creation ALWAYS goes to pr-creator subagent\n- CI monitoring ALWAYS goes to pr-checker subagent\n- \"Simple\" or \"Easy\" tasks do NOT justify direct execution\n\u003C\u002Fdecision_autonomy>\n\u003C\u002Fbest_practices>\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fclaude-code\u002Fskills\u002Fagent-orchestration",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":50,"prompt":60,"zipAvailable":61},[51,54,57],{"tool":52,"command":53},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill agent-orchestration",{"tool":55,"command":56},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill agent-orchestration",{"tool":58,"command":59},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill agent-orchestration","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fclaude-code\u002Fskills\u002Fagent-orchestration\u002FSKILL.md",true,[],[64,81,113,140,162,182],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":73,"publishedAt":34},"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",[70],{"categoryNo":71,"categoryName":72,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[74,75,76,77,78,79,80],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":93,"publishedAt":34},"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",[87,88],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[83,94,95,96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":123,"publishedAt":34},"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",[119,120],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},"01JBSEEDCAT000000000000036","内容创作者",[115,124,125,126,127,128,129,130,102,131,132,133,134,135,136,137,138,139],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","when","use","auto","types","Video","创作",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":147,"publishedAt":34},"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",[146],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[148,149,115,150,151,138,152,153,154,155,156,157,158,159,100,160,134,135,94,161],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":172,"publishedAt":34},"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",[168,169,170,171],{"categoryNo":71,"categoryName":72,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":89,"categoryName":90,"taxonomyType":91,"taxonomyTypeDesc":92},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},[173,79,174,175,176,177,110,134,135,178,179,180,181],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":183,"name":184,"nameZh":6,"description":185,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":186,"categories":187,"keywords":190,"publishedAt":34},"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",[188,189],{"categoryNo":71,"categoryName":72,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":121,"categoryName":122,"taxonomyType":91,"taxonomyTypeDesc":92},[191,79,192,98,193,179,134,174,177,135,180],"Rules","writing rules","project rules"]