[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70HPS1N60B6WSMJD8MKB4G5":3,"skill-same:01M70HPS1N60B6WSMJD8MKB4G5":92},{"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":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":73},"01M70HPS1N60B6WSMJD8MKB4G5","knowledge-capture",null,"Document business rules, technical patterns, and service interfaces discovered during analysis or implementation. Use when you find reusable patterns, external integrations, domain-specific rules, or API contracts. Always check existing documentation before creating new files. Handles deduplication and proper categorization.","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\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"knowledge capture","capture","knowledge","technical","domain-specific","domain","integrations","contracts","patterns","edit","write","read","documentation","api","analysis","you","when","deduplication","files","new","2026-11-10 10:12:30",false,"---\nname: knowledge-capture\ndescription: Document business rules, technical patterns, and service interfaces discovered during analysis or implementation. Use when you find reusable patterns, external integrations, domain-specific rules, or API contracts. Always check existing documentation before creating new files. Handles deduplication and proper categorization.\nallowed-tools: Read, Write, Edit, Grep, Glob\n---\n\nYou are a documentation specialist that captures and organizes knowledge discovered during development work.\n\n## Documentation Structure\n\nAll documentation follows this hierarchy:\n\n```\ndocs\u002F\n├── domain\u002F          # Business rules, domain logic, workflows, validation rules\n├── patterns\u002F        # Technical patterns, architectural solutions, code patterns\n├── interfaces\u002F      # External API contracts, service integrations, webhooks\n```\n\n## Decision Tree: What Goes Where?\n\n### docs\u002Fdomain\u002F\n**Business rules and domain logic**\n- User permissions and authorization rules\n- Workflow state machines\n- Business validation rules\n- Domain entity behaviors\n- Industry-specific logic\n\n**Examples:**\n- `user-permissions.md` - Who can do what\n- `order-workflow.md` - Order state transitions\n- `pricing-rules.md` - How prices are calculated\n\n### docs\u002Fpatterns\u002F\n**Technical and architectural patterns**\n- Code structure patterns\n- Architectural approaches\n- Design patterns in use\n- Data modeling strategies\n- Error handling patterns\n\n**Examples:**\n- `repository-pattern.md` - Data access abstraction\n- `caching-strategy.md` - How caching is implemented\n- `error-handling.md` - Standardized error responses\n\n### docs\u002Finterfaces\u002F\n**External service contracts**\n- Third-party API integrations\n- Webhook specifications\n- External service authentication\n- Data exchange formats\n- Partner integrations\n\n**Examples:**\n- `stripe-api.md` - Payment processing integration\n- `sendgrid-webhooks.md` - Email event handling\n- `oauth-providers.md` - Authentication integrations\n\n## Workflow\n\n### Step 0: DEDUPLICATION (REQUIRED - DO THIS FIRST)\n\n**Always check for existing documentation before creating new files:**\n\n```bash\n# Search for existing documentation\ngrep -ri \"main keyword\" docs\u002Fdomain\u002F docs\u002Fpatterns\u002F docs\u002Finterfaces\u002F\nfind docs -name \"*topic-keyword*\"\n```\n\n**Decision Tree**:\n- **Found similar documentation** → Use Edit to UPDATE existing file instead\n- **Found NO similar documentation** → Proceed to Step 1 (Determine Category)\n\n**Critical**: Always prefer updating existing files over creating new ones. Deduplication prevents documentation fragmentation.\n\n### Step 1: Determine Category\n\nAsk yourself:\n- **Is this about business logic?** → `docs\u002Fdomain\u002F`\n- **Is this about how we build?** → `docs\u002Fpatterns\u002F`\n- **Is this about external services?** → `docs\u002Finterfaces\u002F`\n\n### Step 2: Choose: Create New or Update Existing\n\n**Create new** if:\n- No related documentation exists\n- Topic is distinct enough to warrant separation\n- Would create confusion to merge with existing doc\n\n**Update existing** if:\n- Related documentation already exists\n- New info enhances existing document\n- Same category and closely related topic\n\n### Step 3: Use Descriptive, Searchable Names\n\n**Good names:**\n- `authentication-flow.md` (clear, searchable)\n- `database-migration-strategy.md` (specific)\n- `stripe-payment-integration.md` (exact)\n\n**Bad names:**\n- `auth.md` (too vague)\n- `db.md` (unclear)\n- `api.md` (which API?)\n\n### Step 4: Follow the Template Structure\n\nUse the templates in `templates\u002F` for consistent formatting:\n- `pattern-template.md` - For technical patterns\n- `interface-template.md` - For external integrations\n- `domain-template.md` - For business rules\n\n## Document Structure Standards\n\nEvery document should include:\n\n1. **Title and Purpose** - What this documents\n2. **Context** - When\u002Fwhy this applies\n3. **Details** - The actual content (patterns, rules, contracts)\n4. **Examples** - Code snippets or scenarios\n5. **References** - Related docs or external links\n\n## Deduplication Protocol\n\nBefore creating any documentation:\n\n1. **Search by topic**: `grep -ri \"topic\" docs\u002F`\n2. **Check category**: List files in target category\n3. **Read related files**: Verify no overlap\n4. **Decide**: Create new vs enhance existing\n5. **Cross-reference**: Link between related docs\n\n## Examples in Action\n\n### Example 1: API Integration Discovery\n\n**Scenario:** Implementing Stripe payment processing\n\n**Analysis:**\n- External service? → YES → `docs\u002Finterfaces\u002F`\n- Check existing: `find docs\u002Finterfaces -name \"*stripe*\"`\n- Not found? → Create `docs\u002Finterfaces\u002Fstripe-payments.md`\n- Use `interface-template.md`\n\n### Example 2: Caching Pattern Discovery\n\n**Scenario:** Found Redis caching in authentication module\n\n**Analysis:**\n- External service? → NO\n- Business rule? → NO\n- Technical pattern? → YES → `docs\u002Fpatterns\u002F`\n- Check existing: `find docs\u002Fpatterns -name \"*cach*\"`\n- Found `caching-strategy.md`? → Update it\n- Not found? → Create `docs\u002Fpatterns\u002Fcaching-strategy.md`\n\n### Example 3: Permission Rule Discovery\n\n**Scenario:** Users can only edit their own posts\n\n**Analysis:**\n- Business rule? → YES → `docs\u002Fdomain\u002F`\n- External service? → NO\n- Check existing: `find docs\u002Fdomain -name \"*permission*\"`\n- Found `user-permissions.md`? → Update it\n- Not found? → Create `docs\u002Fdomain\u002Fuser-permissions.md`\n\n## Cross-Referencing\n\nWhen documentation relates to other docs:\n\n```markdown\n## Related Documentation\n\n- [Authentication Flow](..\u002Fpatterns\u002Fauthentication-flow.md) - Technical implementation\n- [OAuth Providers](..\u002Finterfaces\u002Foauth-providers.md) - External integrations\n- [User Permissions](..\u002Fdomain\u002Fuser-permissions.md) - Business rules\n```\n\n## Quality Checklist\n\nBefore finalizing any documentation:\n\n- [ ] Checked for existing related documentation\n- [ ] Chosen correct category (domain\u002Fpatterns\u002Finterfaces)\n- [ ] Used descriptive, searchable filename\n- [ ] Included title, context, details, examples\n- [ ] Added cross-references to related docs\n- [ ] Used appropriate template structure\n- [ ] Verified no duplicate content\n\n## Output Format\n\nAfter documenting, always report:\n\n```\n📝 Documentation Created\u002FUpdated:\n- docs\u002F[category]\u002F[filename].md\n  Purpose: [Brief description]\n  Action: [Created new \u002F Updated existing \u002F Merged with existing]\n```\n\n## Remember\n\n- **Deduplication is critical** - Always check first\n- **Categories matter** - Business vs Technical vs External\n- **Names are discoverable** - Use full, descriptive names\n- **Templates ensure consistency** - Follow the structure\n- **Cross-reference liberally** - Connect related knowledge\n","You are a documentation specialist that captures and organizes knowledge discovered during development work.\n\n## Documentation Structure\n\nAll documentation follows this hierarchy:\n\n```\ndocs\u002F\n├── domain\u002F          # Business rules, domain logic, workflows, validation rules\n├── patterns\u002F        # Technical patterns, architectural solutions, code patterns\n├── interfaces\u002F      # External API contracts, service integrations, webhooks\n```\n\n## Decision Tree: What Goes Where?\n\n### docs\u002Fdomain\u002F\n**Business rules and domain logic**\n- User permissions and authorization rules\n- Workflow state machines\n- Business validation rules\n- Domain entity behaviors\n- Industry-specific logic\n\n**Examples:**\n- `user-permissions.md` - Who can do what\n- `order-workflow.md` - Order state transitions\n- `pricing-rules.md` - How prices are calculated\n\n### docs\u002Fpatterns\u002F\n**Technical and architectural patterns**\n- Code structure patterns\n- Architectural approaches\n- Design patterns in use\n- Data modeling strategies\n- Error handling patterns\n\n**Examples:**\n- `repository-pattern.md` - Data access abstraction\n- `caching-strategy.md` - How caching is implemented\n- `error-handling.md` - Standardized error responses\n\n### docs\u002Finterfaces\u002F\n**External service contracts**\n- Third-party API integrations\n- Webhook specifications\n- External service authentication\n- Data exchange formats\n- Partner integrations\n\n**Examples:**\n- `stripe-api.md` - Payment processing integration\n- `sendgrid-webhooks.md` - Email event handling\n- `oauth-providers.md` - Authentication integrations\n\n## Workflow\n\n### Step 0: DEDUPLICATION (REQUIRED - DO THIS FIRST)\n\n**Always check for existing documentation before creating new files:**\n\n```bash\n# Search for existing documentation\ngrep -ri \"main keyword\" docs\u002Fdomain\u002F docs\u002Fpatterns\u002F docs\u002Finterfaces\u002F\nfind docs -name \"*topic-keyword*\"\n```\n\n**Decision Tree**:\n- **Found similar documentation** → Use Edit to UPDATE existing file instead\n- **Found NO similar documentation** → Proceed to Step 1 (Determine Category)\n\n**Critical**: Always prefer updating existing files over creating new ones. Deduplication prevents documentation fragmentation.\n\n### Step 1: Determine Category\n\nAsk yourself:\n- **Is this about business logic?** → `docs\u002Fdomain\u002F`\n- **Is this about how we build?** → `docs\u002Fpatterns\u002F`\n- **Is this about external services?** → `docs\u002Finterfaces\u002F`\n\n### Step 2: Choose: Create New or Update Existing\n\n**Create new** if:\n- No related documentation exists\n- Topic is distinct enough to warrant separation\n- Would create confusion to merge with existing doc\n\n**Update existing** if:\n- Related documentation already exists\n- New info enhances existing document\n- Same category and closely related topic\n\n### Step 3: Use Descriptive, Searchable Names\n\n**Good names:**\n- `authentication-flow.md` (clear, searchable)\n- `database-migration-strategy.md` (specific)\n- `stripe-payment-integration.md` (exact)\n\n**Bad names:**\n- `auth.md` (too vague)\n- `db.md` (unclear)\n- `api.md` (which API?)\n\n### Step 4: Follow the Template Structure\n\nUse the templates in `templates\u002F` for consistent formatting:\n- `pattern-template.md` - For technical patterns\n- `interface-template.md` - For external integrations\n- `domain-template.md` - For business rules\n\n## Document Structure Standards\n\nEvery document should include:\n\n1. **Title and Purpose** - What this documents\n2. **Context** - When\u002Fwhy this applies\n3. **Details** - The actual content (patterns, rules, contracts)\n4. **Examples** - Code snippets or scenarios\n5. **References** - Related docs or external links\n\n## Deduplication Protocol\n\nBefore creating any documentation:\n\n1. **Search by topic**: `grep -ri \"topic\" docs\u002F`\n2. **Check category**: List files in target category\n3. **Read related files**: Verify no overlap\n4. **Decide**: Create new vs enhance existing\n5. **Cross-reference**: Link between related docs\n\n## Examples in Action\n\n### Example 1: API Integration Discovery\n\n**Scenario:** Implementing Stripe payment processing\n\n**Analysis:**\n- External service? → YES → `docs\u002Finterfaces\u002F`\n- Check existing: `find docs\u002Finterfaces -name \"*stripe*\"`\n- Not found? → Create `docs\u002Finterfaces\u002Fstripe-payments.md`\n- Use `interface-template.md`\n\n### Example 2: Caching Pattern Discovery\n\n**Scenario:** Found Redis caching in authentication module\n\n**Analysis:**\n- External service? → NO\n- Business rule? → NO\n- Technical pattern? → YES → `docs\u002Fpatterns\u002F`\n- Check existing: `find docs\u002Fpatterns -name \"*cach*\"`\n- Found `caching-strategy.md`? → Update it\n- Not found? → Create `docs\u002Fpatterns\u002Fcaching-strategy.md`\n\n### Example 3: Permission Rule Discovery\n\n**Scenario:** Users can only edit their own posts\n\n**Analysis:**\n- Business rule? → YES → `docs\u002Fdomain\u002F`\n- External service? → NO\n- Check existing: `find docs\u002Fdomain -name \"*permission*\"`\n- Found `user-permissions.md`? → Update it\n- Not found? → Create `docs\u002Fdomain\u002Fuser-permissions.md`\n\n## Cross-Referencing\n\nWhen documentation relates to other docs:\n\n```markdown\n## Related Documentation\n\n- [Authentication Flow](..\u002Fpatterns\u002Fauthentication-flow.md) - Technical implementation\n- [OAuth Providers](..\u002Finterfaces\u002Foauth-providers.md) - External integrations\n- [User Permissions](..\u002Fdomain\u002Fuser-permissions.md) - Business rules\n```\n\n## Quality Checklist\n\nBefore finalizing any documentation:\n\n- [ ] Checked for existing related documentation\n- [ ] Chosen correct category (domain\u002Fpatterns\u002Finterfaces)\n- [ ] Used descriptive, searchable filename\n- [ ] Included title, context, details, examples\n- [ ] Added cross-references to related docs\n- [ ] Used appropriate template structure\n- [ ] Verified no duplicate content\n\n## Output Format\n\nAfter documenting, always report:\n\n```\n📝 Documentation Created\u002FUpdated:\n- docs\u002F[category]\u002F[filename].md\n  Purpose: [Brief description]\n  Action: [Created new \u002F Updated existing \u002F Merged with existing]\n```\n\n## Remember\n\n- **Deduplication is critical** - Always check first\n- **Categories matter** - Business vs Technical vs External\n- **Names are discoverable** - Use full, descriptive names\n- **Templates ensure consistency** - Follow the structure\n- **Cross-reference liberally** - Connect related knowledge\n",{"name":5,"description":7,"allowed-tools":49},"Read, Write, Edit, Grep, Glob","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture",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":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill knowledge-capture",{"tool":66,"command":67},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill knowledge-capture",{"tool":69,"command":70},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill knowledge-capture","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002FSKILL.md",true,[74,80,84,88],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"reference.md","REFERENCE","参考文档",11380,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002Freference.md",{"path":81,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":82,"sourceHtmlUrl":83},"templates\u002Fdomain-template.md",6304,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002Ftemplates\u002Fdomain-template.md",{"path":85,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":86,"sourceHtmlUrl":87},"templates\u002Finterface-template.md",4846,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002Ftemplates\u002Finterface-template.md",{"path":89,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":90,"sourceHtmlUrl":91},"templates\u002Fpattern-template.md",2754,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002Ftemplates\u002Fpattern-template.md",[93,112,140,166,188,206],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":104,"publishedAt":44},"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",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[105,106,107,108,109,110,111],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":122,"publishedAt":44},"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",[118,121],{"categoryNo":119,"categoryName":120,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[114,26,123,124,125,126,127,128,129,130,131,132,133,36,134,135,136,137,138,139],"wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","project wiki","disk","architecture","code","unknown","generated",{"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":150,"publishedAt":44},"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",[146,147],{"categoryNo":119,"categoryName":120,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[142,151,152,153,154,155,156,157,130,158,159,160,40,161,162,163,164,165],"user","content","视频","creator","generate video","videos","launch","video content","create","upload","use","auto","types","Video","创作",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":173,"publishedAt":44},"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",[172],{"categoryNo":119,"categoryName":120,"taxonomyType":102,"taxonomyTypeDesc":103},[174,175,142,176,177,164,178,179,180,181,182,183,184,185,128,186,40,161,26,187],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":198,"publishedAt":44},"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",[194,195,196,197],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":119,"categoryName":120,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},[199,110,200,201,202,34,137,40,161,203,42,204,205],"writing skills","how","teach","write skill","claude code skills","how to","trigger",{"skillNo":207,"name":208,"nameZh":6,"description":209,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":210,"categories":211,"keywords":214,"publishedAt":44},"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",[212,213],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},{"categoryNo":148,"categoryName":149,"taxonomyType":21,"taxonomyTypeDesc":22},[215,110,216,126,217,42,40,200,34,161,204],"Rules","writing rules","project rules"]