[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70GPNY0SD7DYTYBKXWQPKDM":3,"skill-same:01M70GPNY0SD7DYTYBKXWQPKDM":75},{"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":51,"commitSha":52,"skillDirectory":53,"forksCount":54,"repositoryHtmlUrl":55,"repositoryHomepageUrl":56,"ownerHtmlUrl":57,"ownerBlogUrl":58,"ownerDescription":59,"updatedAt":60,"install":61,"resources":74},"01M70GPNY0SD7DYTYBKXWQPKDM","implementation-verification",null,"Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\nverifying specification compliance, checking interface contracts, validating\narchitecture decisions, detecting deviations, or ensuring implementations\nmatch documented requirements. Provides structured compliance reporting.","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\u002Fimplementation-verification\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"implementation verification","verification","implementation","specification","when","detecting","interface","specifications","requirements","sdd","task","contracts","validate","use","read","decisions","plan","compliance","reporting","architecture","2026-11-10 10:12:30",false,"---\nname: implementation-verification\ndescription: |\n  Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\n  verifying specification compliance, checking interface contracts, validating\n  architecture decisions, detecting deviations, or ensuring implementations\n  match documented requirements. Provides structured compliance reporting.\nallowed-tools: Task, Read, Grep, Glob\n---\n\n# Specification Compliance Skill\n\nYou are a specification compliance validator that ensures implementations match documented requirements exactly.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Verify SDD compliance** during implementation\n- **Check interface contracts** match specifications\n- **Validate architecture decisions** are followed\n- **Detect deviations** from documented requirements\n- **Report compliance status** at checkpoints\n\n## Core Principle\n\nEvery implementation must match the specification exactly. Deviations require explicit acknowledgment before proceeding.\n\n## Specification Document Hierarchy\n\n```\ndocs\u002Fspecs\u002F[ID]-[name]\u002F\n├── product-requirements.md   # WHAT and WHY (business requirements)\n├── solution-design.md        # HOW (technical design, interfaces, patterns)\n└── implementation-plan.md    # WHEN (execution sequence, phases)\n```\n\n## Compliance Verification Process\n\n### Pre-Implementation Check\n\nBefore implementing any task:\n\n1. **Extract SDD references** from PLAN.md task: `[ref: SDD\u002FSection X.Y]`\n2. **Read referenced sections** from solution-design.md\n3. **Identify requirements**:\n   - Interface contracts\n   - Data structures\n   - Business logic flows\n   - Architecture decisions\n   - Quality requirements\n\n### During Implementation\n\nFor each task, verify:\n\n- [ ] **Interface contracts match** - Function signatures, parameters, return types\n- [ ] **Data structures align** - Schema, types, relationships as specified\n- [ ] **Business logic follows** - Defined flows and rules from SDD\n- [ ] **Architecture respected** - Patterns, layers, dependencies as designed\n- [ ] **Quality met** - Performance, security requirements from SDD\n\n### Post-Implementation Validation\n\nAfter task completion:\n\n1. **Compare implementation to specification**\n2. **Document any deviations found**\n3. **Classify deviations by severity**\n4. **Report compliance status**\n\n## Deviation Classification\n\n### Critical Deviations (🔴)\n\nMust fix before proceeding:\n- Interface contract violations\n- Missing required functionality\n- Security requirement breaches\n- Breaking architectural constraints\n\n### Notable Deviations (🟡)\n\nRequire acknowledgment:\n- Implementation differs but functionally equivalent\n- Enhancement beyond specification\n- Simplified approach with same outcome\n\n### Acceptable Variations (🟢)\n\nCan proceed:\n- Internal implementation details differ\n- Optimizations within spec boundaries\n- Naming\u002Fstyle variations\n\n## Compliance Report Format\n\n### Per-Task Report\n\n```\n📋 Specification Compliance: [Task Name]\n\nSDD Reference: Section [X.Y]\n\nRequirements Checked:\n✅ Interface: [function\u002Fendpoint] matches signature\n✅ Data: [model\u002Fschema] matches structure\n✅ Logic: [flow\u002Frule] implemented correctly\n🟡 Enhancement: [description] - beyond spec but compatible\n🔴 Deviation: [description] - requires fix\n\nStatus: [COMPLIANT \u002F DEVIATION FOUND \u002F NEEDS REVIEW]\n```\n\n### Phase Completion Report\n\n```\n📊 Phase [X] Specification Compliance Summary\n\nTasks Validated: [N]\n- Fully Compliant: [X]\n- With Acceptable Variations: [Y]\n- With Notable Deviations: [Z]\n- Critical Issues: [W]\n\nSDD Sections Covered:\n- Section 2.1: ✅ Compliant\n- Section 2.2: ✅ Compliant\n- Section 3.1: 🟡 Variation documented\n\nCritical Issues (if any):\n1. [Description and required fix]\n\nRecommendation: [PROCEED \u002F FIX REQUIRED \u002F USER REVIEW]\n```\n\n## Interface Verification\n\n### API Endpoints\n\n```\nVerifying: POST \u002Fapi\u002Fusers\nSDD Spec: Section 4.2.1\n\nRequest Schema:\n  ✅ body.email: string (required)\n  ✅ body.password: string (min 8 chars)\n  🔴 body.role: missing (spec requires optional role param)\n\nResponse Schema:\n  ✅ 201: { id, email, createdAt }\n  ✅ 400: { error: string }\n  🟡 409: Added conflict handling (not in spec, beneficial)\n```\n\n### Data Models\n\n```\nVerifying: User Model\nSDD Spec: Section 3.1.2\n\nFields:\n  ✅ id: UUID (primary key)\n  ✅ email: string (unique)\n  ✅ passwordHash: string\n  🟡 lastLoginAt: timestamp (added, not in spec)\n  🔴 role: enum (missing from implementation)\n\nRelationships:\n  ✅ hasMany: sessions\n  ✅ belongsTo: organization\n```\n\n## Architecture Decision Verification\n\nFor each ADR in SDD:\n\n```\nADR-1: [Decision Title]\nImplementation Status:\n\nDecision: [What was decided]\nEvidence: [Where implemented]\nCompliance: [Matched \u002F Deviated]\n\nIf deviated:\n  Deviation: [What differs]\n  Impact: [Consequences]\n  Action: [Fix \u002F Accept with rationale]\n```\n\n## Validation Commands\n\nRun these at checkpoints:\n\n```bash\n# Type checking (if TypeScript)\nnpm run typecheck\n\n# Linting\nnpm run lint\n\n# Test suite\nnpm test\n\n# Build verification\nnpm run build\n```\n\n## Compliance Gates\n\n### Before Proceeding to Next Phase\n\nAll must be true:\n- [ ] All critical deviations resolved\n- [ ] Notable deviations acknowledged by user\n- [ ] Validation commands pass\n- [ ] SDD coverage for phase is complete\n\n### Before Final Completion\n\n- [ ] All phases compliant\n- [ ] All interfaces verified\n- [ ] All architecture decisions respected\n- [ ] Quality requirements met\n- [ ] User confirmed any variations\n\n## Output Format\n\nWhen validating compliance:\n\n```\n📋 Specification Compliance Check\n\nContext: [What's being validated]\nSDD Reference: [Section(s)]\n\nVerification Results:\n[List of checks with status]\n\nDeviations:\n[If any, with classification]\n\nRecommendation: [Action to take]\n\nStatus: [COMPLIANT \u002F NEEDS FIX \u002F USER REVIEW]\n```\n\n## Quick Reference\n\n### Always Check\n- Interface signatures match exactly\n- Required fields are present\n- Business logic follows specified flows\n- Architecture patterns are respected\n\n### Document Deviations\n- What differs from spec\n- Why it differs (if known)\n- Impact assessment\n- Recommended action\n\n### Gate Compliance\n- Critical = must fix\n- Notable = must acknowledge\n- Acceptable = can proceed\n","# Specification Compliance Skill\n\nYou are a specification compliance validator that ensures implementations match documented requirements exactly.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Verify SDD compliance** during implementation\n- **Check interface contracts** match specifications\n- **Validate architecture decisions** are followed\n- **Detect deviations** from documented requirements\n- **Report compliance status** at checkpoints\n\n## Core Principle\n\nEvery implementation must match the specification exactly. Deviations require explicit acknowledgment before proceeding.\n\n## Specification Document Hierarchy\n\n```\ndocs\u002Fspecs\u002F[ID]-[name]\u002F\n├── product-requirements.md   # WHAT and WHY (business requirements)\n├── solution-design.md        # HOW (technical design, interfaces, patterns)\n└── implementation-plan.md    # WHEN (execution sequence, phases)\n```\n\n## Compliance Verification Process\n\n### Pre-Implementation Check\n\nBefore implementing any task:\n\n1. **Extract SDD references** from PLAN.md task: `[ref: SDD\u002FSection X.Y]`\n2. **Read referenced sections** from solution-design.md\n3. **Identify requirements**:\n   - Interface contracts\n   - Data structures\n   - Business logic flows\n   - Architecture decisions\n   - Quality requirements\n\n### During Implementation\n\nFor each task, verify:\n\n- [ ] **Interface contracts match** - Function signatures, parameters, return types\n- [ ] **Data structures align** - Schema, types, relationships as specified\n- [ ] **Business logic follows** - Defined flows and rules from SDD\n- [ ] **Architecture respected** - Patterns, layers, dependencies as designed\n- [ ] **Quality met** - Performance, security requirements from SDD\n\n### Post-Implementation Validation\n\nAfter task completion:\n\n1. **Compare implementation to specification**\n2. **Document any deviations found**\n3. **Classify deviations by severity**\n4. **Report compliance status**\n\n## Deviation Classification\n\n### Critical Deviations (🔴)\n\nMust fix before proceeding:\n- Interface contract violations\n- Missing required functionality\n- Security requirement breaches\n- Breaking architectural constraints\n\n### Notable Deviations (🟡)\n\nRequire acknowledgment:\n- Implementation differs but functionally equivalent\n- Enhancement beyond specification\n- Simplified approach with same outcome\n\n### Acceptable Variations (🟢)\n\nCan proceed:\n- Internal implementation details differ\n- Optimizations within spec boundaries\n- Naming\u002Fstyle variations\n\n## Compliance Report Format\n\n### Per-Task Report\n\n```\n📋 Specification Compliance: [Task Name]\n\nSDD Reference: Section [X.Y]\n\nRequirements Checked:\n✅ Interface: [function\u002Fendpoint] matches signature\n✅ Data: [model\u002Fschema] matches structure\n✅ Logic: [flow\u002Frule] implemented correctly\n🟡 Enhancement: [description] - beyond spec but compatible\n🔴 Deviation: [description] - requires fix\n\nStatus: [COMPLIANT \u002F DEVIATION FOUND \u002F NEEDS REVIEW]\n```\n\n### Phase Completion Report\n\n```\n📊 Phase [X] Specification Compliance Summary\n\nTasks Validated: [N]\n- Fully Compliant: [X]\n- With Acceptable Variations: [Y]\n- With Notable Deviations: [Z]\n- Critical Issues: [W]\n\nSDD Sections Covered:\n- Section 2.1: ✅ Compliant\n- Section 2.2: ✅ Compliant\n- Section 3.1: 🟡 Variation documented\n\nCritical Issues (if any):\n1. [Description and required fix]\n\nRecommendation: [PROCEED \u002F FIX REQUIRED \u002F USER REVIEW]\n```\n\n## Interface Verification\n\n### API Endpoints\n\n```\nVerifying: POST \u002Fapi\u002Fusers\nSDD Spec: Section 4.2.1\n\nRequest Schema:\n  ✅ body.email: string (required)\n  ✅ body.password: string (min 8 chars)\n  🔴 body.role: missing (spec requires optional role param)\n\nResponse Schema:\n  ✅ 201: { id, email, createdAt }\n  ✅ 400: { error: string }\n  🟡 409: Added conflict handling (not in spec, beneficial)\n```\n\n### Data Models\n\n```\nVerifying: User Model\nSDD Spec: Section 3.1.2\n\nFields:\n  ✅ id: UUID (primary key)\n  ✅ email: string (unique)\n  ✅ passwordHash: string\n  🟡 lastLoginAt: timestamp (added, not in spec)\n  🔴 role: enum (missing from implementation)\n\nRelationships:\n  ✅ hasMany: sessions\n  ✅ belongsTo: organization\n```\n\n## Architecture Decision Verification\n\nFor each ADR in SDD:\n\n```\nADR-1: [Decision Title]\nImplementation Status:\n\nDecision: [What was decided]\nEvidence: [Where implemented]\nCompliance: [Matched \u002F Deviated]\n\nIf deviated:\n  Deviation: [What differs]\n  Impact: [Consequences]\n  Action: [Fix \u002F Accept with rationale]\n```\n\n## Validation Commands\n\nRun these at checkpoints:\n\n```bash\n# Type checking (if TypeScript)\nnpm run typecheck\n\n# Linting\nnpm run lint\n\n# Test suite\nnpm test\n\n# Build verification\nnpm run build\n```\n\n## Compliance Gates\n\n### Before Proceeding to Next Phase\n\nAll must be true:\n- [ ] All critical deviations resolved\n- [ ] Notable deviations acknowledged by user\n- [ ] Validation commands pass\n- [ ] SDD coverage for phase is complete\n\n### Before Final Completion\n\n- [ ] All phases compliant\n- [ ] All interfaces verified\n- [ ] All architecture decisions respected\n- [ ] Quality requirements met\n- [ ] User confirmed any variations\n\n## Output Format\n\nWhen validating compliance:\n\n```\n📋 Specification Compliance Check\n\nContext: [What's being validated]\nSDD Reference: [Section(s)]\n\nVerification Results:\n[List of checks with status]\n\nDeviations:\n[If any, with classification]\n\nRecommendation: [Action to take]\n\nStatus: [COMPLIANT \u002F NEEDS FIX \u002F USER REVIEW]\n```\n\n## Quick Reference\n\n### Always Check\n- Interface signatures match exactly\n- Required fields are present\n- Business logic follows specified flows\n- Architecture patterns are respected\n\n### Document Deviations\n- What differs from spec\n- Why it differs (if known)\n- Impact assessment\n- Recommended action\n\n### Gate Compliance\n- Critical = must fix\n- Notable = must acknowledge\n- Acceptable = can proceed\n",{"name":5,"description":49,"allowed-tools":50},"Validate implementation against specifications (PRD\u002FSDD\u002FPLAN). Use when\nverifying specification compliance, checking interface contracts, validating\narchitecture decisions, detecting deviations, or ensuring implementations\nmatch documented requirements. Provides structured compliance reporting.\n","Task, Read, Grep, Glob","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002F_collections\u002Fplugins\u002Fstart\u002Fskills\u002Fimplementation-verification",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification",{"tool":67,"command":68},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification",{"tool":70,"command":71},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill implementation-verification","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002F_collections\u002Fplugins\u002Fstart\u002Fskills\u002Fimplementation-verification\u002FSKILL.md",true,[],[76,85,93,101,109,117],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":84},"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":89,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":84},"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":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":84},"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":102,"name":103,"nameZh":6,"description":104,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":105,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":84},"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":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":113,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":84},"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":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":84},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]