[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70KWYCJKMX5PMMJWPKMGQ0V":3,"skill-same:01M70KWYCJKMX5PMMJWPKMGQ0V":73},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":50,"commitSha":51,"skillDirectory":52,"forksCount":53,"repositoryHtmlUrl":54,"repositoryHomepageUrl":55,"ownerHtmlUrl":56,"ownerBlogUrl":57,"ownerDescription":58,"updatedAt":59,"install":60,"resources":72},"01M70KWYCJKMX5PMMJWPKMGQ0V","audit",null,"Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.","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\u002Faudit\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"responsive design","feature","severity","quality review","responsive","ratings","patterns","anti-patterns","performance audit","run","component","accessibility check","plan","across","review","when","design","performance","actionable","2026-11-10 10:12:30",false,"---\nname: audit\ndescription: Run technical quality checks across accessibility, performance, theming, responsive design, and anti-patterns. Generates a scored report with P0-P3 severity ratings and actionable plan. Use when the user wants an accessibility check, performance audit, or technical quality review.\nuser-invocable: true\nargument-hint: \"[area (feature, page, component...)]\"\n---\n\n## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\nRun systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.\n\nThis is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.\n\n## Diagnostic Scan\n\nRun comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.\n\n### 1. Accessibility (A11y)\n\n**Check for**:\n- **Contrast issues**: Text contrast ratios \u003C 4.5:1 (or 7:1 for AAA)\n- **Missing ARIA**: Interactive elements without proper roles, labels, or states\n- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps\n- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons\n- **Alt text**: Missing or poor image descriptions\n- **Form issues**: Inputs without labels, poor error messaging, missing required indicators\n\n**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA)\n\n### 2. Performance\n\n**Check for**:\n- **Layout thrashing**: Reading\u002Fwriting layout properties in loops\n- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform\u002Fopacity\n- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change\n- **Bundle size**: Unnecessary imports, unused dependencies\n- **Render performance**: Unnecessary re-renders, missing memoization\n\n**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized)\n\n### 3. Theming\n\n**Check for**:\n- **Hard-coded colors**: Colors not using design tokens\n- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme\n- **Inconsistent tokens**: Using wrong tokens, mixing token types\n- **Theme switching issues**: Values that don't update on theme change\n\n**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly)\n\n### 4. Responsive Design\n\n**Check for**:\n- **Fixed widths**: Hard-coded widths that break on mobile\n- **Touch targets**: Interactive elements \u003C 44x44px\n- **Horizontal scroll**: Content overflow on narrow viewports\n- **Text scaling**: Layouts that break when text size increases\n- **Missing breakpoints**: No mobile\u002Ftablet variants\n\n**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets)\n\n### 5. Anti-Patterns (CRITICAL)\n\nCheck against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).\n\n**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design)\n\n## Generate Report\n\n### Audit Health Score\n\n| # | Dimension | Score | Key Finding |\n|---|-----------|-------|-------------|\n| 1 | Accessibility | ? | [most critical a11y issue or \"--\"] |\n| 2 | Performance | ? | |\n| 3 | Responsive Design | ? | |\n| 4 | Theming | ? | |\n| 5 | Anti-Patterns | ? | |\n| **Total** | | **??\u002F20** | **[Rating band]** |\n\n**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)\n\n### Anti-Patterns Verdict\n**Start here.** Pass\u002Ffail: Does this look AI-generated? List specific tells. Be brutally honest.\n\n### Executive Summary\n- Audit Health Score: **??\u002F20** ([rating band])\n- Total issues found (count by severity: P0\u002FP1\u002FP2\u002FP3)\n- Top 3-5 critical issues\n- Recommended next steps\n\n### Detailed Findings by Severity\n\nTag every issue with **P0-P3 severity**:\n- **P0 Blocking**: Prevents task completion — fix immediately\n- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release\n- **P2 Minor**: Annoyance, workaround exists — fix in next pass\n- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits\n\nFor each issue, document:\n- **[P?] Issue name**\n- **Location**: Component, file, line\n- **Category**: Accessibility \u002F Performance \u002F Theming \u002F Responsive \u002F Anti-Pattern\n- **Impact**: How it affects users\n- **WCAG\u002FStandard**: Which standard it violates (if applicable)\n- **Recommendation**: How to fix it\n- **Suggested command**: Which command to use (prefer: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive)\n\n### Patterns & Systemic Issues\n\nIdentify recurring problems that indicate systemic gaps rather than one-off mistakes:\n- \"Hard-coded colors appear in 15+ components, should use design tokens\"\n- \"Touch targets consistently too small (\u003C44px) throughout mobile experience\"\n\n### Positive Findings\n\nNote what's working well — good practices to maintain and replicate.\n\n## Recommended Actions\n\nList recommended commands in priority order (P0 first, then P1, then P2):\n\n1. **[P?] `\u002Fcommand-name`** — Brief description (specific context from audit findings)\n2. **[P?] `\u002Fcommand-name`** — Brief description (specific context)\n\n**Rules**: Only recommend commands from: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive. Map findings to the most appropriate command. End with `\u002Fpolish` as the final step if any fixes were recommended.\n\nAfter presenting the summary, tell the user:\n\n> You can ask me to run these one at a time, all at once, or in any order you prefer.\n>\n> Re-run `\u002Faudit` after fixes to see your score improve.\n\n**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.\n\n**NEVER**:\n- Report issues without explaining impact (why does this matter?)\n- Provide generic recommendations (be specific and actionable)\n- Skip positive findings (celebrate what works)\n- Forget to prioritize (everything can't be P0)\n- Report false positives without verification\n\nRemember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement.","## MANDATORY PREPARATION\n\nInvoke \u002Ffrontend-design — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fteach-impeccable first.\n\n---\n\nRun systematic **technical** quality checks and generate a comprehensive report. Don't fix issues — document them for other commands to address.\n\nThis is a code-level audit, not a design critique. Check what's measurable and verifiable in the implementation.\n\n## Diagnostic Scan\n\nRun comprehensive checks across 5 dimensions. Score each dimension 0-4 using the criteria below.\n\n### 1. Accessibility (A11y)\n\n**Check for**:\n- **Contrast issues**: Text contrast ratios \u003C 4.5:1 (or 7:1 for AAA)\n- **Missing ARIA**: Interactive elements without proper roles, labels, or states\n- **Keyboard navigation**: Missing focus indicators, illogical tab order, keyboard traps\n- **Semantic HTML**: Improper heading hierarchy, missing landmarks, divs instead of buttons\n- **Alt text**: Missing or poor image descriptions\n- **Form issues**: Inputs without labels, poor error messaging, missing required indicators\n\n**Score 0-4**: 0=Inaccessible (fails WCAG A), 1=Major gaps (few ARIA labels, no keyboard nav), 2=Partial (some a11y effort, significant gaps), 3=Good (WCAG AA mostly met, minor gaps), 4=Excellent (WCAG AA fully met, approaches AAA)\n\n### 2. Performance\n\n**Check for**:\n- **Layout thrashing**: Reading\u002Fwriting layout properties in loops\n- **Expensive animations**: Animating layout properties (width, height, top, left) instead of transform\u002Fopacity\n- **Missing optimization**: Images without lazy loading, unoptimized assets, missing will-change\n- **Bundle size**: Unnecessary imports, unused dependencies\n- **Render performance**: Unnecessary re-renders, missing memoization\n\n**Score 0-4**: 0=Severe issues (layout thrash, unoptimized everything), 1=Major problems (no lazy loading, expensive animations), 2=Partial (some optimization, gaps remain), 3=Good (mostly optimized, minor improvements possible), 4=Excellent (fast, lean, well-optimized)\n\n### 3. Theming\n\n**Check for**:\n- **Hard-coded colors**: Colors not using design tokens\n- **Broken dark mode**: Missing dark mode variants, poor contrast in dark theme\n- **Inconsistent tokens**: Using wrong tokens, mixing token types\n- **Theme switching issues**: Values that don't update on theme change\n\n**Score 0-4**: 0=No theming (hard-coded everything), 1=Minimal tokens (mostly hard-coded), 2=Partial (tokens exist but inconsistently used), 3=Good (tokens used, minor hard-coded values), 4=Excellent (full token system, dark mode works perfectly)\n\n### 4. Responsive Design\n\n**Check for**:\n- **Fixed widths**: Hard-coded widths that break on mobile\n- **Touch targets**: Interactive elements \u003C 44x44px\n- **Horizontal scroll**: Content overflow on narrow viewports\n- **Text scaling**: Layouts that break when text size increases\n- **Missing breakpoints**: No mobile\u002Ftablet variants\n\n**Score 0-4**: 0=Desktop-only (breaks on mobile), 1=Major issues (some breakpoints, many failures), 2=Partial (works on mobile, rough edges), 3=Good (responsive, minor touch target or overflow issues), 4=Excellent (fluid, all viewports, proper touch targets)\n\n### 5. Anti-Patterns (CRITICAL)\n\nCheck against ALL the **DON'T** guidelines in the frontend-design skill. Look for AI slop tells (AI color palette, gradient text, glassmorphism, hero metrics, card grids, generic fonts) and general design anti-patterns (gray on color, nested cards, bounce easing, redundant copy).\n\n**Score 0-4**: 0=AI slop gallery (5+ tells), 1=Heavy AI aesthetic (3-4 tells), 2=Some tells (1-2 noticeable), 3=Mostly clean (subtle issues only), 4=No AI tells (distinctive, intentional design)\n\n## Generate Report\n\n### Audit Health Score\n\n| # | Dimension | Score | Key Finding |\n|---|-----------|-------|-------------|\n| 1 | Accessibility | ? | [most critical a11y issue or \"--\"] |\n| 2 | Performance | ? | |\n| 3 | Responsive Design | ? | |\n| 4 | Theming | ? | |\n| 5 | Anti-Patterns | ? | |\n| **Total** | | **??\u002F20** | **[Rating band]** |\n\n**Rating bands**: 18-20 Excellent (minor polish), 14-17 Good (address weak dimensions), 10-13 Acceptable (significant work needed), 6-9 Poor (major overhaul), 0-5 Critical (fundamental issues)\n\n### Anti-Patterns Verdict\n**Start here.** Pass\u002Ffail: Does this look AI-generated? List specific tells. Be brutally honest.\n\n### Executive Summary\n- Audit Health Score: **??\u002F20** ([rating band])\n- Total issues found (count by severity: P0\u002FP1\u002FP2\u002FP3)\n- Top 3-5 critical issues\n- Recommended next steps\n\n### Detailed Findings by Severity\n\nTag every issue with **P0-P3 severity**:\n- **P0 Blocking**: Prevents task completion — fix immediately\n- **P1 Major**: Significant difficulty or WCAG AA violation — fix before release\n- **P2 Minor**: Annoyance, workaround exists — fix in next pass\n- **P3 Polish**: Nice-to-fix, no real user impact — fix if time permits\n\nFor each issue, document:\n- **[P?] Issue name**\n- **Location**: Component, file, line\n- **Category**: Accessibility \u002F Performance \u002F Theming \u002F Responsive \u002F Anti-Pattern\n- **Impact**: How it affects users\n- **WCAG\u002FStandard**: Which standard it violates (if applicable)\n- **Recommendation**: How to fix it\n- **Suggested command**: Which command to use (prefer: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive)\n\n### Patterns & Systemic Issues\n\nIdentify recurring problems that indicate systemic gaps rather than one-off mistakes:\n- \"Hard-coded colors appear in 15+ components, should use design tokens\"\n- \"Touch targets consistently too small (\u003C44px) throughout mobile experience\"\n\n### Positive Findings\n\nNote what's working well — good practices to maintain and replicate.\n\n## Recommended Actions\n\nList recommended commands in priority order (P0 first, then P1, then P2):\n\n1. **[P?] `\u002Fcommand-name`** — Brief description (specific context from audit findings)\n2. **[P?] `\u002Fcommand-name`** — Brief description (specific context)\n\n**Rules**: Only recommend commands from: \u002Fanimate, \u002Fquieter, \u002Foptimize, \u002Fadapt, \u002Fclarify, \u002Fdistill, \u002Fdelight, \u002Fonboard, \u002Fnormalize, \u002Faudit, \u002Fharden, \u002Fpolish, \u002Fextract, \u002Fbolder, \u002Farrange, \u002Ftypeset, \u002Fcritique, \u002Fcolorize, \u002Foverdrive. Map findings to the most appropriate command. End with `\u002Fpolish` as the final step if any fixes were recommended.\n\nAfter presenting the summary, tell the user:\n\n> You can ask me to run these one at a time, all at once, or in any order you prefer.\n>\n> Re-run `\u002Faudit` after fixes to see your score improve.\n\n**IMPORTANT**: Be thorough but actionable. Too many P3 issues creates noise. Focus on what actually matters.\n\n**NEVER**:\n- Report issues without explaining impact (why does this matter?)\n- Provide generic recommendations (be specific and actionable)\n- Skip positive findings (celebrate what works)\n- Forget to prioritize (everything can't be P0)\n- Report false positives without verification\n\nRemember: You're a technical quality auditor. Document systematically, prioritize ruthlessly, cite specific code locations, and provide clear paths to improvement.",{"name":5,"description":7,"argument-hint":48,"user-invocable":49},"[area (feature, page, component...)]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Faudit",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":49},[62,65,68],{"tool":63,"command":64},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill audit",{"tool":66,"command":67},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill audit",{"tool":69,"command":70},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill audit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Faudit\u002FSKILL.md",[],[74,83,91,99,107,115],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":78,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":82},"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":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":82},"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":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":95,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":82},"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":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":103,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":82},"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":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":111,"sourceHtmlUrl":112,"categories":113,"keywords":114,"publishedAt":82},"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":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":82},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]