[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M70MZ664CBJD170ES3CYPH34":3,"skill-same:01M70MZ664CBJD170ES3CYPH34":72},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":71},"01M70MZ664CBJD170ES3CYPH34","onboard",null,"Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.","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\u002Fonboard\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000038","人力资源","PROFESSION","适用职业",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"activation","onboarding","user","empty","help","first","users","use","true","value","run","new user","when","new","flows","time","states","getting started","2026-11-10 10:12:30",false,"---\nname: onboard\ndescription: Designs and improves onboarding flows, empty states, and first-run experiences to help users reach value quickly. Use when the user mentions onboarding, first-time users, empty states, activation, getting started, or new user flows.\nuser-invocable: true\nargument-hint: \"[target]\"\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. Additionally gather: the \"aha moment\" you want users to reach, and users' experience level.\n\n---\n\nCreate or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.\n\n## Assess Onboarding Needs\n\nUnderstand what users need to learn and why:\n\n1. **Identify the challenge**:\n   - What are users trying to accomplish?\n   - What's confusing or unclear about current experience?\n   - Where do users get stuck or drop off?\n   - What's the \"aha moment\" we want users to reach?\n\n2. **Understand the users**:\n   - What's their experience level? (Beginners, power users, mixed?)\n   - What's their motivation? (Excited and exploring? Required by work?)\n   - What's their time commitment? (5 minutes? 30 minutes?)\n   - What alternatives do they know? (Coming from competitor? New to category?)\n\n3. **Define success**:\n   - What's the minimum users need to learn to be successful?\n   - What's the key action we want them to take? (First project? First invite?)\n   - How do we know onboarding worked? (Completion rate? Time to value?)\n\n**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.\n\n## Onboarding Principles\n\nFollow these core principles:\n\n### Show, Don't Tell\n- Demonstrate with working examples, not just descriptions\n- Provide real functionality in onboarding, not separate tutorial mode\n- Use progressive disclosure - teach one thing at a time\n\n### Make It Optional (When Possible)\n- Let experienced users skip onboarding\n- Don't block access to product\n- Provide \"Skip\" or \"I'll explore on my own\" options\n\n### Time to Value\n- Get users to their \"aha moment\" ASAP\n- Front-load most important concepts\n- Teach 20% that delivers 80% of value\n- Save advanced features for contextual discovery\n\n### Context Over Ceremony\n- Teach features when users need them, not upfront\n- Empty states are onboarding opportunities\n- Tooltips and hints at point of use\n\n### Respect User Intelligence\n- Don't patronize or over-explain\n- Be concise and clear\n- Assume users can figure out standard patterns\n\n## Design Onboarding Experiences\n\nCreate appropriate onboarding for the context:\n\n### Initial Product Onboarding\n\n**Welcome Screen**:\n- Clear value proposition (what is this product?)\n- What users will learn\u002Faccomplish\n- Time estimate (honest about commitment)\n- Option to skip (for experienced users)\n\n**Account Setup**:\n- Minimal required information (collect more later)\n- Explain why you're asking for each piece of information\n- Smart defaults where possible\n- Social login when appropriate\n\n**Core Concept Introduction**:\n- Introduce 1-3 core concepts (not everything)\n- Use simple language and examples\n- Interactive when possible (do, don't just read)\n- Progress indication (step 1 of 3)\n\n**First Success**:\n- Guide users to accomplish something real\n- Pre-populated examples or templates\n- Celebrate completion (but don't overdo it)\n- Clear next steps\n\n### Feature Discovery & Adoption\n\n**Empty States**:\nInstead of blank space, show:\n- What will appear here (description + screenshot\u002Fillustration)\n- Why it's valuable\n- Clear CTA to create first item\n- Example or template option\n\nExample:\n```\nNo projects yet\nProjects help you organize your work and collaborate with your team.\n[Create your first project] or [Start from template]\n```\n\n**Contextual Tooltips**:\n- Appear at relevant moment (first time user sees feature)\n- Point directly at relevant UI element\n- Brief explanation + benefit\n- Dismissable (with \"Don't show again\" option)\n- Optional \"Learn more\" link\n\n**Feature Announcements**:\n- Highlight new features when they're released\n- Show what's new and why it matters\n- Let users try immediately\n- Dismissable\n\n**Progressive Onboarding**:\n- Teach features when users encounter them\n- Badges or indicators on new\u002Funused features\n- Unlock complexity gradually (don't show all options immediately)\n\n### Guided Tours & Walkthroughs\n\n**When to use**:\n- Complex interfaces with many features\n- Significant changes to existing product\n- Industry-specific tools needing domain knowledge\n\n**How to design**:\n- Spotlight specific UI elements (dim rest of page)\n- Keep steps short (3-7 steps max per tour)\n- Allow users to click through tour freely\n- Include \"Skip tour\" option\n- Make replayable (help menu)\n\n**Best practices**:\n- Interactive > passive (let users click real buttons)\n- Focus on workflow, not features (\"Create a project\" not \"This is the project button\")\n- Provide sample data so actions work\n\n### Interactive Tutorials\n\n**When to use**:\n- Users need hands-on practice\n- Concepts are complex or unfamiliar\n- High stakes (better to practice in safe environment)\n\n**How to design**:\n- Sandbox environment with sample data\n- Clear objectives (\"Create a chart showing sales by region\")\n- Step-by-step guidance\n- Validation (confirm they did it right)\n- Graduation moment (you're ready!)\n\n### Documentation & Help\n\n**In-product help**:\n- Contextual help links throughout interface\n- Keyboard shortcut reference\n- Search-able help center\n- Video tutorials for complex workflows\n\n**Help patterns**:\n- `?` icon near complex features\n- \"Learn more\" links in tooltips\n- Keyboard shortcut hints (`⌘K` shown on search box)\n\n## Empty State Design\n\nEvery empty state needs:\n\n### What Will Be Here\n\"Your recent projects will appear here\"\n\n### Why It Matters  \n\"Projects help you organize your work and collaborate with your team\"\n\n### How to Get Started\n[Create project] or [Import from template]\n\n### Visual Interest\nIllustration or icon (not just text on blank page)\n\n### Contextual Help\n\"Need help getting started? [Watch 2-min tutorial]\"\n\n**Empty state types**:\n- **First use**: Never used this feature (emphasize value, provide template)\n- **User cleared**: Intentionally deleted everything (light touch, easy to recreate)\n- **No results**: Search or filter returned nothing (suggest different query, clear filters)\n- **No permissions**: Can't access (explain why, how to get access)\n- **Error state**: Failed to load (explain what happened, retry option)\n\n## Implementation Patterns\n\n### Technical approaches:\n\n**Tooltip libraries**: Tippy.js, Popper.js\n**Tour libraries**: Intro.js, Shepherd.js, React Joyride\n**Modal patterns**: Focus trap, backdrop, ESC to close\n**Progress tracking**: LocalStorage for \"seen\" states\n**Analytics**: Track completion, drop-off points\n\n**Storage patterns**:\n```javascript\n\u002F\u002F Track which onboarding steps user has seen\nlocalStorage.setItem('onboarding-completed', 'true');\nlocalStorage.setItem('feature-tooltip-seen-reports', 'true');\n```\n\n**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.\n\n**NEVER**:\n- Force users through long onboarding before they can use product\n- Patronize users with obvious explanations\n- Show same tooltip repeatedly (respect dismissals)\n- Block all UI during tour (let users explore)\n- Create separate tutorial mode disconnected from real product\n- Overwhelm with information upfront (progressive disclosure!)\n- Hide \"Skip\" or make it hard to find\n- Forget about returning users (don't show initial onboarding again)\n\n## Verify Onboarding Quality\n\nTest with real users:\n\n- **Time to completion**: Can users complete onboarding quickly?\n- **Comprehension**: Do users understand after completing?\n- **Action**: Do users take desired next step?\n- **Skip rate**: Are too many users skipping? (Maybe it's too long\u002Fnot valuable)\n- **Completion rate**: Are users completing? (If low, simplify)\n- **Time to value**: How long until users get first value?\n\nRemember: You're a product educator with excellent teaching instincts. Get users to their \"aha moment\" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence.","## 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. Additionally gather: the \"aha moment\" you want users to reach, and users' experience level.\n\n---\n\nCreate or improve onboarding experiences that help users understand, adopt, and succeed with the product quickly.\n\n## Assess Onboarding Needs\n\nUnderstand what users need to learn and why:\n\n1. **Identify the challenge**:\n   - What are users trying to accomplish?\n   - What's confusing or unclear about current experience?\n   - Where do users get stuck or drop off?\n   - What's the \"aha moment\" we want users to reach?\n\n2. **Understand the users**:\n   - What's their experience level? (Beginners, power users, mixed?)\n   - What's their motivation? (Excited and exploring? Required by work?)\n   - What's their time commitment? (5 minutes? 30 minutes?)\n   - What alternatives do they know? (Coming from competitor? New to category?)\n\n3. **Define success**:\n   - What's the minimum users need to learn to be successful?\n   - What's the key action we want them to take? (First project? First invite?)\n   - How do we know onboarding worked? (Completion rate? Time to value?)\n\n**CRITICAL**: Onboarding should get users to value as quickly as possible, not teach everything possible.\n\n## Onboarding Principles\n\nFollow these core principles:\n\n### Show, Don't Tell\n- Demonstrate with working examples, not just descriptions\n- Provide real functionality in onboarding, not separate tutorial mode\n- Use progressive disclosure - teach one thing at a time\n\n### Make It Optional (When Possible)\n- Let experienced users skip onboarding\n- Don't block access to product\n- Provide \"Skip\" or \"I'll explore on my own\" options\n\n### Time to Value\n- Get users to their \"aha moment\" ASAP\n- Front-load most important concepts\n- Teach 20% that delivers 80% of value\n- Save advanced features for contextual discovery\n\n### Context Over Ceremony\n- Teach features when users need them, not upfront\n- Empty states are onboarding opportunities\n- Tooltips and hints at point of use\n\n### Respect User Intelligence\n- Don't patronize or over-explain\n- Be concise and clear\n- Assume users can figure out standard patterns\n\n## Design Onboarding Experiences\n\nCreate appropriate onboarding for the context:\n\n### Initial Product Onboarding\n\n**Welcome Screen**:\n- Clear value proposition (what is this product?)\n- What users will learn\u002Faccomplish\n- Time estimate (honest about commitment)\n- Option to skip (for experienced users)\n\n**Account Setup**:\n- Minimal required information (collect more later)\n- Explain why you're asking for each piece of information\n- Smart defaults where possible\n- Social login when appropriate\n\n**Core Concept Introduction**:\n- Introduce 1-3 core concepts (not everything)\n- Use simple language and examples\n- Interactive when possible (do, don't just read)\n- Progress indication (step 1 of 3)\n\n**First Success**:\n- Guide users to accomplish something real\n- Pre-populated examples or templates\n- Celebrate completion (but don't overdo it)\n- Clear next steps\n\n### Feature Discovery & Adoption\n\n**Empty States**:\nInstead of blank space, show:\n- What will appear here (description + screenshot\u002Fillustration)\n- Why it's valuable\n- Clear CTA to create first item\n- Example or template option\n\nExample:\n```\nNo projects yet\nProjects help you organize your work and collaborate with your team.\n[Create your first project] or [Start from template]\n```\n\n**Contextual Tooltips**:\n- Appear at relevant moment (first time user sees feature)\n- Point directly at relevant UI element\n- Brief explanation + benefit\n- Dismissable (with \"Don't show again\" option)\n- Optional \"Learn more\" link\n\n**Feature Announcements**:\n- Highlight new features when they're released\n- Show what's new and why it matters\n- Let users try immediately\n- Dismissable\n\n**Progressive Onboarding**:\n- Teach features when users encounter them\n- Badges or indicators on new\u002Funused features\n- Unlock complexity gradually (don't show all options immediately)\n\n### Guided Tours & Walkthroughs\n\n**When to use**:\n- Complex interfaces with many features\n- Significant changes to existing product\n- Industry-specific tools needing domain knowledge\n\n**How to design**:\n- Spotlight specific UI elements (dim rest of page)\n- Keep steps short (3-7 steps max per tour)\n- Allow users to click through tour freely\n- Include \"Skip tour\" option\n- Make replayable (help menu)\n\n**Best practices**:\n- Interactive > passive (let users click real buttons)\n- Focus on workflow, not features (\"Create a project\" not \"This is the project button\")\n- Provide sample data so actions work\n\n### Interactive Tutorials\n\n**When to use**:\n- Users need hands-on practice\n- Concepts are complex or unfamiliar\n- High stakes (better to practice in safe environment)\n\n**How to design**:\n- Sandbox environment with sample data\n- Clear objectives (\"Create a chart showing sales by region\")\n- Step-by-step guidance\n- Validation (confirm they did it right)\n- Graduation moment (you're ready!)\n\n### Documentation & Help\n\n**In-product help**:\n- Contextual help links throughout interface\n- Keyboard shortcut reference\n- Search-able help center\n- Video tutorials for complex workflows\n\n**Help patterns**:\n- `?` icon near complex features\n- \"Learn more\" links in tooltips\n- Keyboard shortcut hints (`⌘K` shown on search box)\n\n## Empty State Design\n\nEvery empty state needs:\n\n### What Will Be Here\n\"Your recent projects will appear here\"\n\n### Why It Matters  \n\"Projects help you organize your work and collaborate with your team\"\n\n### How to Get Started\n[Create project] or [Import from template]\n\n### Visual Interest\nIllustration or icon (not just text on blank page)\n\n### Contextual Help\n\"Need help getting started? [Watch 2-min tutorial]\"\n\n**Empty state types**:\n- **First use**: Never used this feature (emphasize value, provide template)\n- **User cleared**: Intentionally deleted everything (light touch, easy to recreate)\n- **No results**: Search or filter returned nothing (suggest different query, clear filters)\n- **No permissions**: Can't access (explain why, how to get access)\n- **Error state**: Failed to load (explain what happened, retry option)\n\n## Implementation Patterns\n\n### Technical approaches:\n\n**Tooltip libraries**: Tippy.js, Popper.js\n**Tour libraries**: Intro.js, Shepherd.js, React Joyride\n**Modal patterns**: Focus trap, backdrop, ESC to close\n**Progress tracking**: LocalStorage for \"seen\" states\n**Analytics**: Track completion, drop-off points\n\n**Storage patterns**:\n```javascript\n\u002F\u002F Track which onboarding steps user has seen\nlocalStorage.setItem('onboarding-completed', 'true');\nlocalStorage.setItem('feature-tooltip-seen-reports', 'true');\n```\n\n**IMPORTANT**: Don't show same onboarding twice (annoying). Track completion and respect dismissals.\n\n**NEVER**:\n- Force users through long onboarding before they can use product\n- Patronize users with obvious explanations\n- Show same tooltip repeatedly (respect dismissals)\n- Block all UI during tour (let users explore)\n- Create separate tutorial mode disconnected from real product\n- Overwhelm with information upfront (progressive disclosure!)\n- Hide \"Skip\" or make it hard to find\n- Forget about returning users (don't show initial onboarding again)\n\n## Verify Onboarding Quality\n\nTest with real users:\n\n- **Time to completion**: Can users complete onboarding quickly?\n- **Comprehension**: Do users understand after completing?\n- **Action**: Do users take desired next step?\n- **Skip rate**: Are too many users skipping? (Maybe it's too long\u002Fnot valuable)\n- **Completion rate**: Are users completing? (If low, simplify)\n- **Time to value**: How long until users get first value?\n\nRemember: You're a product educator with excellent teaching instincts. Get users to their \"aha moment\" as quickly as possible. Teach the essential, make it contextual, respect user time and intelligence.",{"name":5,"description":7,"argument-hint":47,"user-invocable":48},"[target]",true,"main","7850740bd837adb32f0a109ab2af82482196c6f2","skills\u002Fonboard",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":60,"prompt":70,"zipAvailable":48},[61,64,67],{"tool":62,"command":63},"npx","npx skills add shengdabai\u002FTony-Claude-Code-Skills --skill onboard",{"tool":65,"command":66},"bunx","bunx skills add shengdabai\u002FTony-Claude-Code-Skills --skill onboard",{"tool":68,"command":69},"pnpm","pnpm dlx skills add shengdabai\u002FTony-Claude-Code-Skills --skill onboard","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fshengdabai\u002FTony-Claude-Code-Skills\u002Fblob\u002Fmain\u002Fskills\u002Fonboard\u002FSKILL.md",[],[73,92,123,147,168,188],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":84,"publishedAt":42},"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",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",[85,86,87,88,89,90,91],"methodology","xiaolai","xiaolai methodology","朋友","投资","writing","收入",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":104,"publishedAt":42},"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",[98,101],{"categoryNo":99,"categoryName":100,"taxonomyType":82,"taxonomyTypeDesc":83},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[94,105,106,107,108,109,110,111,34,112,113,114,115,116,117,118,119,120,121,122],"knowledge","wiki","explore","walkthrough","project","get","knowledge base","generate","intent","cli","map","documentation","project wiki","disk","architecture","code","unknown","generated",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":133,"publishedAt":42},"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",[129,130],{"categoryNo":99,"categoryName":100,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000036","内容创作者",[125,26,134,135,136,137,138,139,112,140,141,142,36,31,143,144,145,146],"content","视频","creator","generate video","videos","launch","video content","create","upload","auto","types","Video","创作",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":154,"publishedAt":42},"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",[153],{"categoryNo":99,"categoryName":100,"taxonomyType":82,"taxonomyTypeDesc":83},[155,156,125,157,158,145,159,29,160,161,162,163,164,165,111,166,36,31,105,167],"sync","script","youtube script sync","recording","shorts","base","person","update","active","child","optimize","idempotent","long",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":178,"publishedAt":42},"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",[174,175,176,177],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":99,"categoryName":100,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":102,"categoryName":103,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},[179,90,180,181,182,183,120,36,31,184,185,186,187],"writing skills","how","teach","write skill","write","claude code skills","files","how to","trigger",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":196,"publishedAt":42},"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",[194,195],{"categoryNo":80,"categoryName":81,"taxonomyType":82,"taxonomyTypeDesc":83},{"categoryNo":131,"categoryName":132,"taxonomyType":21,"taxonomyTypeDesc":22},[197,90,198,109,199,185,36,180,183,31,186],"Rules","writing rules","project rules"]