[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70NMXAEMT20T35VJN9F9VG9":3,"skill-same:01M70NMXAEMT20T35VJN9F9VG9":78},{"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":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":59,"ownerHtmlUrl":60,"ownerBlogUrl":61,"ownerDescription":62,"updatedAt":63,"install":64,"resources":77},"01M70NMXAEMT20T35VJN9F9VG9","web-perf",null,"Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.","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\u002Fweb-perf\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"perf","web","web perf","network","dependency","audit","layout","optimize","documentation","caching","when","MCP","knowledge","devtools","issues","render","performance","chrome devtools","vitals","resources","2026-11-10 10:12:30",false,"---\nname: web-perf\ndescription: Analyzes web performance using Chrome DevTools MCP. Measures Core Web Vitals (LCP, INP, CLS) and supplementary metrics (FCP, TBT, Speed Index), identifies render-blocking resources, network dependency chains, layout shifts, caching issues, and accessibility gaps. Use when asked to audit, profile, debug, or optimize page load performance, Lighthouse scores, or site speed. Biases towards retrieval from current documentation over pre-trained knowledge.\n---\n\n# Web Performance Audit\n\nYour knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. **Prefer retrieval over pre-training** when citing specific numbers or recommendations.\n\n## Retrieval Sources\n\n| Source | How to retrieve | Use for |\n|--------|----------------|---------|\n| web.dev | `https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals` | Core Web Vitals thresholds, definitions |\n| Chrome DevTools docs | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fdevtools\u002Fperformance` | Tooling APIs, trace analysis |\n| Lighthouse scoring | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Flighthouse\u002Fperformance\u002Fperformance-scoring` | Score weights, metric thresholds |\n\n## FIRST: Verify MCP Tools Available\n\n**Run this before starting.** Try calling `navigate_page` or `performance_start_trace`. If unavailable, STOP—the chrome-devtools MCP server isn't configured.\n\nAsk the user to add this to their MCP config:\n\n```json\n\"chrome-devtools\": {\n  \"type\": \"local\",\n  \"command\": [\"npx\", \"-y\", \"chrome-devtools-mcp@latest\"]\n}\n```\n\n## Key Guidelines\n\n- **Be assertive**: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.\n- **Verify before recommending**: Confirm something is unused before suggesting removal.\n- **Quantify impact**: Use estimated savings from insights. Don't prioritize changes with 0ms impact.\n- **Skip non-issues**: If render-blocking resources have 0ms estimated impact, note but don't recommend action.\n- **Be specific**: Say \"compress hero.png (450KB) to WebP\" not \"optimize images\".\n- **Prioritize ruthlessly**: A site with 200ms LCP and 0 CLS is already excellent—say so.\n\n## Quick Reference\n\n| Task | Tool Call |\n|------|-----------|\n| Load page | `navigate_page(url: \"...\")` |\n| Start trace | `performance_start_trace(autoStop: true, reload: true)` |\n| Analyze insight | `performance_analyze_insight(insightSetId: \"...\", insightName: \"...\")` |\n| List requests | `list_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", ...])` |\n| Request details | `get_network_request(reqid: \u003Cid>)` |\n| A11y snapshot | `take_snapshot(verbose: true)` |\n\n## Workflow\n\nCopy this checklist to track progress:\n\n```\nAudit Progress:\n- [ ] Phase 1: Performance trace (navigate + record)\n- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)\n- [ ] Phase 3: Network analysis\n- [ ] Phase 4: Accessibility snapshot\n- [ ] Phase 5: Codebase analysis (skip if third-party site)\n```\n\n### Phase 1: Performance Trace\n\n1. Navigate to the target URL:\n   ```\n   navigate_page(url: \"\u003Ctarget-url>\")\n   ```\n\n2. Start a performance trace with reload to capture cold-load metrics:\n   ```\n   performance_start_trace(autoStop: true, reload: true)\n   ```\n\n3. Wait for trace completion, then retrieve results.\n\n**Troubleshooting:**\n- If trace returns empty or fails, verify the page loaded correctly with `navigate_page` first\n- If insight names don't match, inspect the trace response to list available insights\n\n### Phase 2: Core Web Vitals Analysis\n\nUse `performance_analyze_insight` to extract key metrics.\n\n**Note:** Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the `insightSetId` from the trace response to discover available insights.\n\nCommon insight names:\n\n| Metric | Insight Name | What to Look For |\n|--------|--------------|------------------|\n| LCP | `LCPBreakdown` | Time to largest contentful paint; breakdown of TTFB, resource load, render delay |\n| CLS | `CLSCulprits` | Elements causing layout shifts (images without dimensions, injected content, font swaps) |\n| Render Blocking | `RenderBlocking` | CSS\u002FJS blocking first paint |\n| Document Latency | `DocumentLatency` | Server response time issues |\n| Network Dependencies | `NetworkRequestsDepGraph` | Request chains delaying critical resources |\n\nExample:\n```\nperformance_analyze_insight(insightSetId: \"\u003Cid-from-trace>\", insightName: \"LCPBreakdown\")\n```\n\n**Key thresholds (good\u002Fneeds-improvement\u002Fpoor):**\n- TTFB: \u003C 800ms \u002F \u003C 1.8s \u002F > 1.8s\n- FCP: \u003C 1.8s \u002F \u003C 3s \u002F > 3s\n- LCP: \u003C 2.5s \u002F \u003C 4s \u002F > 4s\n- INP: \u003C 200ms \u002F \u003C 500ms \u002F > 500ms\n- TBT: \u003C 200ms \u002F \u003C 600ms \u002F > 600ms\n- CLS: \u003C 0.1 \u002F \u003C 0.25 \u002F > 0.25\n- Speed Index: \u003C 3.4s \u002F \u003C 5.8s \u002F > 5.8s\n\n### Phase 3: Network Analysis\n\nList all network requests to identify optimization opportunities:\n```\nlist_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", \"Document\", \"Font\", \"Image\"])\n```\n\n**Look for:**\n\n1. **Render-blocking resources**: JS\u002FCSS in `\u003Chead>` without `async`\u002F`defer`\u002F`media` attributes\n2. **Network chains**: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)\n3. **Missing preloads**: Critical resources (fonts, hero images, key scripts) not preloaded\n4. **Caching issues**: Missing or weak `Cache-Control`, `ETag`, or `Last-Modified` headers\n5. **Large payloads**: Uncompressed or oversized JS\u002FCSS bundles\n6. **Unused preconnects**: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.\n\nFor detailed request info:\n```\nget_network_request(reqid: \u003Cid>)\n```\n\n### Phase 4: Accessibility Snapshot\n\nTake an accessibility tree snapshot:\n```\ntake_snapshot(verbose: true)\n```\n\n**Flag high-level gaps:**\n- Missing or duplicate ARIA IDs\n- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)\n- Focus traps or missing focus indicators\n- Interactive elements without accessible names\n\n## Phase 5: Codebase Analysis\n\n**Skip if auditing a third-party site without codebase access.**\n\nAnalyze the codebase to understand where improvements can be made.\n\n### Detect Framework & Bundler\n\nSearch for configuration files to identify the stack:\n\n| Tool | Config Files |\n|------|--------------|\n| Webpack | `webpack.config.js`, `webpack.*.js` |\n| Vite | `vite.config.js`, `vite.config.ts` |\n| Rollup | `rollup.config.js`, `rollup.config.mjs` |\n| esbuild | `esbuild.config.js`, build scripts with `esbuild` |\n| Parcel | `.parcelrc`, `package.json` (parcel field) |\n| Next.js | `next.config.js`, `next.config.mjs` |\n| Nuxt | `nuxt.config.js`, `nuxt.config.ts` |\n| SvelteKit | `svelte.config.js` |\n| Astro | `astro.config.mjs` |\n\nAlso check `package.json` for framework dependencies and build scripts.\n\n### Tree-Shaking & Dead Code\n\n- **Webpack**: Check for `mode: 'production'`, `sideEffects` in package.json, `usedExports` optimization\n- **Vite\u002FRollup**: Tree-shaking enabled by default; check for `treeshake` options\n- **Look for**: Barrel files (`index.js` re-exports), large utility libraries imported wholesale (lodash, moment)\n\n### Unused JS\u002FCSS\n\n- Check for CSS-in-JS vs. static CSS extraction\n- Look for PurgeCSS\u002FUnCSS configuration (Tailwind's `content` config)\n- Identify dynamic imports vs. eager loading\n\n### Polyfills\n\n- Check for `@babel\u002Fpreset-env` targets and `useBuiltIns` setting\n- Look for `core-js` imports (often oversized)\n- Check `browserslist` config for overly broad targeting\n\n### Compression & Minification\n\n- Check for `terser`, `esbuild`, or `swc` minification\n- Look for gzip\u002Fbrotli compression in build output or server config\n- Check for source maps in production builds (should be external or disabled)\n\n## Output Format\n\nPresent findings as:\n\n1. **Core Web Vitals Summary** - Table with metric, value, and rating (good\u002Fneeds-improvement\u002Fpoor)\n2. **Top Issues** - Prioritized list of problems with estimated impact (high\u002Fmedium\u002Flow)\n3. **Recommendations** - Specific, actionable fixes with code snippets or config changes\n4. **Codebase Findings** - Framework\u002Fbundler detected, optimization opportunities (omit if no codebase access)\n","# Web Performance Audit\n\nYour knowledge of web performance metrics, thresholds, and tooling APIs may be outdated. **Prefer retrieval over pre-training** when citing specific numbers or recommendations.\n\n## Retrieval Sources\n\n| Source | How to retrieve | Use for |\n|--------|----------------|---------|\n| web.dev | `https:\u002F\u002Fweb.dev\u002Farticles\u002Fvitals` | Core Web Vitals thresholds, definitions |\n| Chrome DevTools docs | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Fdevtools\u002Fperformance` | Tooling APIs, trace analysis |\n| Lighthouse scoring | `https:\u002F\u002Fdeveloper.chrome.com\u002Fdocs\u002Flighthouse\u002Fperformance\u002Fperformance-scoring` | Score weights, metric thresholds |\n\n## FIRST: Verify MCP Tools Available\n\n**Run this before starting.** Try calling `navigate_page` or `performance_start_trace`. If unavailable, STOP—the chrome-devtools MCP server isn't configured.\n\nAsk the user to add this to their MCP config:\n\n```json\n\"chrome-devtools\": {\n  \"type\": \"local\",\n  \"command\": [\"npx\", \"-y\", \"chrome-devtools-mcp@latest\"]\n}\n```\n\n## Key Guidelines\n\n- **Be assertive**: Verify claims by checking network requests, DOM, or codebase—then state findings definitively.\n- **Verify before recommending**: Confirm something is unused before suggesting removal.\n- **Quantify impact**: Use estimated savings from insights. Don't prioritize changes with 0ms impact.\n- **Skip non-issues**: If render-blocking resources have 0ms estimated impact, note but don't recommend action.\n- **Be specific**: Say \"compress hero.png (450KB) to WebP\" not \"optimize images\".\n- **Prioritize ruthlessly**: A site with 200ms LCP and 0 CLS is already excellent—say so.\n\n## Quick Reference\n\n| Task | Tool Call |\n|------|-----------|\n| Load page | `navigate_page(url: \"...\")` |\n| Start trace | `performance_start_trace(autoStop: true, reload: true)` |\n| Analyze insight | `performance_analyze_insight(insightSetId: \"...\", insightName: \"...\")` |\n| List requests | `list_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", ...])` |\n| Request details | `get_network_request(reqid: \u003Cid>)` |\n| A11y snapshot | `take_snapshot(verbose: true)` |\n\n## Workflow\n\nCopy this checklist to track progress:\n\n```\nAudit Progress:\n- [ ] Phase 1: Performance trace (navigate + record)\n- [ ] Phase 2: Core Web Vitals analysis (includes CLS culprits)\n- [ ] Phase 3: Network analysis\n- [ ] Phase 4: Accessibility snapshot\n- [ ] Phase 5: Codebase analysis (skip if third-party site)\n```\n\n### Phase 1: Performance Trace\n\n1. Navigate to the target URL:\n   ```\n   navigate_page(url: \"\u003Ctarget-url>\")\n   ```\n\n2. Start a performance trace with reload to capture cold-load metrics:\n   ```\n   performance_start_trace(autoStop: true, reload: true)\n   ```\n\n3. Wait for trace completion, then retrieve results.\n\n**Troubleshooting:**\n- If trace returns empty or fails, verify the page loaded correctly with `navigate_page` first\n- If insight names don't match, inspect the trace response to list available insights\n\n### Phase 2: Core Web Vitals Analysis\n\nUse `performance_analyze_insight` to extract key metrics.\n\n**Note:** Insight names may vary across Chrome DevTools versions. If an insight name doesn't work, check the `insightSetId` from the trace response to discover available insights.\n\nCommon insight names:\n\n| Metric | Insight Name | What to Look For |\n|--------|--------------|------------------|\n| LCP | `LCPBreakdown` | Time to largest contentful paint; breakdown of TTFB, resource load, render delay |\n| CLS | `CLSCulprits` | Elements causing layout shifts (images without dimensions, injected content, font swaps) |\n| Render Blocking | `RenderBlocking` | CSS\u002FJS blocking first paint |\n| Document Latency | `DocumentLatency` | Server response time issues |\n| Network Dependencies | `NetworkRequestsDepGraph` | Request chains delaying critical resources |\n\nExample:\n```\nperformance_analyze_insight(insightSetId: \"\u003Cid-from-trace>\", insightName: \"LCPBreakdown\")\n```\n\n**Key thresholds (good\u002Fneeds-improvement\u002Fpoor):**\n- TTFB: \u003C 800ms \u002F \u003C 1.8s \u002F > 1.8s\n- FCP: \u003C 1.8s \u002F \u003C 3s \u002F > 3s\n- LCP: \u003C 2.5s \u002F \u003C 4s \u002F > 4s\n- INP: \u003C 200ms \u002F \u003C 500ms \u002F > 500ms\n- TBT: \u003C 200ms \u002F \u003C 600ms \u002F > 600ms\n- CLS: \u003C 0.1 \u002F \u003C 0.25 \u002F > 0.25\n- Speed Index: \u003C 3.4s \u002F \u003C 5.8s \u002F > 5.8s\n\n### Phase 3: Network Analysis\n\nList all network requests to identify optimization opportunities:\n```\nlist_network_requests(resourceTypes: [\"Script\", \"Stylesheet\", \"Document\", \"Font\", \"Image\"])\n```\n\n**Look for:**\n\n1. **Render-blocking resources**: JS\u002FCSS in `\u003Chead>` without `async`\u002F`defer`\u002F`media` attributes\n2. **Network chains**: Resources discovered late because they depend on other resources loading first (e.g., CSS imports, JS-loaded fonts)\n3. **Missing preloads**: Critical resources (fonts, hero images, key scripts) not preloaded\n4. **Caching issues**: Missing or weak `Cache-Control`, `ETag`, or `Last-Modified` headers\n5. **Large payloads**: Uncompressed or oversized JS\u002FCSS bundles\n6. **Unused preconnects**: If flagged, verify by checking if ANY requests went to that origin. If zero requests, it's definitively unused—recommend removal. If requests exist but loaded late, the preconnect may still be valuable.\n\nFor detailed request info:\n```\nget_network_request(reqid: \u003Cid>)\n```\n\n### Phase 4: Accessibility Snapshot\n\nTake an accessibility tree snapshot:\n```\ntake_snapshot(verbose: true)\n```\n\n**Flag high-level gaps:**\n- Missing or duplicate ARIA IDs\n- Elements with poor contrast ratios (check against WCAG AA: 4.5:1 for normal text, 3:1 for large text)\n- Focus traps or missing focus indicators\n- Interactive elements without accessible names\n\n## Phase 5: Codebase Analysis\n\n**Skip if auditing a third-party site without codebase access.**\n\nAnalyze the codebase to understand where improvements can be made.\n\n### Detect Framework & Bundler\n\nSearch for configuration files to identify the stack:\n\n| Tool | Config Files |\n|------|--------------|\n| Webpack | `webpack.config.js`, `webpack.*.js` |\n| Vite | `vite.config.js`, `vite.config.ts` |\n| Rollup | `rollup.config.js`, `rollup.config.mjs` |\n| esbuild | `esbuild.config.js`, build scripts with `esbuild` |\n| Parcel | `.parcelrc`, `package.json` (parcel field) |\n| Next.js | `next.config.js`, `next.config.mjs` |\n| Nuxt | `nuxt.config.js`, `nuxt.config.ts` |\n| SvelteKit | `svelte.config.js` |\n| Astro | `astro.config.mjs` |\n\nAlso check `package.json` for framework dependencies and build scripts.\n\n### Tree-Shaking & Dead Code\n\n- **Webpack**: Check for `mode: 'production'`, `sideEffects` in package.json, `usedExports` optimization\n- **Vite\u002FRollup**: Tree-shaking enabled by default; check for `treeshake` options\n- **Look for**: Barrel files (`index.js` re-exports), large utility libraries imported wholesale (lodash, moment)\n\n### Unused JS\u002FCSS\n\n- Check for CSS-in-JS vs. static CSS extraction\n- Look for PurgeCSS\u002FUnCSS configuration (Tailwind's `content` config)\n- Identify dynamic imports vs. eager loading\n\n### Polyfills\n\n- Check for `@babel\u002Fpreset-env` targets and `useBuiltIns` setting\n- Look for `core-js` imports (often oversized)\n- Check `browserslist` config for overly broad targeting\n\n### Compression & Minification\n\n- Check for `terser`, `esbuild`, or `swc` minification\n- Look for gzip\u002Fbrotli compression in build output or server config\n- Check for source maps in production builds (should be external or disabled)\n\n## Output Format\n\nPresent findings as:\n\n1. **Core Web Vitals Summary** - Table with metric, value, and rating (good\u002Fneeds-improvement\u002Fpoor)\n2. **Top Issues** - Prioritized list of problems with estimated impact (high\u002Fmedium\u002Flow)\n3. **Recommendations** - Specific, actionable fixes with code snippets or config changes\n4. **Codebase Findings** - Framework\u002Fbundler detected, optimization opportunities (omit if no codebase access)\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fweb-perf",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":65,"prompt":75,"zipAvailable":76},[66,69,72],{"tool":67,"command":68},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill web-perf",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill web-perf",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill web-perf","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fweb-perf\u002FSKILL.md",true,[],[79,88,96,104,112,120],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":87},"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":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":87},"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":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":87},"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":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":87},"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":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":116,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":87},"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":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":87},"01M73G086AXAH9DW1H5G5N3CPB","dbs-video-extract","接收抖音、小红书、微信视频号等短视频链接或分享文案，查询作品／账号数据并提取语音文字稿，按作者和标题归档为 Markdown。用户希望完整解析短视频、取得数据或文字稿时使用；运行前检查 TikHub 与轻抖使用凭证，缺少时用新手能理解的方式引导购买和安全配置。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fdbs-video-extract\u002FSKILL.md",[],[]]