[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70N1FQ42QH3SMHSSVTFWHTW":3,"skill-same:01M70N1FQ42QH3SMHSSVTFWHTW":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":23,"publishedAt":40,"linkOnly":41,"markdownContent":42,"markdownBody":43,"frontMatter":44,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":52,"ownerHtmlUrl":53,"ownerBlogUrl":54,"ownerDescription":55,"updatedAt":56,"install":57,"resources":69},"01M70N1FQ42QH3SMHSSVTFWHTW","overdrive",null,"Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.","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\u002Foverdrive\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39],"animations","driven","user","impress","scroll","with","spring","use","true","make","go","past","shaders","limits","when","physics","2026-11-10 10:12:30",false,"---\nname: overdrive\ndescription: Pushes interfaces past conventional limits with technically ambitious implementations — shaders, spring physics, scroll-driven reveals, 60fps animations. Use when the user wants to wow, impress, go all-out, or make something that feels extraordinary.\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nStart your response with:\n\n```\n──────────── ⚡ OVERDRIVE ─────────────\n》》》 Entering overdrive mode...\n```\n\nPush an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic.\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**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what \"extraordinary\" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate.\n\n### Propose Before Building\n\nThis skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST:\n\n1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like.\n2. **STOP and call the AskUserQuestion tool to clarify.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity).\n3. Only proceed with the direction the user confirms.\n\nSkipping this step risks building something embarrassing that needs to be thrown away.\n\n### Iterate with Browser Automation\n\nTechnically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between \"technically works\" and \"looks extraordinary\" is closed through visual iteration, not code alone.\n\n---\n\n## Assess What \"Extraordinary\" Means Here\n\nThe right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say \"wow, that's nice\"?**\n\n### For visual\u002Fmarketing surfaces\nPages, hero sections, landing pages, portfolios — the \"wow\" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor.\n\n### For functional UI\nTables, forms, dialogs, navigation — the \"wow\" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics.\n\n### For performance-critical UI\nThe \"wow\" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates.\n\n### For data-heavy interfaces\nCharts and dashboards — the \"wow\" is in fluidity: GPU-accelerated rendering via Canvas\u002FWebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally.\n\n**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around.\n\n## The Toolkit\n\nOrganized by what you're trying to achieve, not by technology name.\n\n### Make transitions feel cinematic\n- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations.\n- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes\n- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver.\n\n### Tie animation to scroll position\n- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome\u002FEdge\u002FSafari; Firefox: flag only — always provide a static fallback)\n\n### Render beyond CSS\n- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express.\n- **WebGPU** (Chrome\u002FEdge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2.\n- **Canvas 2D \u002F OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas.\n- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable.\n\n### Make data feel alive\n- **Virtual scrolling** — render only visible rows for tables\u002Flists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones.\n- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG\u002FDOM. Libraries: deck.gl, regl-based custom renderers.\n- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts.\n\n### Animate complex properties\n- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate.\n- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography.\n\n### Push performance boundaries\n- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank.\n- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background.\n- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs.\n\n### Interact with the device\n- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start.\n- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission.\n\n**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary.\n\n## Implement with Discipline\n\n### Progressive enhancement is non-negotiable\n\nEvery technique must degrade gracefully. The experience without the enhancement must still be good.\n\n```css\n@supports (animation-timeline: scroll()) {\n  .hero { animation-timeline: scroll(); }\n}\n```\n\n```javascript\nif ('gpu' in navigator) { \u002F* WebGPU *\u002F }\nelse if (canvas.getContext('webgl2')) { \u002F* WebGL2 fallback *\u002F }\n\u002F* CSS-only fallback must still look good *\u002F\n```\n\n### Performance rules\n\n- Target 60fps. If dropping below 50, simplify.\n- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative.\n- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport.\n- Pause off-screen rendering. Kill what you can't see.\n- Test on real mid-range devices, not just your development machine.\n\n### Polish is the difference\n\nThe gap between \"cool\" and \"extraordinary\" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable.\n\n**NEVER**:\n- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion\n- Ship effects that cause jank on mid-range devices\n- Use bleeding-edge APIs without a functional fallback\n- Add sound without explicit user opt-in\n- Use technical ambition to mask weak design fundamentals — fix those first with other skills\n- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise\n\n## Verify the Result\n\n- **The wow test**: Show it to someone who hasn't seen it. Do they react?\n- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice?\n- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth?\n- **The accessibility test**: Enable reduced motion. Still beautiful?\n- **The context test**: Does this make sense for THIS brand and audience?\n\nRemember: \"Technically extraordinary\" isn't about using the newest API. It's about making an interface do something users didn't think a website could do.","Start your response with:\n\n```\n──────────── ⚡ OVERDRIVE ─────────────\n》》》 Entering overdrive mode...\n```\n\nPush an interface past conventional limits. This isn't just about visual effects — it's about using the full power of the browser to make any part of an interface feel extraordinary: a table that handles a million rows, a dialog that morphs from its trigger, a form that validates in real-time with streaming feedback, a page transition that feels cinematic.\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**EXTRA IMPORTANT FOR THIS SKILL**: Context determines what \"extraordinary\" means. A particle system on a creative portfolio is impressive. The same particle system on a settings page is embarrassing. But a settings page with instant optimistic saves and animated state transitions? That's extraordinary too. Understand the project's personality and goals before deciding what's appropriate.\n\n### Propose Before Building\n\nThis skill has the highest potential to misfire. Do NOT jump straight into implementation. You MUST:\n\n1. **Think through 2-3 different directions** — consider different techniques, levels of ambition, and aesthetic approaches. For each direction, briefly describe what the result would look and feel like.\n2. **STOP and call the AskUserQuestion tool to clarify.** to present these directions and get the user's pick before writing any code. Explain trade-offs (browser support, performance cost, complexity).\n3. Only proceed with the direction the user confirms.\n\nSkipping this step risks building something embarrassing that needs to be thrown away.\n\n### Iterate with Browser Automation\n\nTechnically ambitious effects almost never work on the first try. You MUST actively use browser automation tools to preview your work, visually verify the result, and iterate. Do not assume the effect looks right — check it. Expect multiple rounds of refinement. The gap between \"technically works\" and \"looks extraordinary\" is closed through visual iteration, not code alone.\n\n---\n\n## Assess What \"Extraordinary\" Means Here\n\nThe right kind of technical ambition depends entirely on what you're working with. Before choosing a technique, ask: **what would make a user of THIS specific interface say \"wow, that's nice\"?**\n\n### For visual\u002Fmarketing surfaces\nPages, hero sections, landing pages, portfolios — the \"wow\" is often sensory: a scroll-driven reveal, a shader background, a cinematic page transition, generative art that responds to the cursor.\n\n### For functional UI\nTables, forms, dialogs, navigation — the \"wow\" is in how it FEELS: a dialog that morphs from the button that triggered it via View Transitions, a data table that renders 100k rows at 60fps via virtual scrolling, a form with streaming validation that feels instant, drag-and-drop with spring physics.\n\n### For performance-critical UI\nThe \"wow\" is invisible but felt: a search that filters 50k items without a flicker, a complex form that never blocks the main thread, an image editor that processes in near-real-time. The interface just never hesitates.\n\n### For data-heavy interfaces\nCharts and dashboards — the \"wow\" is in fluidity: GPU-accelerated rendering via Canvas\u002FWebGL for massive datasets, animated transitions between data states, force-directed graph layouts that settle naturally.\n\n**The common thread**: something about the implementation goes beyond what users expect from a web interface. The technique serves the experience, not the other way around.\n\n## The Toolkit\n\nOrganized by what you're trying to achieve, not by technology name.\n\n### Make transitions feel cinematic\n- **View Transitions API** (same-document: all browsers; cross-document: no Firefox) — shared element morphing between states. A list item expanding into a detail page. A button morphing into a dialog. This is the closest thing to native FLIP animations.\n- **`@starting-style`** (all browsers) — animate elements from `display: none` to visible with CSS only, including entry keyframes\n- **Spring physics** — natural motion with mass, tension, and damping instead of cubic-bezier. Libraries: motion (formerly Framer Motion), GSAP, or roll your own spring solver.\n\n### Tie animation to scroll position\n- **Scroll-driven animations** (`animation-timeline: scroll()`) — CSS-only, no JS. Parallax, progress bars, reveal sequences all driven by scroll position. (Chrome\u002FEdge\u002FSafari; Firefox: flag only — always provide a static fallback)\n\n### Render beyond CSS\n- **WebGL** (all browsers) — shader effects, post-processing, particle systems. Libraries: Three.js, OGL (lightweight), regl. Use for effects CSS can't express.\n- **WebGPU** (Chrome\u002FEdge; Safari partial; Firefox: flag only) — next-gen GPU compute. More powerful than WebGL but limited browser support. Always fall back to WebGL2.\n- **Canvas 2D \u002F OffscreenCanvas** — custom rendering, pixel manipulation, or moving heavy rendering off the main thread entirely via Web Workers + OffscreenCanvas.\n- **SVG filter chains** — displacement maps, turbulence, morphology for organic distortion effects. CSS-animatable.\n\n### Make data feel alive\n- **Virtual scrolling** — render only visible rows for tables\u002Flists with tens of thousands of items. No library required for simple cases; TanStack Virtual for complex ones.\n- **GPU-accelerated charts** — Canvas or WebGL-rendered data visualization for datasets too large for SVG\u002FDOM. Libraries: deck.gl, regl-based custom renderers.\n- **Animated data transitions** — morph between chart states rather than replacing. D3's `transition()` or View Transitions for DOM-based charts.\n\n### Animate complex properties\n- **`@property`** (all browsers) — register custom CSS properties with types, enabling animation of gradients, colors, and complex values that CSS can't normally interpolate.\n- **Web Animations API** (all browsers) — JavaScript-driven animations with the performance of CSS. Composable, cancellable, reversible. The foundation for complex choreography.\n\n### Push performance boundaries\n- **Web Workers** — move computation off the main thread. Heavy data processing, image manipulation, search indexing — anything that would cause jank.\n- **OffscreenCanvas** — render in a Worker thread. The main thread stays free while complex visuals render in the background.\n- **WASM** — near-native performance for computation-heavy features. Image processing, physics simulations, codecs.\n\n### Interact with the device\n- **Web Audio API** — spatial audio, audio-reactive visualizations, sonic feedback. Requires user gesture to start.\n- **Device APIs** — orientation, ambient light, geolocation. Use sparingly and always with user permission.\n\n**NOTE**: This skill is about enhancing how an interface FEELS, not changing what a product DOES. Adding real-time collaboration, offline support, or new backend capabilities are product decisions, not UI enhancements. Focus on making existing features feel extraordinary.\n\n## Implement with Discipline\n\n### Progressive enhancement is non-negotiable\n\nEvery technique must degrade gracefully. The experience without the enhancement must still be good.\n\n```css\n@supports (animation-timeline: scroll()) {\n  .hero { animation-timeline: scroll(); }\n}\n```\n\n```javascript\nif ('gpu' in navigator) { \u002F* WebGPU *\u002F }\nelse if (canvas.getContext('webgl2')) { \u002F* WebGL2 fallback *\u002F }\n\u002F* CSS-only fallback must still look good *\u002F\n```\n\n### Performance rules\n\n- Target 60fps. If dropping below 50, simplify.\n- Respect `prefers-reduced-motion` — always. Provide a beautiful static alternative.\n- Lazy-initialize heavy resources (WebGL contexts, WASM modules) only when near viewport.\n- Pause off-screen rendering. Kill what you can't see.\n- Test on real mid-range devices, not just your development machine.\n\n### Polish is the difference\n\nThe gap between \"cool\" and \"extraordinary\" is in the last 20% of refinement: the easing curve on a spring animation, the timing offset in a staggered reveal, the subtle secondary motion that makes a transition feel physical. Don't ship the first version that works — ship the version that feels inevitable.\n\n**NEVER**:\n- Ignore `prefers-reduced-motion` — this is an accessibility requirement, not a suggestion\n- Ship effects that cause jank on mid-range devices\n- Use bleeding-edge APIs without a functional fallback\n- Add sound without explicit user opt-in\n- Use technical ambition to mask weak design fundamentals — fix those first with other skills\n- Layer multiple competing extraordinary moments — focus creates impact, excess creates noise\n\n## Verify the Result\n\n- **The wow test**: Show it to someone who hasn't seen it. Do they react?\n- **The removal test**: Take it away. Does the experience feel diminished, or does nobody notice?\n- **The device test**: Run it on a phone, a tablet, a Chromebook. Still smooth?\n- **The accessibility test**: Enable reduced motion. Still beautiful?\n- **The context test**: Does this make sense for THIS brand and audience?\n\nRemember: \"Technically extraordinary\" isn't about using the newest API. It's about making an interface do something users didn't think a website could do.",{"name":5,"description":7,"argument-hint":45,"user-invocable":46},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Foverdrive",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":58,"prompt":68,"zipAvailable":46},[59,62,65],{"tool":60,"command":61},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill overdrive",{"tool":63,"command":64},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill overdrive",{"tool":66,"command":67},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill overdrive","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Foverdrive\u002FSKILL.md",[],[71,88,120,144,166,186],{"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":6,"sourceHtmlUrl":75,"categories":76,"keywords":80,"publishedAt":40},"01M70P17DAD4C1C47NPH6A96EM","xiaolai-methodology","以李笑来(Li Xiaolai)的思考方式、方法论与表达风格,为用户做全方位 1-on-1 教练指导,覆盖创业、赚钱、投资、学习、自学、读书写作、用 AI、以及人生心态与自我管理。当用户提到 \"李笑来\"、\"笑来\"、\"笑来老师\"、\"扮演李笑来\"、\"找笑来聊聊\"、\"笑来怎么看\"、\"xiaolai\"、\"把时间当作朋友\"、\"通往财富自由之路\"、\"定投改变命运\"、\"韭菜的自我修养\"、\"自学是门手艺\"、\"让时间陪你慢慢变富\"、\"七年就是一辈子\"、\"元认知\"、\"活在未来\"、\"复利\u002F长期主义\"、\"践行\"、\"痴迷改进\"、\"个人商业模式\u002F出售时间\"、\"睡后收入\"、\"定投\"、\"财富自由\"、\"操作系统升级\"、\"最少必要知识\"、\"北极星提示词\"、\"用 AI 该怎么学\u002F思考\" 等任一触发词,或当用户带着关于创业\u002F赚钱\u002F投资\u002F学习\u002F职业\u002F重大人生决策的困惑、希望被人用笑来式的「逻辑 + 大白话 + 类比 + 重新定义 + 践行导向」来点醒和指导时,自动进入李笑来教练模式。","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fxiaolai-methodology\u002FSKILL.md",[77],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",[81,82,83,84,85,86,87],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"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":6,"sourceHtmlUrl":92,"categories":93,"keywords":100,"publishedAt":40},"01M70P13NB9YP7ACJR1S861CDS","zread","Produce and consume a wiki-style knowledge base for a code repository via the `zread` CLI and its on-disk output under `.\u002F.zread\u002Fwiki\u002F`. Use this skill whenever the user wants to understand, onboard onto, explore, summarize, map, or get an overview of an unfamiliar codebase; asks for architecture docs, a project wiki, a repo walkthrough, module\u002Fpackage explanations, or \"what does this repo do\"; wants to generate, regenerate, resume, browse, or serve code documentation locally; or mentions zread \u002F zread.ai directly. Also use it proactively before diving into a large unknown repo — if `.\u002F.zread\u002Fwiki\u002Fcurrent` exists, read the generated pages instead of crawling source file-by-file; if it doesn't, consider offering to run `zread generate`. The trigger is the intent (understand a codebase through generated docs), not the literal word \"zread\".","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fzread\u002FSKILL.md",[94,95],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[90,101,102,103,104,105,106,107,108,109,110,111,112,113,114,115,116,117,118,119],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","run","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"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":130,"publishedAt":40},"01M70P10S4SWMZQ8BJAFBFDRW3","youtube","Launch the YouTube Creator Agent to auto-generate videos.\nUse when: user types \u002Fyoutube, wants to create YouTube videos,\ngenerate video content, or upload to YouTube.\nKeywords: youtube, video, 视频, 创作视频, 发布视频","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[126,127],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},"01JBSEEDCAT000000000000036","内容创作者",[122,26,131,132,133,134,135,136,109,137,138,139,38,31,140,141,142,143],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":151,"publishedAt":40},"01M70P0YE95D8BACZCGV8BK90K","youtube-script-sync","Sync, update, or optimize Tony's GetNote knowledge base `Youtube视频逐字稿` by turning each parent recording or first-person idea note into an idempotent child note containing a directly recordable YouTube long-video or Shorts script. Use when the user says “更新\u002F同步\u002F优化 Youtube视频逐字稿知识库”, or says “更新\u002F同步\u002F优化该知识库” while this knowledge base is the active context.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-script-sync\u002FSKILL.md",[150],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[152,153,122,154,155,142,156,157,158,159,160,161,162,163,107,164,38,31,101,165],"sync","script","youtube script sync","recording","shorts","first","base","person","update","active","child","optimize","idempotent","long",{"skillNo":167,"name":168,"nameZh":6,"description":169,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":170,"categories":171,"keywords":176,"publishedAt":40},"01M70P0WMV5XT0EEC0N445PW07","writing-skills","How to write SKILL.md files that trigger reliably and teach effectively. Use when creating, improving, or reviewing Claude Code skills.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-skills\u002FSKILL.md",[172,173,174,175],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":96,"categoryName":97,"taxonomyType":98,"taxonomyTypeDesc":99},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},[177,86,178,179,180,181,117,38,31,182,183,184,185],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":187,"name":188,"nameZh":6,"description":189,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":190,"categories":191,"keywords":194,"publishedAt":40},"01M70P0SJFR4YVJQBGMHKGSKXT","writing-rules","How to write .claude\u002Frules\u002F files that Claude actually follows. Use when creating, improving, or reviewing project rules.","https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fxiaolai\u002Fnlpm\u002Fskills\u002Fnlpm\u002Fwriting-rules\u002FSKILL.md",[192,193],{"categoryNo":78,"categoryName":79,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":128,"categoryName":129,"taxonomyType":98,"taxonomyTypeDesc":99},[195,86,196,105,197,183,38,178,181,31,184],"Rules","writing rules","project rules"]