[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70MMVK6CPYSDZ3XQYPK82A4":3,"skill-same:01M70MMVK6CPYSDZ3XQYPK82A4":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},"01M70MMVK6CPYSDZ3XQYPK82A4","tailwind",null,"Tailwind CSS v4.2 browser-runtime patterns for HyperFrames compositions. Use when scaffolding or editing projects created with `hyperframes init --tailwind`, writing Tailwind utility classes in composition HTML, adding CSS-first Tailwind v4 theme tokens, debugging v3 vs v4 syntax, or deciding when to compile Tailwind to CSS instead of using the browser runtime.","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\u002Fhyperframes-tailwind\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发","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],"Tailwind","tailwind v4","compile","editing","runtime","for","theme","html","patterns","syntax","browser","when","debugging","utility","writing","init","scaffolding","css","Composition","projects","2026-11-10 10:12:30",false,"---\nname: tailwind\ndescription: Tailwind CSS v4.2 browser-runtime patterns for HyperFrames compositions. Use when scaffolding or editing projects created with `hyperframes init --tailwind`, writing Tailwind utility classes in composition HTML, adding CSS-first Tailwind v4 theme tokens, debugging v3 vs v4 syntax, or deciding when to compile Tailwind to CSS instead of using the browser runtime.\n---\n\n# Tailwind CSS for HyperFrames\n\nHyperFrames `init --tailwind` uses the Tailwind browser runtime pinned to `@tailwindcss\u002Fbrowser@4.2.4`. Treat that as Tailwind v4, not v3.\n\nThis skill is for composition HTML generated by the CLI. It is not for `packages\u002Fstudio`, which still uses Tailwind v3 internally with `tailwind.config.js`, PostCSS, and `@tailwind` directives.\n\n## When To Use\n\n- The user asks for Tailwind in a HyperFrames composition.\n- A project was created with `hyperframes init --tailwind`.\n- You see `window.__tailwindReady` in `index.html`.\n- You need utility classes, CSS-first theme tokens, custom utilities, or v3-to-v4 migration guidance.\n- The render has missing styles and the project is relying on the browser runtime.\n\n## Version Contract\n\n- Pinned runtime: `@tailwindcss\u002Fbrowser@4.2.4`.\n- Browser runtime script is injected by the CLI. Do not replace it with `cdn.tailwindcss.com`.\n- HyperFrames waits for `window.__tailwindReady` before frame capture starts.\n- The readiness shim must stay deterministic: no render-loop polling APIs, no clock-based retries, no runtime network fetches beyond the pinned Tailwind runtime script.\n- For offline, locked-down, or production-stable renders, compile Tailwind to CSS and include the stylesheet directly instead of relying on the browser runtime.\n\n## v4 Rules\n\nTailwind v4 is CSS-first:\n\n```html\n\u003Cstyle type=\"text\u002Ftailwindcss\">\n  @theme {\n    --color-brand: oklch(0.68 0.2 252);\n    --font-display: \"Inter\", sans-serif;\n  }\n\n  @utility headline-balance {\n    text-wrap: balance;\n    letter-spacing: 0;\n  }\n\u003C\u002Fstyle>\n```\n\nAvoid v3 setup patterns in browser-runtime compositions:\n\n```css\n\u002F* Do not use these in Tailwind v4 browser-runtime compositions. *\u002F\n@tailwind base;\n@tailwind components;\n@tailwind utilities;\n```\n\nDo not add a `tailwind.config.js` just to define colors, fonts, spacing, or utilities for a v4 browser-runtime composition. Use `@theme` and `@utility` in a `text\u002Ftailwindcss` style block.\n\nIf you truly need an existing JavaScript config for a compiled v4 build, load it explicitly from CSS with `@config`, then validate in the browser. Do not assume v4 auto-detects v3 config files.\n\n## HyperFrames Composition Pattern\n\nKeep Tailwind responsible for static layout and visual style. Keep motion timing in GSAP or another seekable adapter.\n\n```html\n\u003Csection\n  class=\"clip absolute inset-0 grid place-items-center bg-zinc-950 text-white\"\n  data-start=\"0\"\n  data-duration=\"5\"\n  data-track-index=\"1\"\n>\n  \u003Cdiv class=\"w-[1280px] max-w-[82vw] text-center\">\n    \u003Cp class=\"mb-6 text-xl font-medium uppercase tracking-[0.18em] text-cyan-300\">\n      Render-ready Tailwind\n    \u003C\u002Fp>\n    \u003Ch1 class=\"text-7xl font-black leading-none text-balance\">\n      Utility classes, deterministic frames.\n    \u003C\u002Fh1>\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nFor repeated items, prefer class lists plus CSS custom properties over generating class names dynamically:\n\n```html\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 0\">\u003C\u002Fspan>\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 1\">\u003C\u002Fspan>\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 2\">\u003C\u002Fspan>\n```\n\n## Dynamic Class Safety\n\nTailwind's browser runtime scans the current document and generates CSS for class names it can see. Do not build render-critical class names only at seek time:\n\n```js\n\u002F\u002F Risky: Tailwind may not see every generated class before capture.\nelement.className = `bg-${color}-500`;\n```\n\nUse complete class names in HTML, data attributes, or explicit CSS instead:\n\n```html\n\u003Cdiv data-tone=\"blue\" class=\"bg-blue-500 data-[tone=rose]:bg-rose-500\">\u003C\u002Fdiv>\n```\n\nIf a generated class is unavoidable, make sure the full class token appears in a `text\u002Ftailwindcss` block before validation.\n\n## Video-Specific Guardrails\n\n- Use stable dimensions: `w-[...]`, `h-[...]`, `aspect-video`, `grid`, `flex`, and fixed padding for video layouts.\n- Prefer transforms and opacity for animated properties.\n- Keep Tailwind transitions out of render-critical timing unless a seekable runtime owns the state.\n- Avoid hover, focus, scroll, viewport, or pointer variants for content that must render deterministically.\n- Use explicit border colors. Tailwind v4 changed the default border behavior from v3, so `border border-white\u002F20` is safer than bare `border`.\n- Use v4 utility names: `shadow-xs`, `rounded-xs`, `outline-hidden`, `shrink-*`, and `grow-*` where those replacements apply.\n- Be careful with modern CSS utilities if the output needs older browser support. Tailwind v4 targets modern browsers.\n\n## Validation\n\nAfter editing a Tailwind-enabled composition:\n\n```bash\nnpx hyperframes lint\nnpx hyperframes validate\nnpx hyperframes inspect\n```\n\nFor a render proof:\n\n```bash\nnpx hyperframes render . --workers 1 --quality draft --output tailwind-proof.mp4\n```\n\nThe validation path should show no missing-style flashes on frame 0. If styles appear in preview but not render, check that `window.__tailwindReady` exists and resolves before capture.\n\n## Quick Debug Checklist\n\n1. Confirm the project was scaffolded with `hyperframes init --tailwind`.\n2. Confirm the script points to `@tailwindcss\u002Fbrowser@4.2.4`.\n3. Confirm `window.__tailwindReady` is present.\n4. Replace v3 `@tailwind` directives with v4 browser-runtime CSS.\n5. Move custom tokens from `tailwind.config.js` to `@theme`.\n6. Replace dynamically assembled classes with complete static tokens.\n7. Run `npx hyperframes validate` and render a short proof.\n\n## Credits And References\n\n- Tailwind CSS official v4 installation, upgrade, and compatibility docs: https:\u002F\u002Ftailwindcss.com\u002Fdocs\n- Tailwind CSS v4 release notes: https:\u002F\u002Ftailwindcss.com\u002Fblog\u002Ftailwindcss-v4\n- Community Tailwind skills were reviewed for v4 gotchas and skill shape, but this skill keeps the durable contract in-repo and HyperFrames-specific.\n","# Tailwind CSS for HyperFrames\n\nHyperFrames `init --tailwind` uses the Tailwind browser runtime pinned to `@tailwindcss\u002Fbrowser@4.2.4`. Treat that as Tailwind v4, not v3.\n\nThis skill is for composition HTML generated by the CLI. It is not for `packages\u002Fstudio`, which still uses Tailwind v3 internally with `tailwind.config.js`, PostCSS, and `@tailwind` directives.\n\n## When To Use\n\n- The user asks for Tailwind in a HyperFrames composition.\n- A project was created with `hyperframes init --tailwind`.\n- You see `window.__tailwindReady` in `index.html`.\n- You need utility classes, CSS-first theme tokens, custom utilities, or v3-to-v4 migration guidance.\n- The render has missing styles and the project is relying on the browser runtime.\n\n## Version Contract\n\n- Pinned runtime: `@tailwindcss\u002Fbrowser@4.2.4`.\n- Browser runtime script is injected by the CLI. Do not replace it with `cdn.tailwindcss.com`.\n- HyperFrames waits for `window.__tailwindReady` before frame capture starts.\n- The readiness shim must stay deterministic: no render-loop polling APIs, no clock-based retries, no runtime network fetches beyond the pinned Tailwind runtime script.\n- For offline, locked-down, or production-stable renders, compile Tailwind to CSS and include the stylesheet directly instead of relying on the browser runtime.\n\n## v4 Rules\n\nTailwind v4 is CSS-first:\n\n```html\n\u003Cstyle type=\"text\u002Ftailwindcss\">\n  @theme {\n    --color-brand: oklch(0.68 0.2 252);\n    --font-display: \"Inter\", sans-serif;\n  }\n\n  @utility headline-balance {\n    text-wrap: balance;\n    letter-spacing: 0;\n  }\n\u003C\u002Fstyle>\n```\n\nAvoid v3 setup patterns in browser-runtime compositions:\n\n```css\n\u002F* Do not use these in Tailwind v4 browser-runtime compositions. *\u002F\n@tailwind base;\n@tailwind components;\n@tailwind utilities;\n```\n\nDo not add a `tailwind.config.js` just to define colors, fonts, spacing, or utilities for a v4 browser-runtime composition. Use `@theme` and `@utility` in a `text\u002Ftailwindcss` style block.\n\nIf you truly need an existing JavaScript config for a compiled v4 build, load it explicitly from CSS with `@config`, then validate in the browser. Do not assume v4 auto-detects v3 config files.\n\n## HyperFrames Composition Pattern\n\nKeep Tailwind responsible for static layout and visual style. Keep motion timing in GSAP or another seekable adapter.\n\n```html\n\u003Csection\n  class=\"clip absolute inset-0 grid place-items-center bg-zinc-950 text-white\"\n  data-start=\"0\"\n  data-duration=\"5\"\n  data-track-index=\"1\"\n>\n  \u003Cdiv class=\"w-[1280px] max-w-[82vw] text-center\">\n    \u003Cp class=\"mb-6 text-xl font-medium uppercase tracking-[0.18em] text-cyan-300\">\n      Render-ready Tailwind\n    \u003C\u002Fp>\n    \u003Ch1 class=\"text-7xl font-black leading-none text-balance\">\n      Utility classes, deterministic frames.\n    \u003C\u002Fh1>\n  \u003C\u002Fdiv>\n\u003C\u002Fsection>\n```\n\nFor repeated items, prefer class lists plus CSS custom properties over generating class names dynamically:\n\n```html\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 0\">\u003C\u002Fspan>\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 1\">\u003C\u002Fspan>\n\u003Cspan class=\"inline-block translate-y-[calc(var(--i)*6px)] opacity-80\" style=\"--i: 2\">\u003C\u002Fspan>\n```\n\n## Dynamic Class Safety\n\nTailwind's browser runtime scans the current document and generates CSS for class names it can see. Do not build render-critical class names only at seek time:\n\n```js\n\u002F\u002F Risky: Tailwind may not see every generated class before capture.\nelement.className = `bg-${color}-500`;\n```\n\nUse complete class names in HTML, data attributes, or explicit CSS instead:\n\n```html\n\u003Cdiv data-tone=\"blue\" class=\"bg-blue-500 data-[tone=rose]:bg-rose-500\">\u003C\u002Fdiv>\n```\n\nIf a generated class is unavoidable, make sure the full class token appears in a `text\u002Ftailwindcss` block before validation.\n\n## Video-Specific Guardrails\n\n- Use stable dimensions: `w-[...]`, `h-[...]`, `aspect-video`, `grid`, `flex`, and fixed padding for video layouts.\n- Prefer transforms and opacity for animated properties.\n- Keep Tailwind transitions out of render-critical timing unless a seekable runtime owns the state.\n- Avoid hover, focus, scroll, viewport, or pointer variants for content that must render deterministically.\n- Use explicit border colors. Tailwind v4 changed the default border behavior from v3, so `border border-white\u002F20` is safer than bare `border`.\n- Use v4 utility names: `shadow-xs`, `rounded-xs`, `outline-hidden`, `shrink-*`, and `grow-*` where those replacements apply.\n- Be careful with modern CSS utilities if the output needs older browser support. Tailwind v4 targets modern browsers.\n\n## Validation\n\nAfter editing a Tailwind-enabled composition:\n\n```bash\nnpx hyperframes lint\nnpx hyperframes validate\nnpx hyperframes inspect\n```\n\nFor a render proof:\n\n```bash\nnpx hyperframes render . --workers 1 --quality draft --output tailwind-proof.mp4\n```\n\nThe validation path should show no missing-style flashes on frame 0. If styles appear in preview but not render, check that `window.__tailwindReady` exists and resolves before capture.\n\n## Quick Debug Checklist\n\n1. Confirm the project was scaffolded with `hyperframes init --tailwind`.\n2. Confirm the script points to `@tailwindcss\u002Fbrowser@4.2.4`.\n3. Confirm `window.__tailwindReady` is present.\n4. Replace v3 `@tailwind` directives with v4 browser-runtime CSS.\n5. Move custom tokens from `tailwind.config.js` to `@theme`.\n6. Replace dynamically assembled classes with complete static tokens.\n7. Run `npx hyperframes validate` and render a short proof.\n\n## Credits And References\n\n- Tailwind CSS official v4 installation, upgrade, and compatibility docs: https:\u002F\u002Ftailwindcss.com\u002Fdocs\n- Tailwind CSS v4 release notes: https:\u002F\u002Ftailwindcss.com\u002Fblog\u002Ftailwindcss-v4\n- Community Tailwind skills were reviewed for v4 gotchas and skill shape, but this skill keeps the durable contract in-repo and HyperFrames-specific.\n",{"name":5,"description":7},"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fhyperframes-tailwind",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 tailwind",{"tool":70,"command":71},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill tailwind",{"tool":73,"command":74},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill tailwind","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fhyperframes-tailwind\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",[],[]]