[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GPRZC6M1C32J85KNTE6AC":3,"skill-same:01M70GPRZC6M1C32J85KNTE6AC":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},"01M70GPRZC6M1C32J85KNTE6AC","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\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","use","technical","domain-specific","domain","integrations","contracts","patterns","edit","write","read","documentation","api","analysis","you","when","deduplication","files","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\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\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\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\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\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\u002Fplugins\u002Fstart\u002Fskills\u002Fknowledge-capture\u002Ftemplates\u002Fpattern-template.md",[93,102,110,118,126,134],{"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":97,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":101},"01M73H7XKBHE1ETQDZT94MF9HH","seedance-prompt-en","Write effective prompts for Jimeng Seedance 2.0 multimodal AI video generation. Use when users want to create video prompts using text, images, videos, and audio inputs with the @ reference system. Covers camera movements, effects replication, video extension, editing, music beat-matching, e-commerce ads, short dramas, and educational content.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fseedance-prompt-en\u002FSKILL.md",[],[],"2026-11-11 15:11:14",{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":106,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":101},"01M73GRE9998Q1DZWC71N41JWG","onepage-pdf","Convert an HTML page into a single continuous-page PDF (one tall page, no pagination breaks), preserving desktop layout, backgrounds and selectable text. Use when the user asks to turn an HTML file\u002Freport\u002Fproposal into a \"single-page PDF\", \"long PDF\", \"不分页 PDF\", \"单页 PDF\", \"长图式 PDF\", or complains that an HTML-to-PDF export breaks into pages or cuts content. Supports optional string redaction with leak verification.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonepage-pdf\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":114,"sourceHtmlUrl":115,"categories":116,"keywords":117,"publishedAt":101},"01M73GQG1KZDADVPV3MHAT1J5A","native-feel-cross-platform-desktop","Use when the user is designing, prototyping, or rewriting a desktop app that must run on multiple OSes (macOS + Windows, optionally Linux) AND feel indistinguishable from a native app to its users — fast launch, native windowing, native input handling, native materials. Trigger words include \"cross-platform desktop\", \"Electron alternative\", \"Tauri vs native\", \"WebView wrapper\", \"near-native performance\", \"Raycast architecture\", \"WebKit\u002FWebView2 quirks\", \"WKWebView\", \"system tray app\", \"global hotkey app\", \"launcher app\". Do NOT trigger this skill for pure web apps, pure mobile apps, or for greenfield projects that have no native-feel requirement.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fnative-feel-cross-platform-desktop\u002FSKILL.md",[],[],{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":122,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":101},"01M73G87PDNSMKG2FHWCYER6N8","gstack","Router for the gstack skill suite. (gstack)","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fgstack\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":130,"sourceHtmlUrl":131,"categories":132,"keywords":133,"publishedAt":101},"01M73G3EAQWKCM8DB8D0N0QSVG","fireworks-tech-graph","Use when the user wants to create any technical diagram - architecture, data flow, flowchart, sequence, agent\u002Fmemory, or concept map - and export as SVG+PNG. Trigger on: \"画图\" \"帮我画\" \"生成图\" \"做个图\" \"架构图\" \"流程图\" \"可视化一下\" \"出图\" \"generate diagram\" \"draw diagram\" \"visualize\" or any system\u002Fflow description the user wants illustrated.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Ffireworks-tech-graph\u002FSKILL.md",[],[],{"skillNo":135,"name":136,"nameZh":6,"description":137,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":138,"categories":139,"keywords":140,"publishedAt":101},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]