[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NDE128HS4PR4JWCEPTP12":3,"skill-same:01M70NDE128HS4PR4JWCEPTP12":93},{"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":55,"commitSha":56,"skillDirectory":57,"forksCount":58,"repositoryHtmlUrl":59,"repositoryHomepageUrl":60,"ownerHtmlUrl":61,"ownerBlogUrl":62,"ownerDescription":63,"updatedAt":64,"install":65,"resources":78},"01M70NDE128HS4PR4JWCEPTP12","architecture-design",null,"Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs\u002Fspecs\u002F. Includes validation checklist, consistency verification, and overlap detection.","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\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-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","architecture","architecture design","decisions","use","technical","system","consistency","analyzing","edit","write","read","designing architecture","verification","create","sdd","components","when","documents","files","2026-11-10 10:12:30",false,"---\nname: architecture-design\ndescription: Create and validate solution design documents (SDD). Use when designing architecture, defining interfaces, documenting technical decisions, analyzing system components, or working on solution-design.md files in docs\u002Fspecs\u002F. Includes validation checklist, consistency verification, and overlap detection.\nallowed-tools: Read, Write, Edit, Task, TodoWrite, Grep, Glob\n---\n\n# Solution Design Skill\n\nYou are a solution design specialist that creates and validates SDDs focusing on HOW the solution will be built through technical architecture and design decisions.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Create a new SDD** from the template\n- **Complete sections** in an existing solution-design.md\n- **Validate SDD completeness** and consistency\n- **Design architecture** and document technical decisions\n- **Work on any `solution-design.md`** file in docs\u002Fspecs\u002F\n\n**IMPORTANT:** You MUST NEVER perform actual implementation or code changes. Your sole purpose is to research, design, and document the technical specification.\n\n## Template\n\nThe SDD template is at [template.md](template.md). Use this structure exactly.\n\n**To write template to spec directory:**\n1. Read the template: `plugins\u002Fstart\u002Fskills\u002Fsolution-design\u002Ftemplate.md`\n2. Write to spec directory: `docs\u002Fspecs\u002F[ID]-[name]\u002Fsolution-design.md`\n\n## SDD Focus Areas\n\nWhen working on an SDD, focus on:\n- **HOW** it will be built (architecture, patterns)\n- **WHERE** code lives (directory structure, components)\n- **WHAT** interfaces exist (APIs, data models, integrations)\n- **WHY** decisions were made (ADRs with rationale)\n\n**Ensure alignment with:**\n- PRD requirements (every requirement should be addressable)\n- Existing codebase patterns (don't reinvent the wheel)\n- Constraints identified in the PRD\n\n## Cycle Pattern\n\nFor each section requiring clarification, follow this iterative process:\n\n### 1. Discovery Phase\n- **Read the completed PRD** to understand requirements\n- **Explore the codebase** to understand existing patterns\n- **Launch parallel specialist agents** to investigate:\n  - Architecture patterns and best practices\n  - Database\u002Fdata model design\n  - API design and interface contracts\n  - Security implications\n  - Performance characteristics\n  - Integration approaches\n\n### 2. Documentation Phase\n- **Update the SDD** with research findings\n- **Replace [NEEDS CLARIFICATION] markers** with actual content\n- Focus only on current section being processed\n- Follow template structure exactly - never add or remove sections\n\n### 3. Review Phase\n- **Present ALL agent findings** to user (complete responses, not summaries)\n- Show conflicting recommendations or trade-offs\n- Present proposed architecture with rationale\n- Highlight decisions needing user confirmation (ADRs)\n- **Wait for user confirmation** before next cycle\n\n**Ask yourself each cycle:**\n1. Have I read and understood the relevant PRD requirements?\n2. Have I explored existing codebase patterns?\n3. Have I launched parallel specialist agents?\n4. Have I updated the SDD according to findings?\n5. Have I presented options and trade-offs to the user?\n6. Have I received user confirmation on architecture decisions?\n\n## Final Validation\n\nBefore completing the SDD, validate through systematic checks:\n\n### Overlap and Conflict Detection\nLaunch specialists to identify:\n- **Component Overlap**: Are responsibilities duplicated across components?\n- **Interface Conflicts**: Do multiple interfaces serve the same purpose?\n- **Pattern Inconsistency**: Are there conflicting architectural patterns?\n- **Data Redundancy**: Is data duplicated without justification?\n\n### Coverage Analysis\nLaunch specialists to verify:\n- **PRD Coverage**: Are ALL requirements from the PRD addressed?\n- **Component Completeness**: Are all necessary components defined (UI, business logic, data, integration)?\n- **Interface Completeness**: Are all external and internal interfaces specified?\n- **Cross-Cutting Concerns**: Are security, error handling, logging, and performance addressed?\n- **Deployment Coverage**: Are all deployment, configuration, and operational aspects covered?\n\n### Boundary Validation\nLaunch specialists to validate:\n- **Component Boundaries**: Is each component's responsibility clearly defined and bounded?\n- **Layer Separation**: Are architectural layers (presentation, business, data) properly separated?\n- **Integration Points**: Are all system boundaries and integration points explicitly documented?\n- **Dependency Direction**: Do dependencies flow in the correct direction (no circular dependencies)?\n\n### Consistency Verification\nLaunch specialists to check:\n- **PRD Alignment**: Does every SDD design decision trace back to a PRD requirement?\n- **Naming Consistency**: Are components, interfaces, and concepts named consistently?\n- **Pattern Adherence**: Are architectural patterns applied consistently throughout?\n- **No Context Drift**: Has the design stayed true to the original business requirements?\n\n## Validation Checklist\n\nSee [validation.md](validation.md) for the complete checklist. Key gates:\n\n- [ ] All required sections are complete\n- [ ] No [NEEDS CLARIFICATION] markers remain\n- [ ] All context sources are listed with relevance ratings\n- [ ] Project commands are discovered from actual project files\n- [ ] Constraints → Strategy → Design → Implementation path is logical\n- [ ] Architecture pattern is clearly stated with rationale\n- [ ] Every component in diagram has directory mapping\n- [ ] Every interface has specification\n- [ ] Error handling covers all error types\n- [ ] Quality requirements are specific and measurable\n- [ ] Every quality requirement has test coverage\n- [ ] **All architecture decisions confirmed by user**\n- [ ] Component names consistent across diagrams\n- [ ] A developer could implement from this design\n\n## Architecture Decision Records (ADRs)\n\nEvery significant decision needs user confirmation:\n\n```markdown\n- [ ] ADR-1 [Decision Name]: [Choice made]\n  - Rationale: [Why this over alternatives]\n  - Trade-offs: [What we accept]\n  - User confirmed: _Pending_\n```\n\n**Never proceed with implementation-impacting decisions without user confirmation.**\n\n## Output Format\n\nAfter SDD work, report:\n\n```\n🏗️ SDD Status: [spec-id]-[name]\n\nArchitecture:\n- Pattern: [Selected pattern]\n- Key Components: [List]\n- External Integrations: [List]\n\nSections Completed:\n- [Section 1]: ✅ Complete\n- [Section 2]: ⚠️ Needs user decision on [topic]\n- [Section 3]: 🔄 In progress\n\nADRs:\n- [ADR-1]: ✅ Confirmed\n- [ADR-2]: ⏳ Pending confirmation\n\nValidation Status:\n- [X] items passed\n- [Y] items pending\n\nNext Steps:\n- [What needs to happen next]\n```\n\n## Examples\n\nSee [examples\u002Farchitecture-examples.md](examples\u002Farchitecture-examples.md) for reference.\n","# Solution Design Skill\n\nYou are a solution design specialist that creates and validates SDDs focusing on HOW the solution will be built through technical architecture and design decisions.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Create a new SDD** from the template\n- **Complete sections** in an existing solution-design.md\n- **Validate SDD completeness** and consistency\n- **Design architecture** and document technical decisions\n- **Work on any `solution-design.md`** file in docs\u002Fspecs\u002F\n\n**IMPORTANT:** You MUST NEVER perform actual implementation or code changes. Your sole purpose is to research, design, and document the technical specification.\n\n## Template\n\nThe SDD template is at [template.md](template.md). Use this structure exactly.\n\n**To write template to spec directory:**\n1. Read the template: `plugins\u002Fstart\u002Fskills\u002Fsolution-design\u002Ftemplate.md`\n2. Write to spec directory: `docs\u002Fspecs\u002F[ID]-[name]\u002Fsolution-design.md`\n\n## SDD Focus Areas\n\nWhen working on an SDD, focus on:\n- **HOW** it will be built (architecture, patterns)\n- **WHERE** code lives (directory structure, components)\n- **WHAT** interfaces exist (APIs, data models, integrations)\n- **WHY** decisions were made (ADRs with rationale)\n\n**Ensure alignment with:**\n- PRD requirements (every requirement should be addressable)\n- Existing codebase patterns (don't reinvent the wheel)\n- Constraints identified in the PRD\n\n## Cycle Pattern\n\nFor each section requiring clarification, follow this iterative process:\n\n### 1. Discovery Phase\n- **Read the completed PRD** to understand requirements\n- **Explore the codebase** to understand existing patterns\n- **Launch parallel specialist agents** to investigate:\n  - Architecture patterns and best practices\n  - Database\u002Fdata model design\n  - API design and interface contracts\n  - Security implications\n  - Performance characteristics\n  - Integration approaches\n\n### 2. Documentation Phase\n- **Update the SDD** with research findings\n- **Replace [NEEDS CLARIFICATION] markers** with actual content\n- Focus only on current section being processed\n- Follow template structure exactly - never add or remove sections\n\n### 3. Review Phase\n- **Present ALL agent findings** to user (complete responses, not summaries)\n- Show conflicting recommendations or trade-offs\n- Present proposed architecture with rationale\n- Highlight decisions needing user confirmation (ADRs)\n- **Wait for user confirmation** before next cycle\n\n**Ask yourself each cycle:**\n1. Have I read and understood the relevant PRD requirements?\n2. Have I explored existing codebase patterns?\n3. Have I launched parallel specialist agents?\n4. Have I updated the SDD according to findings?\n5. Have I presented options and trade-offs to the user?\n6. Have I received user confirmation on architecture decisions?\n\n## Final Validation\n\nBefore completing the SDD, validate through systematic checks:\n\n### Overlap and Conflict Detection\nLaunch specialists to identify:\n- **Component Overlap**: Are responsibilities duplicated across components?\n- **Interface Conflicts**: Do multiple interfaces serve the same purpose?\n- **Pattern Inconsistency**: Are there conflicting architectural patterns?\n- **Data Redundancy**: Is data duplicated without justification?\n\n### Coverage Analysis\nLaunch specialists to verify:\n- **PRD Coverage**: Are ALL requirements from the PRD addressed?\n- **Component Completeness**: Are all necessary components defined (UI, business logic, data, integration)?\n- **Interface Completeness**: Are all external and internal interfaces specified?\n- **Cross-Cutting Concerns**: Are security, error handling, logging, and performance addressed?\n- **Deployment Coverage**: Are all deployment, configuration, and operational aspects covered?\n\n### Boundary Validation\nLaunch specialists to validate:\n- **Component Boundaries**: Is each component's responsibility clearly defined and bounded?\n- **Layer Separation**: Are architectural layers (presentation, business, data) properly separated?\n- **Integration Points**: Are all system boundaries and integration points explicitly documented?\n- **Dependency Direction**: Do dependencies flow in the correct direction (no circular dependencies)?\n\n### Consistency Verification\nLaunch specialists to check:\n- **PRD Alignment**: Does every SDD design decision trace back to a PRD requirement?\n- **Naming Consistency**: Are components, interfaces, and concepts named consistently?\n- **Pattern Adherence**: Are architectural patterns applied consistently throughout?\n- **No Context Drift**: Has the design stayed true to the original business requirements?\n\n## Validation Checklist\n\nSee [validation.md](validation.md) for the complete checklist. Key gates:\n\n- [ ] All required sections are complete\n- [ ] No [NEEDS CLARIFICATION] markers remain\n- [ ] All context sources are listed with relevance ratings\n- [ ] Project commands are discovered from actual project files\n- [ ] Constraints → Strategy → Design → Implementation path is logical\n- [ ] Architecture pattern is clearly stated with rationale\n- [ ] Every component in diagram has directory mapping\n- [ ] Every interface has specification\n- [ ] Error handling covers all error types\n- [ ] Quality requirements are specific and measurable\n- [ ] Every quality requirement has test coverage\n- [ ] **All architecture decisions confirmed by user**\n- [ ] Component names consistent across diagrams\n- [ ] A developer could implement from this design\n\n## Architecture Decision Records (ADRs)\n\nEvery significant decision needs user confirmation:\n\n```markdown\n- [ ] ADR-1 [Decision Name]: [Choice made]\n  - Rationale: [Why this over alternatives]\n  - Trade-offs: [What we accept]\n  - User confirmed: _Pending_\n```\n\n**Never proceed with implementation-impacting decisions without user confirmation.**\n\n## Output Format\n\nAfter SDD work, report:\n\n```\n🏗️ SDD Status: [spec-id]-[name]\n\nArchitecture:\n- Pattern: [Selected pattern]\n- Key Components: [List]\n- External Integrations: [List]\n\nSections Completed:\n- [Section 1]: ✅ Complete\n- [Section 2]: ⚠️ Needs user decision on [topic]\n- [Section 3]: 🔄 In progress\n\nADRs:\n- [ADR-1]: ✅ Confirmed\n- [ADR-2]: ⏳ Pending confirmation\n\nValidation Status:\n- [X] items passed\n- [Y] items pending\n\nNext Steps:\n- [What needs to happen next]\n```\n\n## Examples\n\nSee [examples\u002Farchitecture-examples.md](examples\u002Farchitecture-examples.md) for reference.\n",{"name":5,"description":7,"allowed-tools":54},"Read, Write, Edit, Task, TodoWrite, Grep, Glob","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-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":66,"prompt":76,"zipAvailable":77},[67,70,73],{"tool":68,"command":69},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill architecture-design",{"tool":71,"command":72},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill architecture-design",{"tool":74,"command":75},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill architecture-design","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-design\u002FSKILL.md",true,[79,85,89],{"path":80,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":83,"sourceHtmlUrl":84},"examples\u002Farchitecture-examples.md","REFERENCE","参考文档",4968,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-design\u002Fexamples\u002Farchitecture-examples.md",{"path":86,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":87,"sourceHtmlUrl":88},"template.md",28628,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-design\u002Ftemplate.md",{"path":90,"resourceType":81,"resourceTypeDesc":82,"sizeBytes":91,"sourceHtmlUrl":92},"validation.md",4312,"https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Farchitecture-design\u002Fvalidation.md",[94,103,111,119,127,135],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":102},"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":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":107,"sourceHtmlUrl":108,"categories":109,"keywords":110,"publishedAt":102},"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":112,"name":113,"nameZh":6,"description":114,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":115,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":102},"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":123,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":102},"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":128,"name":129,"nameZh":6,"description":130,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":131,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":102},"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":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":102},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]