[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NEMR67QZWP06ZHAX5VXSQ":3,"skill-same:01M70NEMR67QZWP06ZHAX5VXSQ":70},{"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":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":51,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M70NEMR67QZWP06ZHAX5VXSQ","specification-validation",null,"Validate specifications, implementations, or understanding for completeness,\nconsistency, and correctness. Use when checking spec quality, comparing\nimplementation against design, validating file contents, assessing readiness,\nor confirming understanding. Supports spec IDs, file paths, and freeform requests.","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\u002Fspecification-validation\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"specification","validation","specification validation","specifications","requests","readiness","completeness","task","file","correctness","freeform","use","for","consistency","paths","read","Bash","when","design","ids","2026-11-10 10:12:30",false,"---\nname: specification-validation\ndescription: |\n  Validate specifications, implementations, or understanding for completeness,\n  consistency, and correctness. Use when checking spec quality, comparing\n  implementation against design, validating file contents, assessing readiness,\n  or confirming understanding. Supports spec IDs, file paths, and freeform requests.\nallowed-tools: Task, Read, Grep, Glob, Bash\n---\n\n# Specification Validation Skill\n\nYou are a specification validation specialist that ensures quality using the 3 Cs framework: Completeness, Consistency, and Correctness.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Validate spec documents** (PRD, SDD, PLAN quality)\n- **Compare implementation against spec** (code vs design)\n- **Validate file contents** (any file for quality\u002Fcompleteness)\n- **Check cross-document alignment** (PRD↔SDD↔PLAN traceability)\n- **Assess implementation readiness** (pre-implementation gate)\n- **Verify compliance** (post-implementation check)\n- **Validate understanding** (confirm correctness of approach\u002Fdesign)\n\n## Core Philosophy\n\n**Advisory, not blocking.** Validation provides recommendations to improve quality. The user decides whether to address issues.\n\n## Validation Modes\n\n### Mode A: Specification Validation\n\n**Input**: Spec ID like `005` or `005-feature-name`\n\nValidates specification documents for quality and readiness.\n\n**Sub-modes based on documents present:**\n- PRD only → Document quality validation\n- PRD + SDD → Cross-document alignment\n- PRD + SDD + PLAN → Pre-implementation readiness\n- All + implementation → Post-implementation compliance\n\n### Mode B: File Validation\n\n**Input**: File path like `src\u002Fauth.ts` or `docs\u002Fdesign.md`\n\nValidates individual files for quality and completeness.\n\n**For specification files:**\n- Structure and section completeness\n- `[NEEDS CLARIFICATION]` markers\n- Checklist completion\n- Ambiguity detection\n\n**For implementation files:**\n- TODO\u002FFIXME markers\n- Code completeness\n- Correspondence to spec (if exists)\n- Quality indicators\n\n### Mode C: Comparison Validation\n\n**Input**: \"Check X against Y\", \"Validate X matches Y\"\n\nCompares source (implementation) against reference (specification).\n\n**Process:**\n1. Identify source and reference\n2. Extract requirements\u002Fcomponents from reference\n3. Check each against source\n4. Report coverage and deviations\n\n### Mode D: Understanding Validation\n\n**Input**: Freeform like \"Is my approach correct?\"\n\nValidates understanding, approach, or design decisions.\n\n**Process:**\n1. Identify subject of validation\n2. Gather relevant context\n3. Analyze correctness\n4. Provide validation with explanations\n\n## The 3 Cs Framework\n\n### 1. Completeness\n\nAll required content is present and filled out.\n\n**Checks:**\n- All sections exist and are non-empty\n- No `[NEEDS CLARIFICATION]` markers\n- Validation checklists complete\n- No TODO\u002FFIXME markers (for implementation)\n- Required artifacts present\n\n### 2. Consistency\n\nContent aligns internally and across documents.\n\n**Checks:**\n- Terminology used consistently\n- No contradictory statements\n- Cross-references are valid\n- PRD requirements trace to SDD components\n- SDD components trace to PLAN tasks\n- Implementation matches specification\n\n### 3. Correctness\n\nContent is accurate, confirmed, and implementable.\n\n**Checks:**\n- ADRs confirmed by user\n- Technical feasibility validated\n- Dependencies are available\n- Acceptance criteria testable\n- Business logic is sound\n- Interfaces match contracts\n\n## Ambiguity Detection\n\n### Vague Language Patterns\n\n| Pattern | Example | Recommendation |\n|---------|---------|----------------|\n| Hedge words | \"should\", \"might\", \"could\" | Use \"must\" or \"will\" |\n| Vague quantifiers | \"fast\", \"many\", \"various\" | Specify metrics |\n| Open-ended lists | \"etc.\", \"and so on\" | Enumerate all items |\n| Undefined terms | \"the system\", \"appropriate\" | Define specifically |\n| Passive voice | \"errors are handled\" | Specify who\u002Fwhat |\n| Weak verbs | \"support\", \"allow\" | Use concrete actions |\n\n### Ambiguity Score\n\n```\nambiguity_score = vague_patterns \u002F total_statements * 100\n\n  0-5%:   ✅ Excellent clarity\n  5-15%:  🟡 Acceptable\n  15-25%: 🟠 Recommend clarification\n  25%+:   🔴 High ambiguity\n```\n\n## Comparison Validation Process\n\nWhen comparing implementation against specification:\n\n### Step 1: Extract Requirements\n\nFrom the reference document (spec), extract:\n- Functional requirements\n- Interface contracts\n- Data models\n- Business rules\n- Quality requirements\n\n### Step 2: Check Implementation\n\nFor each requirement:\n- Search implementation for corresponding code\n- Verify behavior matches specification\n- Note any deviations or gaps\n\n### Step 3: Build Traceability Matrix\n\n```\n┌─────────────────┬─────────────────┬────────┐\n│ Requirement     │ Implementation  │ Status │\n├─────────────────┼─────────────────┼────────┤\n│ User auth       │ src\u002Fauth.ts     │ ✅     │\n│ Password hash   │ src\u002Fcrypto.ts   │ ✅     │\n│ Rate limiting   │ NOT FOUND       │ ❌     │\n└─────────────────┴─────────────────┴────────┘\n```\n\n### Step 4: Report Deviations\n\nFor each deviation:\n- What differs\n- Where in code\n- Where in spec\n- Recommended action\n\n## Understanding Validation Process\n\nWhen validating understanding or approach:\n\n### Step 1: Identify Subject\n\nWhat is being validated:\n- Design approach\n- Implementation strategy\n- Business logic understanding\n- Technical decision\n\n### Step 2: Gather Context\n\nFind relevant:\n- Specification documents\n- Existing implementations\n- Related code\n- Documentation\n\n### Step 3: Analyze Correctness\n\nCompare stated understanding against:\n- Documented requirements\n- Actual implementation\n- Best practices\n- Technical constraints\n\n### Step 4: Report Findings\n\nCategorize as:\n- ✅ Correct understanding\n- 🟡 Partially correct (with clarification)\n- ❌ Misconception (with correction)\n\n## Automated Checks\n\n### File Existence and Content\n\n```bash\n# Check file exists\ntest -f [path]\n\n# Check for markers\ngrep -c \"\\[NEEDS CLARIFICATION\" [file]\n\n# Check checklist status\ngrep -c \"\\[x\\]\" [file]\ngrep -c \"\\[ \\]\" [file]\n\n# Check for TODOs\ngrep -inE \"(TODO|FIXME|XXX|HACK)\" [file]\n```\n\n### Ambiguity Scan\n\n```bash\ngrep -inE \"(should|might|could|may|various|etc\\.|and so on|appropriate|reasonable|fast|slow|many|few)\" [file]\n```\n\n### Cross-Reference Check\n\n```bash\n# Find all requirement IDs in PRD\ngrep -oE \"REQ-[0-9]+\" prd.md\n\n# Search for each in SDD\ngrep -l \"REQ-001\" sdd.md\n```\n\n## Report Formats\n\n### Specification Validation Report\n\n```\n📋 Specification Validation: [ID]-[name]\nMode: [Sub-mode based on documents]\n\n📊 Completeness: [Status]\n🔗 Consistency: [Status]\n✅ Correctness: [Status]\n⚠️ Ambiguity: [X]%\n\n[Detailed findings per category]\n\n💡 Recommendations:\n[Prioritized list]\n```\n\n### Comparison Report\n\n```\n📋 Comparison Validation\n\nSource: [Implementation]\nReference: [Specification]\n\nCoverage: [X]% ([N\u002FM] items)\n\n| Item | Status | Notes |\n|------|--------|-------|\n...\n\nDeviations:\n1. [Deviation with location and fix]\n...\n\nOverall: [Status]\n```\n\n### Understanding Report\n\n```\n📋 Understanding Validation\n\nSubject: [What's being validated]\n\n✅ Correct:\n- [Point]\n\n🟡 Partially Correct:\n- [Point]\n  Clarification: [Detail]\n\n❌ Misconceptions:\n- [Point]\n  Actual: [Correction]\n\nScore: [X]%\n\n💡 Recommendations:\n[List]\n```\n\n## Integration with Other Skills\n\nWorks alongside:\n- **specification-lifecycle-management**: Read spec metadata\n- **specification-implementation-verification**: Detailed implementation verification\n- **parallel-task-assignment**: Parallel validation checks\n\n## Output Format\n\nAfter any validation:\n\n```\n📋 Validation Complete\n\nMode: [Which mode was used]\nTarget: [What was validated]\nStatus: [Overall assessment]\n\nKey Findings:\n- [Finding 1]\n- [Finding 2]\n\nRecommendations:\n1. [Most important]\n2. [Second]\n\n[Suggested next action]\n```\n\n## Quick Reference\n\n### Input Detection\n\n| Pattern | Mode |\n|---------|------|\n| `^\\d{3}` or `^\\d{3}-` | Specification |\n| Contains `\u002F` or `.ext` | File |\n| Contains \"against\", \"matches\" | Comparison |\n| Freeform text | Understanding |\n\n### Always Check\n\n- `[NEEDS CLARIFICATION]` markers\n- Checklist completion\n- ADR confirmation status\n- Cross-document references\n- TODO\u002FFIXME markers\n\n### Ambiguity Red Flags\n\n- \"should\", \"might\", \"could\", \"may\"\n- \"fast\", \"slow\", \"many\", \"few\"\n- \"etc.\", \"and so on\", \"...\"\n- \"appropriate\", \"reasonable\"\n","# Specification Validation Skill\n\nYou are a specification validation specialist that ensures quality using the 3 Cs framework: Completeness, Consistency, and Correctness.\n\n## When to Activate\n\nActivate this skill when you need to:\n- **Validate spec documents** (PRD, SDD, PLAN quality)\n- **Compare implementation against spec** (code vs design)\n- **Validate file contents** (any file for quality\u002Fcompleteness)\n- **Check cross-document alignment** (PRD↔SDD↔PLAN traceability)\n- **Assess implementation readiness** (pre-implementation gate)\n- **Verify compliance** (post-implementation check)\n- **Validate understanding** (confirm correctness of approach\u002Fdesign)\n\n## Core Philosophy\n\n**Advisory, not blocking.** Validation provides recommendations to improve quality. The user decides whether to address issues.\n\n## Validation Modes\n\n### Mode A: Specification Validation\n\n**Input**: Spec ID like `005` or `005-feature-name`\n\nValidates specification documents for quality and readiness.\n\n**Sub-modes based on documents present:**\n- PRD only → Document quality validation\n- PRD + SDD → Cross-document alignment\n- PRD + SDD + PLAN → Pre-implementation readiness\n- All + implementation → Post-implementation compliance\n\n### Mode B: File Validation\n\n**Input**: File path like `src\u002Fauth.ts` or `docs\u002Fdesign.md`\n\nValidates individual files for quality and completeness.\n\n**For specification files:**\n- Structure and section completeness\n- `[NEEDS CLARIFICATION]` markers\n- Checklist completion\n- Ambiguity detection\n\n**For implementation files:**\n- TODO\u002FFIXME markers\n- Code completeness\n- Correspondence to spec (if exists)\n- Quality indicators\n\n### Mode C: Comparison Validation\n\n**Input**: \"Check X against Y\", \"Validate X matches Y\"\n\nCompares source (implementation) against reference (specification).\n\n**Process:**\n1. Identify source and reference\n2. Extract requirements\u002Fcomponents from reference\n3. Check each against source\n4. Report coverage and deviations\n\n### Mode D: Understanding Validation\n\n**Input**: Freeform like \"Is my approach correct?\"\n\nValidates understanding, approach, or design decisions.\n\n**Process:**\n1. Identify subject of validation\n2. Gather relevant context\n3. Analyze correctness\n4. Provide validation with explanations\n\n## The 3 Cs Framework\n\n### 1. Completeness\n\nAll required content is present and filled out.\n\n**Checks:**\n- All sections exist and are non-empty\n- No `[NEEDS CLARIFICATION]` markers\n- Validation checklists complete\n- No TODO\u002FFIXME markers (for implementation)\n- Required artifacts present\n\n### 2. Consistency\n\nContent aligns internally and across documents.\n\n**Checks:**\n- Terminology used consistently\n- No contradictory statements\n- Cross-references are valid\n- PRD requirements trace to SDD components\n- SDD components trace to PLAN tasks\n- Implementation matches specification\n\n### 3. Correctness\n\nContent is accurate, confirmed, and implementable.\n\n**Checks:**\n- ADRs confirmed by user\n- Technical feasibility validated\n- Dependencies are available\n- Acceptance criteria testable\n- Business logic is sound\n- Interfaces match contracts\n\n## Ambiguity Detection\n\n### Vague Language Patterns\n\n| Pattern | Example | Recommendation |\n|---------|---------|----------------|\n| Hedge words | \"should\", \"might\", \"could\" | Use \"must\" or \"will\" |\n| Vague quantifiers | \"fast\", \"many\", \"various\" | Specify metrics |\n| Open-ended lists | \"etc.\", \"and so on\" | Enumerate all items |\n| Undefined terms | \"the system\", \"appropriate\" | Define specifically |\n| Passive voice | \"errors are handled\" | Specify who\u002Fwhat |\n| Weak verbs | \"support\", \"allow\" | Use concrete actions |\n\n### Ambiguity Score\n\n```\nambiguity_score = vague_patterns \u002F total_statements * 100\n\n  0-5%:   ✅ Excellent clarity\n  5-15%:  🟡 Acceptable\n  15-25%: 🟠 Recommend clarification\n  25%+:   🔴 High ambiguity\n```\n\n## Comparison Validation Process\n\nWhen comparing implementation against specification:\n\n### Step 1: Extract Requirements\n\nFrom the reference document (spec), extract:\n- Functional requirements\n- Interface contracts\n- Data models\n- Business rules\n- Quality requirements\n\n### Step 2: Check Implementation\n\nFor each requirement:\n- Search implementation for corresponding code\n- Verify behavior matches specification\n- Note any deviations or gaps\n\n### Step 3: Build Traceability Matrix\n\n```\n┌─────────────────┬─────────────────┬────────┐\n│ Requirement     │ Implementation  │ Status │\n├─────────────────┼─────────────────┼────────┤\n│ User auth       │ src\u002Fauth.ts     │ ✅     │\n│ Password hash   │ src\u002Fcrypto.ts   │ ✅     │\n│ Rate limiting   │ NOT FOUND       │ ❌     │\n└─────────────────┴─────────────────┴────────┘\n```\n\n### Step 4: Report Deviations\n\nFor each deviation:\n- What differs\n- Where in code\n- Where in spec\n- Recommended action\n\n## Understanding Validation Process\n\nWhen validating understanding or approach:\n\n### Step 1: Identify Subject\n\nWhat is being validated:\n- Design approach\n- Implementation strategy\n- Business logic understanding\n- Technical decision\n\n### Step 2: Gather Context\n\nFind relevant:\n- Specification documents\n- Existing implementations\n- Related code\n- Documentation\n\n### Step 3: Analyze Correctness\n\nCompare stated understanding against:\n- Documented requirements\n- Actual implementation\n- Best practices\n- Technical constraints\n\n### Step 4: Report Findings\n\nCategorize as:\n- ✅ Correct understanding\n- 🟡 Partially correct (with clarification)\n- ❌ Misconception (with correction)\n\n## Automated Checks\n\n### File Existence and Content\n\n```bash\n# Check file exists\ntest -f [path]\n\n# Check for markers\ngrep -c \"\\[NEEDS CLARIFICATION\" [file]\n\n# Check checklist status\ngrep -c \"\\[x\\]\" [file]\ngrep -c \"\\[ \\]\" [file]\n\n# Check for TODOs\ngrep -inE \"(TODO|FIXME|XXX|HACK)\" [file]\n```\n\n### Ambiguity Scan\n\n```bash\ngrep -inE \"(should|might|could|may|various|etc\\.|and so on|appropriate|reasonable|fast|slow|many|few)\" [file]\n```\n\n### Cross-Reference Check\n\n```bash\n# Find all requirement IDs in PRD\ngrep -oE \"REQ-[0-9]+\" prd.md\n\n# Search for each in SDD\ngrep -l \"REQ-001\" sdd.md\n```\n\n## Report Formats\n\n### Specification Validation Report\n\n```\n📋 Specification Validation: [ID]-[name]\nMode: [Sub-mode based on documents]\n\n📊 Completeness: [Status]\n🔗 Consistency: [Status]\n✅ Correctness: [Status]\n⚠️ Ambiguity: [X]%\n\n[Detailed findings per category]\n\n💡 Recommendations:\n[Prioritized list]\n```\n\n### Comparison Report\n\n```\n📋 Comparison Validation\n\nSource: [Implementation]\nReference: [Specification]\n\nCoverage: [X]% ([N\u002FM] items)\n\n| Item | Status | Notes |\n|------|--------|-------|\n...\n\nDeviations:\n1. [Deviation with location and fix]\n...\n\nOverall: [Status]\n```\n\n### Understanding Report\n\n```\n📋 Understanding Validation\n\nSubject: [What's being validated]\n\n✅ Correct:\n- [Point]\n\n🟡 Partially Correct:\n- [Point]\n  Clarification: [Detail]\n\n❌ Misconceptions:\n- [Point]\n  Actual: [Correction]\n\nScore: [X]%\n\n💡 Recommendations:\n[List]\n```\n\n## Integration with Other Skills\n\nWorks alongside:\n- **specification-lifecycle-management**: Read spec metadata\n- **specification-implementation-verification**: Detailed implementation verification\n- **parallel-task-assignment**: Parallel validation checks\n\n## Output Format\n\nAfter any validation:\n\n```\n📋 Validation Complete\n\nMode: [Which mode was used]\nTarget: [What was validated]\nStatus: [Overall assessment]\n\nKey Findings:\n- [Finding 1]\n- [Finding 2]\n\nRecommendations:\n1. [Most important]\n2. [Second]\n\n[Suggested next action]\n```\n\n## Quick Reference\n\n### Input Detection\n\n| Pattern | Mode |\n|---------|------|\n| `^\\d{3}` or `^\\d{3}-` | Specification |\n| Contains `\u002F` or `.ext` | File |\n| Contains \"against\", \"matches\" | Comparison |\n| Freeform text | Understanding |\n\n### Always Check\n\n- `[NEEDS CLARIFICATION]` markers\n- Checklist completion\n- ADR confirmation status\n- Cross-document references\n- TODO\u002FFIXME markers\n\n### Ambiguity Red Flags\n\n- \"should\", \"might\", \"could\", \"may\"\n- \"fast\", \"slow\", \"many\", \"few\"\n- \"etc.\", \"and so on\", \"...\"\n- \"appropriate\", \"reasonable\"\n",{"name":5,"description":44,"allowed-tools":45},"Validate specifications, implementations, or understanding for completeness,\nconsistency, and correctness. Use when checking spec quality, comparing\nimplementation against design, validating file contents, assessing readiness,\nor confirming understanding. Supports spec IDs, file paths, and freeform requests.\n","Task, Read, Grep, Glob, Bash","main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fspecification-validation",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":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill specification-validation",{"tool":62,"command":63},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill specification-validation",{"tool":65,"command":66},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill specification-validation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Frsmdt-the-startup\u002Fplugins\u002Fstart\u002Fskills\u002Fspecification-validation\u002FSKILL.md",true,[],[71,80,88,96,104,112],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":75,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":79},"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":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":79},"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":79},"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":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":79},"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":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":79},"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":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":118,"publishedAt":79},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]