[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JPDZAX2J3RKN73VEHMF770":3,"skill-same:01M6JPDZAX2J3RKN73VEHMF770":84},{"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":18,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":43,"commitSha":44,"skillDirectory":45,"forksCount":46,"repositoryHtmlUrl":47,"repositoryHomepageUrl":48,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6JPDZAX2J3RKN73VEHMF770","linkedin_authority_builder",null,"Build a LinkedIn content system for thought leadership. Use when someone needs to establish authority, attract inbound leads, or build a consistent content presence. Covers positioning, content pillars, formats, and posting rhythm.","LongLeo287\u002FOmniClaw","LongLeo287","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F141803367?v=4","01M6JK75C62VCNZKR5BRZ386YV","LongLeo","01M6JK75GQ78TSP1ZPXNKK3MCH",9,"MIT","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"authority","linkedin","builder","linkedin authority builder","positioning","for","presence","formats","leads","content pillars","posting","leadership","linkedin content system","thought leadership","build","use","linkedin content","system","content","2026-11-10 10:12:30",false,"---\nname: linkedin_authority_builder\n\ndescription: Build a LinkedIn content system for thought leadership. Use when someone needs to establish authority, attract inbound leads, or build a consistent content presence. Covers positioning, content pillars, formats, and posting rhythm.\n---\n\n# LinkedIn Authority Builder\n\nHere's what most people get wrong about LinkedIn: they're trying to go viral.\n\nViral doesn't pay your bills. Being remembered by the right 500 people when they need what you do — that pays your bills.\n\nThis skill builds a content system around consistent positioning and clear pillars — not hacks.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"Starter plan, full content system, or 90-day build?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | 3 content pillars + 1-week posting starter plan | Getting unstuck, first week of consistency |\n| `standard` | Full content system: pillars, formats, posting rhythm + first week written | Building a repeatable presence |\n| `deep` | Full system + 90-day calendar + 10 posts written + engagement playbook | Serious authority-building campaign |\n\n**Default: `standard`** — use `quick` if they just need to start posting. Use `deep` if they're committing to LinkedIn as a growth channel.\n\n---\n\n## Context Loading Gates\n\n**Before generating any strategy, load:**\n\n- [ ] **Current positioning:** One-liner, ICP, key differentiator (load from `positioning-basics` output if available)\n- [ ] **Target audience on LinkedIn:** Specific titles, company stages, industries\n- [ ] **Posting history:** What have they tried? What worked? What didn't?\n- [ ] **Content goals:** Leads \u002F job offers \u002F speaking \u002F partnerships \u002F audience growth\n- [ ] **Available time per week:** Hours they can realistically commit\n\n**Sequencing gate:**\nIf positioning isn't clear yet, stop and ask:\n> \"Before building a content strategy, I need your one-liner: 'I help [specific audience] with [specific outcome] through [unique approach].' Do you have this locked, or should we nail positioning first with `positioning-basics`?\"\n\nDo not build a content system for an unclear position — the content will be unfocused.\n\n**Also suggest:**\n> \"Run `linkedin-profile-optimizer` if you haven't — the content we build needs a profile that converts the traffic.\"\n\n---\n\n## Phase 1: Positioning Alignment Analysis\n\nBefore recommending any content, reason through:\n\n1. **Positioning check:** Is the one-liner specific enough to anchor content pillars? If it's \"I help businesses grow,\" that's too vague — push for specificity before proceeding.\n2. **Audience clarity:** Are we targeting a specific title + company stage, or a demographic? Specific is better.\n3. **Time-to-output match:** If they have 2 hours\u002Fweek, don't recommend 5 posts\u002Fweek. Sustainability matters more than ambition.\n4. **Goal alignment:** Content for lead generation looks different from content for speaking gigs. Confirm goal before building pillars.\n\nOutput a brief strategy assessment:\n> \"You're a [role] targeting [audience] with [X hours\u002Fweek] and a goal of [outcome]. I'll build a [3\u002F5 post\u002Fweek] strategy anchored to [X] pillars. The main gap in your current approach: [specific gap].\"\n\n---\n\n## Phase 2: Content Pillars (3–5 Required)\n\nEach pillar must pass all 4 tests:\n1. You have genuine expertise (not just interest)\n2. Your target audience actively cares about it\n3. You can produce content on it consistently for 6+ months\n4. It connects to what you sell or want to be known for\n\n**Pillar ratio:**\n- 70% core expertise → builds authority\n- 20% adjacent insights → makes you interesting\n- 10% personal → makes you relatable\n\n**Output format per pillar:**\n```\nPillar: [Name]\nRatio: [%]\nContent types: [frameworks \u002F stories \u002F case studies]\nExample hook: \"[First line of a real post]\"\nConnection to goal: [how this drives the stated outcome]\n```\n\n---\n\n## Phase 3: Format Selection & Post Templates\n\n### Format-to-Goal Mapping\n\n| Format | Best For | Engagement Level |\n|---|---|---|\n| Story | Connection, memorability | High |\n| Framework\u002FList | Authority, credibility | High |\n| Hot take | Reach, visibility | Variable |\n| Case study\u002Fproof | Credibility, late-stage trust | Medium |\n| Behind-the-scenes | Relatability, trust | Medium |\n\n**Recommended weekly mix:**\n- 2–3 frameworks (authority)\n- 1–2 stories (connection)\n- 1 proof point (credibility)\n\n### Post Templates\n\n**Story Post:**\n```\n[Hook — the moment or realization]\n[Setup — quick context]\n[Tension — what was hard or went wrong]\n[Turn — the insight]\n[Lesson — the takeaway]\n[Question — drives engagement]\n```\n\n**Framework Post:**\n```\n[Hook — bold claim or problem statement]\n[Why this matters — 1-2 sentences]\n[The X-step framework:]\n1. [Step + brief explanation]\n2. [Step + brief explanation]\n3. [Step + brief explanation]\n[Key insight or summary]\n[CTA or discussion question]\n```\n\n**Hot Take:**\n```\n[Controversial statement]\n[Your reasoning — 2-3 sentences]\n[The nuance people miss]\n[What to do instead]\n[Question to drive comments]\n```\n\n---\n\n## Phase 4: Content Calendar with Real Dates\n\nGenerate a 4-week calendar with actual dates (not generic day names):\n\n| Date | Pillar | Format | Hook (first line) | Status |\n|---|---|---|---|---|\n| [YYYY-MM-DD] | [Pillar] | Framework | \"[First line]\" | Draft |\n| [YYYY-MM-DD] | [Pillar] | Story | \"[First line]\" | Draft |\n\nFill 4 full weeks. Generic \"Week 1, Monday\" output is not sufficient.\n\nAlso output **5 starter post hooks** ready to write immediately — these break the blank-page problem:\n```\n1. [Hook]\n2. [Hook]\n3. [Hook]\n4. [Hook]\n5. [Hook]\n```\n\n---\n\n## Phase 5: Self-Critique Pass (REQUIRED)\n\nAfter generating the strategy, evaluate:\n\n- [ ] Is the positioning one-liner specific enough to anchor the pillars?\n- [ ] Are the 5 starter hooks actually strong — would they stop the scroll?\n- [ ] Does the time commitment match the user's stated available hours?\n- [ ] Is at least one pillar directly tied to the revenue\u002Fgoal outcome?\n- [ ] Does the calendar have actual dates, or just generic \"Day 1\u002FDay 3\" placeholders?\n- [ ] Would this content system still work in 6 months if the user stays consistent?\n\nFlag issues: \"Pillar 3 ('general business tips') doesn't connect to your stated goal of attracting SaaS founders. Replace with something more specific.\"\n\n---\n\n## Phase 6: 30-Day Iteration Protocol\n\nAfter 30 days, review with these questions:\n- Which posts got the most comments? What pillar did they fall under?\n- Which posts drove DMs or profile views?\n- Which posts got the most impressions regardless of engagement?\n\n**Adjust based on data:**\n- If case study posts outperform frameworks → increase case study ratio\n- If stories drive DMs but frameworks drive impressions → use both intentionally\n\n---\n\n## Output Structure\n\n```markdown\n## LinkedIn Strategy: [Name] — [Date]\n\n### Positioning Alignment\n[One-liner + assessment of clarity]\n\n### Content Pillars\n[3-5 pillars with ratio, examples, connection to goal]\n\n### Weekly Rhythm\n- Posts\u002Fweek: [X]\n- Best times: [e.g., Tue\u002FThu 8am EST]\n- Active commenting: [X min\u002Fday]\n\n### Format Mix\n[Breakdown with rationale]\n\n### 4-Week Content Calendar\n[Table with real dates + hooks]\n\n### 5 Starter Posts (Write These First)\n[Hooks with format labels]\n\n### Engagement Plan\n[Who to engage with, how much time, what to say]\n\n### Self-Critique Notes\n[Issues flagged + recommended fixes]\n\n### 30-Day Review Triggers\n[What to measure and when to adjust]\n\n### Cross-References\n- linkedin-profile-optimizer (run before publishing)\n- content-idea-generator (for ongoing idea generation)\n- voice-extractor (to ensure posts sound authentic)\n```\n\n---\n\n*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*\n","# LinkedIn Authority Builder\n\nHere's what most people get wrong about LinkedIn: they're trying to go viral.\n\nViral doesn't pay your bills. Being remembered by the right 500 people when they need what you do — that pays your bills.\n\nThis skill builds a content system around consistent positioning and clear pillars — not hacks.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"Starter plan, full content system, or 90-day build?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | 3 content pillars + 1-week posting starter plan | Getting unstuck, first week of consistency |\n| `standard` | Full content system: pillars, formats, posting rhythm + first week written | Building a repeatable presence |\n| `deep` | Full system + 90-day calendar + 10 posts written + engagement playbook | Serious authority-building campaign |\n\n**Default: `standard`** — use `quick` if they just need to start posting. Use `deep` if they're committing to LinkedIn as a growth channel.\n\n---\n\n## Context Loading Gates\n\n**Before generating any strategy, load:**\n\n- [ ] **Current positioning:** One-liner, ICP, key differentiator (load from `positioning-basics` output if available)\n- [ ] **Target audience on LinkedIn:** Specific titles, company stages, industries\n- [ ] **Posting history:** What have they tried? What worked? What didn't?\n- [ ] **Content goals:** Leads \u002F job offers \u002F speaking \u002F partnerships \u002F audience growth\n- [ ] **Available time per week:** Hours they can realistically commit\n\n**Sequencing gate:**\nIf positioning isn't clear yet, stop and ask:\n> \"Before building a content strategy, I need your one-liner: 'I help [specific audience] with [specific outcome] through [unique approach].' Do you have this locked, or should we nail positioning first with `positioning-basics`?\"\n\nDo not build a content system for an unclear position — the content will be unfocused.\n\n**Also suggest:**\n> \"Run `linkedin-profile-optimizer` if you haven't — the content we build needs a profile that converts the traffic.\"\n\n---\n\n## Phase 1: Positioning Alignment Analysis\n\nBefore recommending any content, reason through:\n\n1. **Positioning check:** Is the one-liner specific enough to anchor content pillars? If it's \"I help businesses grow,\" that's too vague — push for specificity before proceeding.\n2. **Audience clarity:** Are we targeting a specific title + company stage, or a demographic? Specific is better.\n3. **Time-to-output match:** If they have 2 hours\u002Fweek, don't recommend 5 posts\u002Fweek. Sustainability matters more than ambition.\n4. **Goal alignment:** Content for lead generation looks different from content for speaking gigs. Confirm goal before building pillars.\n\nOutput a brief strategy assessment:\n> \"You're a [role] targeting [audience] with [X hours\u002Fweek] and a goal of [outcome]. I'll build a [3\u002F5 post\u002Fweek] strategy anchored to [X] pillars. The main gap in your current approach: [specific gap].\"\n\n---\n\n## Phase 2: Content Pillars (3–5 Required)\n\nEach pillar must pass all 4 tests:\n1. You have genuine expertise (not just interest)\n2. Your target audience actively cares about it\n3. You can produce content on it consistently for 6+ months\n4. It connects to what you sell or want to be known for\n\n**Pillar ratio:**\n- 70% core expertise → builds authority\n- 20% adjacent insights → makes you interesting\n- 10% personal → makes you relatable\n\n**Output format per pillar:**\n```\nPillar: [Name]\nRatio: [%]\nContent types: [frameworks \u002F stories \u002F case studies]\nExample hook: \"[First line of a real post]\"\nConnection to goal: [how this drives the stated outcome]\n```\n\n---\n\n## Phase 3: Format Selection & Post Templates\n\n### Format-to-Goal Mapping\n\n| Format | Best For | Engagement Level |\n|---|---|---|\n| Story | Connection, memorability | High |\n| Framework\u002FList | Authority, credibility | High |\n| Hot take | Reach, visibility | Variable |\n| Case study\u002Fproof | Credibility, late-stage trust | Medium |\n| Behind-the-scenes | Relatability, trust | Medium |\n\n**Recommended weekly mix:**\n- 2–3 frameworks (authority)\n- 1–2 stories (connection)\n- 1 proof point (credibility)\n\n### Post Templates\n\n**Story Post:**\n```\n[Hook — the moment or realization]\n[Setup — quick context]\n[Tension — what was hard or went wrong]\n[Turn — the insight]\n[Lesson — the takeaway]\n[Question — drives engagement]\n```\n\n**Framework Post:**\n```\n[Hook — bold claim or problem statement]\n[Why this matters — 1-2 sentences]\n[The X-step framework:]\n1. [Step + brief explanation]\n2. [Step + brief explanation]\n3. [Step + brief explanation]\n[Key insight or summary]\n[CTA or discussion question]\n```\n\n**Hot Take:**\n```\n[Controversial statement]\n[Your reasoning — 2-3 sentences]\n[The nuance people miss]\n[What to do instead]\n[Question to drive comments]\n```\n\n---\n\n## Phase 4: Content Calendar with Real Dates\n\nGenerate a 4-week calendar with actual dates (not generic day names):\n\n| Date | Pillar | Format | Hook (first line) | Status |\n|---|---|---|---|---|\n| [YYYY-MM-DD] | [Pillar] | Framework | \"[First line]\" | Draft |\n| [YYYY-MM-DD] | [Pillar] | Story | \"[First line]\" | Draft |\n\nFill 4 full weeks. Generic \"Week 1, Monday\" output is not sufficient.\n\nAlso output **5 starter post hooks** ready to write immediately — these break the blank-page problem:\n```\n1. [Hook]\n2. [Hook]\n3. [Hook]\n4. [Hook]\n5. [Hook]\n```\n\n---\n\n## Phase 5: Self-Critique Pass (REQUIRED)\n\nAfter generating the strategy, evaluate:\n\n- [ ] Is the positioning one-liner specific enough to anchor the pillars?\n- [ ] Are the 5 starter hooks actually strong — would they stop the scroll?\n- [ ] Does the time commitment match the user's stated available hours?\n- [ ] Is at least one pillar directly tied to the revenue\u002Fgoal outcome?\n- [ ] Does the calendar have actual dates, or just generic \"Day 1\u002FDay 3\" placeholders?\n- [ ] Would this content system still work in 6 months if the user stays consistent?\n\nFlag issues: \"Pillar 3 ('general business tips') doesn't connect to your stated goal of attracting SaaS founders. Replace with something more specific.\"\n\n---\n\n## Phase 6: 30-Day Iteration Protocol\n\nAfter 30 days, review with these questions:\n- Which posts got the most comments? What pillar did they fall under?\n- Which posts drove DMs or profile views?\n- Which posts got the most impressions regardless of engagement?\n\n**Adjust based on data:**\n- If case study posts outperform frameworks → increase case study ratio\n- If stories drive DMs but frameworks drive impressions → use both intentionally\n\n---\n\n## Output Structure\n\n```markdown\n## LinkedIn Strategy: [Name] — [Date]\n\n### Positioning Alignment\n[One-liner + assessment of clarity]\n\n### Content Pillars\n[3-5 pillars with ratio, examples, connection to goal]\n\n### Weekly Rhythm\n- Posts\u002Fweek: [X]\n- Best times: [e.g., Tue\u002FThu 8am EST]\n- Active commenting: [X min\u002Fday]\n\n### Format Mix\n[Breakdown with rationale]\n\n### 4-Week Content Calendar\n[Table with real dates + hooks]\n\n### 5 Starter Posts (Write These First)\n[Hooks with format labels]\n\n### Engagement Plan\n[Who to engage with, how much time, what to say]\n\n### Self-Critique Notes\n[Issues flagged + recommended fixes]\n\n### 30-Day Review Triggers\n[What to measure and when to adjust]\n\n### Cross-References\n- linkedin-profile-optimizer (run before publishing)\n- content-idea-generator (for ongoing idea generation)\n- voice-extractor (to ensure posts sound authentic)\n```\n\n---\n\n*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*\n",{"name":5,"description":7},"main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Flinkedin_authority_builder",0,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw","https:\u002F\u002Fportfolio-longleo.vercel.app\u002Flabs\u002Fomniclaw.html","https:\u002F\u002Fgithub.com\u002FLongLeo287","https:\u002F\u002Fwww.facebook.com\u002FResourceRookie2023","2026-09-30 00:58:05",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add LongLeo287\u002FOmniClaw --skill linkedin_authority_builder",{"tool":58,"command":59},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill linkedin_authority_builder",{"tool":61,"command":62},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill linkedin_authority_builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002FSKILL.md",true,[66,72,76,80],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"_DIR_IDENTITY.md","REFERENCE","参考文档",435,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002F_DIR_IDENTITY.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"README.md",487,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002FREADME.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"schema.json",480,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002Fschema.json",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"skill_oc.md",2804,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Flinkedin_authority_builder\u002Fskill_oc.md",[85,128,149,176,192,219],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":107,"publishedAt":38},"01M6JR0KQP4MHT32TN40D9CBFX","UI-UX Pro Max","Advanced UI\u002FUX analysis and generation skills with data-driven patterns. Python scripts (core.py, search.py) for systematic UI pattern extraction, design system generation, and component search from curated data sources.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fui_ux_pro_max\u002FSKILL.md",[91,96,99,104],{"categoryNo":92,"categoryName":93,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000015","视觉设计","SCENARIO","使用场景",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":105,"categoryName":106,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000033","数据分析师",[108,109,110,111,112,113,114,115,116,117,118,119,120,121,122,123,124,125,126,127],"ux","ui","ui ux pro max","max","pro","ui ux","design","component","search","analysis","team","rd","ui-ux","active","systematic","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":135,"publishedAt":38},"01M6JR0EF5AEQHP2FSTB57H05P","shadcn-ui","Expert guidance for integrating and building applications with shadcn\u002Fui components, including component discovery, installation, customization, and best practices.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fui_components\u002Fshadcn_ui\u002FSKILL.md",[134],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},[136,109,137,138,115,139,140,141,142,118,143,144,145,121,146,147,148,24],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":158,"publishedAt":38},"01M6JR08F51BEN17RHFYX65WVE","zustand_store_ts","Create Zustand stores with TypeScript, subscribeWithSelector middleware, and proper state\u002Faction separation. Use when building React state management, creating global stores, or implementing reactive state patterns with Zustand.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand_store_ts\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000009","前端开发",[159,160,161,162,163,164,165,166,167,168,169,170,34,171,172,173,148,174,175],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","patterns","separation","middleware","action","implementing",{"skillNo":177,"name":160,"nameZh":6,"description":178,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":179,"categories":180,"keywords":181,"publishedAt":38},"01M6JR00TDMVAFFCZXZ04AN7Q7","Zustand state management guide. Use when working with store code (src\u002Fstore\u002F**), implementing actions, managing state, or creating slices. Triggers on Zustand store development, state management questions, or action implementation.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fzustand\u002FSKILL.md",[],[160,182,166,183,167,184,185,169,186,34,187,188,189,161,148,190,191,174,175],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":202,"publishedAt":38},"01M6JQZSWV4KWJP112G6XHEP44","youtube_summarizer","Automatically fetch YouTube video transcripts, generate structured summaries, and send full transcripts to messaging platforms. Detects YouTube URLs and provides metadata, key insights, and downloadable transcripts.","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_summarizer\u002FSKILL.md",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":94,"taxonomyTypeDesc":95},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":97,"categoryName":98,"taxonomyType":94,"taxonomyTypeDesc":95},[203,204,205,206,207,208,209,210,211,212,213,214,215,216,217,218],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":220,"name":221,"nameZh":6,"description":222,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":223,"categories":224,"keywords":225,"publishedAt":38},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[203,226,227,209,228,229,230,231,232,233,234,235,236,237,238,239,240],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]