[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JM183W3R4S4GMSVRYRSA71":3,"skill-same:01M6JM183W3R4S4GMSVRYRSA71":81},{"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":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":53,"ownerHtmlUrl":54,"ownerBlogUrl":55,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6JM183W3R4S4GMSVRYRSA71","cold-outreach-sequence",null,"Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.","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\u002Fai_marketing_claude_code_skills\u002Fcold_outreach_sequence\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"outreach","sequence","cold outreach sequence","cold","cold outreach","up","conversion","build","use","research","systematic","linkedin","engine","connection","leads","follow-ups","requests","for","email","2026-11-10 10:12:30",false,"---\nname: cold-outreach-sequence\ndescription: Build personalized cold outreach sequences for LinkedIn and email. Use when someone needs to reach prospects, warm up cold leads, or build a systematic outreach engine. Covers research, connection requests, follow-ups, and conversion.\n---\n\n# Cold Outreach Sequence\n\nHere's what I've learned about cold outreach: the word \"cold\" is the problem.\n\nSpray-and-pray templates don't work. 10 minutes of research + a specific reference = not cold anymore. This skill builds the second kind.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"One message, full sequence, or full outreach system?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | 1 connection request + 1 follow-up for a single prospect | Testing an angle, one-off outreach |\n| `standard` | Full 4-touch sequence for a single prospect | Active pipeline, individual targets |\n| `deep` | Multi-prospect sequence system + A\u002FB variants + tracking framework | Launching an outreach campaign |\n\n**Default: `standard`** — use `quick` if they give you one name and say \"draft something.\" Use `deep` if they're building a repeatable outreach engine.\n\n---\n\n## Context Loading Gates\n\n**Before writing any message, collect:**\n\n- [ ] **Prospect name and company** — full name, company, role\u002Ftitle\n- [ ] **Research signals** — run tool calls first (see below); do not write without them\n- [ ] **Sender positioning** — what does the sender do, for whom, with what result? (Use `positioning-basics` output if available)\n- [ ] **Platform** — LinkedIn DM, email, or both?\n- [ ] **Batch size** — how many prospects? (determines tier assignment)\n\n**Research tool calls — run before writing:**\n\n```\nweb_search('[Company] [Founder\u002FName] news 2026')\nweb_search('[Company] funding recent')\nweb_search('[Person name] [Company] LinkedIn')\n```\n\n**Personalization constraint:** Do not write a Tier 1 message without a named specific signal from research. If search yields 0 signals, default to Tier 3 and say so explicitly.\n\n---\n\n## Phase 1: Research & Signal Assessment\n\nFor each prospect, document findings before drafting:\n\n**Signal types (ranked by message strength):**\n1. Recent news event (funding, launch, hire, press) → strongest signal\n2. Recent LinkedIn post activity → strong signal\n3. Company stage\u002Fgrowth data → medium signal\n4. Role + industry awareness only → weak signal (Tier 3)\n\n**Personalization tier assignment:**\n\n| Research Result | Tier | Approach |\n|---|---|---|\n| Named signal (news + post + context) | Tier 1 | Fully custom, reference signal in every message |\n| Company info + role context | Tier 2 | Template + personalized opener |\n| No signals found | Tier 3 | Volume template, minimal customization |\n\n---\n\n## Phase 2: Sequence Generation\n\n### Connection Request (LinkedIn) — 300 chars max\n\n**Formula:** `[Specific observation from research] + [Simple reason to connect]`\n\n**Rules:**\n- No pitching\n- Prove you did research (name the signal)\n- One sentence, conversational\n- Never \"I'd love to pick your brain\"\n\n**By signal type:**\n```\nRecent funding: \"Congrats on the Series A — the [investor] backing is a smart signal. Would love to connect.\"\n\nRecent post: \"Your post on [specific topic] resonated — been thinking the same thing. Happy to connect.\"\n\nNews\u002Flaunch: \"Saw the [product] launch — [specific detail] is smart positioning. Would love to connect.\"\n```\n\n---\n\n### First Message (After Accept — Wait 24-48 Hours)\n\n**Formula:** `[Thanks] + [Bridge to relevance] + [Light value] + [Soft question]`\n\n**Template:**\n```\nThanks for connecting. I work with [ICP description] on [specific outcome].\n\nCurious — is [relevant function] something you own directly at [Company], \nor is that still founder-led?\n\nHappy to share what I'm seeing work at similar-stage companies either way.\n```\n\n---\n\n### Follow-Up #1 (Day 7)\n\n**Formula:** `[Light nudge] + [New signal or angle] + [Easy out]`\n\n**Constraint:** Do NOT write \"following up\" with nothing new. Add one new piece:\n- A relevant article or trend\n- A related insight you recently had\n- A connection to something they posted\n\n**Template:**\n```\nBumping this up — came across [specific article\u002Ftrend\u002Finsight] and \nthought of your situation at [Company].\n\n[One sentence on why it's relevant to them.]\n\nHappy to share more if useful. If not, no worries.\n```\n\n---\n\n### Follow-Up #2 (Day 14)\n\nShift to email if LinkedIn hasn't converted, or try a different angle.\n\n**Subject line options:**\n- \"[Company]'s [function] as you scale\"\n- \"Saw your [post\u002Fnews] — quick thought\"\n- \"Question about [specific thing they're doing]\"\n\n**Email structure:**\n```\n[1-line hook tied to their specific situation]\n\n[2-3 sentences: why you're reaching out + one proof point]\n\n[Soft CTA — 1 sentence]\n```\n\n---\n\n### Break-Up Message (Day 21)\n\n```\nI'll assume timing isn't right — totally get it. \n\nIf [relevant pain point] becomes a priority down the road, happy to reconnect. \nBest of luck with [specific thing they're working on based on research].\n```\n\n**Post-break-up action:** Add to 6-month re-engagement list with a resurface date.\n\n---\n\n## Phase 3: Self-Critique Pass (REQUIRED)\n\nAfter generating the full sequence, evaluate:\n\n- [ ] Does every message reference the specific signal from research, or are they generic?\n- [ ] Is the connection request under 300 characters?\n- [ ] Does the first message ask a question (invite dialogue) rather than pitch?\n- [ ] Does follow-up #1 add something genuinely new, or is it just \"following up\"?\n- [ ] Does the break-up message reference something specific about their situation?\n- [ ] Did I correctly assign the personalization tier, or am I over-personalizing a Tier 3 prospect?\n\nFlag any issue: \"The first message doesn't include a soft question — it reads as a pitch. Revised to invite dialogue.\"\n\n---\n\n## Pipeline Tracking Table\n\nAlways output a tracking table for the batch:\n\n```markdown\n| Prospect | Company | Platform | Tier | Sent Date | Response | Stage | Next Action | Resurface Date |\n|---|---|---|---|---|---|---|---|---|\n| [Name] | [Co] | LinkedIn | 1 | [date] | — | Connection sent | Wait 24-48h | — |\n| [Name] | [Co] | Email | 2 | [date] | — | First email sent | Follow-up Day 7 | — |\n```\n\n---\n\n## Iteration Protocol\n\nAfter each response (or non-response), ask:\n- Did the connection request get accepted? If low acceptance rate → revise the observation line\n- Did the first message get a reply? If no → was the question soft enough, or did it feel like a pitch?\n- Did follow-ups get ignored? If yes → try a different angle or acknowledge the silence directly\n\n---\n\n## Output Structure\n\n```markdown\n## Outreach Sequence: [Prospect Name] — [Date]\n\n### Research Summary\n- Signal type: [news \u002F post \u002F company info \u002F none]\n- Signal found: \"[Specific detail]\"\n- Personalization tier: [1\u002F2\u002F3]\n- Source: [URL or platform]\n\n### Sequence\n\n**Connection Request (LinkedIn):**\n[Text — max 300 chars]\n\n**First Message (Day 1-2 after accept):**\n[Text]\n\n**Follow-Up #1 (Day 7):**\n[Text]\n\n**Follow-Up #2 (Day 14):**\nPlatform: [LinkedIn \u002F Email]\nSubject: [if email]\n[Text]\n\n**Break-Up (Day 21):**\n[Text]\n\n### Pipeline Entry\n| Prospect | Company | Platform | Tier | Stage | Next Action | Resurface Date |\n|---|---|---|---|---|---|---|\n| [Name] | [Co] | [Platform] | [Tier] | Connection sent | Wait 24-48h | — |\n\n### Self-Critique Notes\n[Any issues flagged + revisions made]\n```\n\n---\n\n*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*\n","# Cold Outreach Sequence\n\nHere's what I've learned about cold outreach: the word \"cold\" is the problem.\n\nSpray-and-pray templates don't work. 10 minutes of research + a specific reference = not cold anymore. This skill builds the second kind.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"One message, full sequence, or full outreach system?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | 1 connection request + 1 follow-up for a single prospect | Testing an angle, one-off outreach |\n| `standard` | Full 4-touch sequence for a single prospect | Active pipeline, individual targets |\n| `deep` | Multi-prospect sequence system + A\u002FB variants + tracking framework | Launching an outreach campaign |\n\n**Default: `standard`** — use `quick` if they give you one name and say \"draft something.\" Use `deep` if they're building a repeatable outreach engine.\n\n---\n\n## Context Loading Gates\n\n**Before writing any message, collect:**\n\n- [ ] **Prospect name and company** — full name, company, role\u002Ftitle\n- [ ] **Research signals** — run tool calls first (see below); do not write without them\n- [ ] **Sender positioning** — what does the sender do, for whom, with what result? (Use `positioning-basics` output if available)\n- [ ] **Platform** — LinkedIn DM, email, or both?\n- [ ] **Batch size** — how many prospects? (determines tier assignment)\n\n**Research tool calls — run before writing:**\n\n```\nweb_search('[Company] [Founder\u002FName] news 2026')\nweb_search('[Company] funding recent')\nweb_search('[Person name] [Company] LinkedIn')\n```\n\n**Personalization constraint:** Do not write a Tier 1 message without a named specific signal from research. If search yields 0 signals, default to Tier 3 and say so explicitly.\n\n---\n\n## Phase 1: Research & Signal Assessment\n\nFor each prospect, document findings before drafting:\n\n**Signal types (ranked by message strength):**\n1. Recent news event (funding, launch, hire, press) → strongest signal\n2. Recent LinkedIn post activity → strong signal\n3. Company stage\u002Fgrowth data → medium signal\n4. Role + industry awareness only → weak signal (Tier 3)\n\n**Personalization tier assignment:**\n\n| Research Result | Tier | Approach |\n|---|---|---|\n| Named signal (news + post + context) | Tier 1 | Fully custom, reference signal in every message |\n| Company info + role context | Tier 2 | Template + personalized opener |\n| No signals found | Tier 3 | Volume template, minimal customization |\n\n---\n\n## Phase 2: Sequence Generation\n\n### Connection Request (LinkedIn) — 300 chars max\n\n**Formula:** `[Specific observation from research] + [Simple reason to connect]`\n\n**Rules:**\n- No pitching\n- Prove you did research (name the signal)\n- One sentence, conversational\n- Never \"I'd love to pick your brain\"\n\n**By signal type:**\n```\nRecent funding: \"Congrats on the Series A — the [investor] backing is a smart signal. Would love to connect.\"\n\nRecent post: \"Your post on [specific topic] resonated — been thinking the same thing. Happy to connect.\"\n\nNews\u002Flaunch: \"Saw the [product] launch — [specific detail] is smart positioning. Would love to connect.\"\n```\n\n---\n\n### First Message (After Accept — Wait 24-48 Hours)\n\n**Formula:** `[Thanks] + [Bridge to relevance] + [Light value] + [Soft question]`\n\n**Template:**\n```\nThanks for connecting. I work with [ICP description] on [specific outcome].\n\nCurious — is [relevant function] something you own directly at [Company], \nor is that still founder-led?\n\nHappy to share what I'm seeing work at similar-stage companies either way.\n```\n\n---\n\n### Follow-Up #1 (Day 7)\n\n**Formula:** `[Light nudge] + [New signal or angle] + [Easy out]`\n\n**Constraint:** Do NOT write \"following up\" with nothing new. Add one new piece:\n- A relevant article or trend\n- A related insight you recently had\n- A connection to something they posted\n\n**Template:**\n```\nBumping this up — came across [specific article\u002Ftrend\u002Finsight] and \nthought of your situation at [Company].\n\n[One sentence on why it's relevant to them.]\n\nHappy to share more if useful. If not, no worries.\n```\n\n---\n\n### Follow-Up #2 (Day 14)\n\nShift to email if LinkedIn hasn't converted, or try a different angle.\n\n**Subject line options:**\n- \"[Company]'s [function] as you scale\"\n- \"Saw your [post\u002Fnews] — quick thought\"\n- \"Question about [specific thing they're doing]\"\n\n**Email structure:**\n```\n[1-line hook tied to their specific situation]\n\n[2-3 sentences: why you're reaching out + one proof point]\n\n[Soft CTA — 1 sentence]\n```\n\n---\n\n### Break-Up Message (Day 21)\n\n```\nI'll assume timing isn't right — totally get it. \n\nIf [relevant pain point] becomes a priority down the road, happy to reconnect. \nBest of luck with [specific thing they're working on based on research].\n```\n\n**Post-break-up action:** Add to 6-month re-engagement list with a resurface date.\n\n---\n\n## Phase 3: Self-Critique Pass (REQUIRED)\n\nAfter generating the full sequence, evaluate:\n\n- [ ] Does every message reference the specific signal from research, or are they generic?\n- [ ] Is the connection request under 300 characters?\n- [ ] Does the first message ask a question (invite dialogue) rather than pitch?\n- [ ] Does follow-up #1 add something genuinely new, or is it just \"following up\"?\n- [ ] Does the break-up message reference something specific about their situation?\n- [ ] Did I correctly assign the personalization tier, or am I over-personalizing a Tier 3 prospect?\n\nFlag any issue: \"The first message doesn't include a soft question — it reads as a pitch. Revised to invite dialogue.\"\n\n---\n\n## Pipeline Tracking Table\n\nAlways output a tracking table for the batch:\n\n```markdown\n| Prospect | Company | Platform | Tier | Sent Date | Response | Stage | Next Action | Resurface Date |\n|---|---|---|---|---|---|---|---|---|\n| [Name] | [Co] | LinkedIn | 1 | [date] | — | Connection sent | Wait 24-48h | — |\n| [Name] | [Co] | Email | 2 | [date] | — | First email sent | Follow-up Day 7 | — |\n```\n\n---\n\n## Iteration Protocol\n\nAfter each response (or non-response), ask:\n- Did the connection request get accepted? If low acceptance rate → revise the observation line\n- Did the first message get a reply? If no → was the question soft enough, or did it feel like a pitch?\n- Did follow-ups get ignored? If yes → try a different angle or acknowledge the silence directly\n\n---\n\n## Output Structure\n\n```markdown\n## Outreach Sequence: [Prospect Name] — [Date]\n\n### Research Summary\n- Signal type: [news \u002F post \u002F company info \u002F none]\n- Signal found: \"[Specific detail]\"\n- Personalization tier: [1\u002F2\u002F3]\n- Source: [URL or platform]\n\n### Sequence\n\n**Connection Request (LinkedIn):**\n[Text — max 300 chars]\n\n**First Message (Day 1-2 after accept):**\n[Text]\n\n**Follow-Up #1 (Day 7):**\n[Text]\n\n**Follow-Up #2 (Day 14):**\nPlatform: [LinkedIn \u002F Email]\nSubject: [if email]\n[Text]\n\n**Break-Up (Day 21):**\n[Text]\n\n### Pipeline Entry\n| Prospect | Company | Platform | Tier | Stage | Next Action | Resurface Date |\n|---|---|---|---|---|---|---|\n| [Name] | [Co] | [Platform] | [Tier] | Connection sent | Wait 24-48h | — |\n\n### Self-Critique Notes\n[Any issues flagged + revisions made]\n```\n\n---\n\n*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*\n",{"name":5,"description":7},"main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fcold_outreach_sequence",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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add LongLeo287\u002FOmniClaw --skill cold-outreach-sequence",{"tool":63,"command":64},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill cold-outreach-sequence",{"tool":66,"command":67},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill cold-outreach-sequence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fcold_outreach_sequence\u002FSKILL.md",true,[71,77],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"_DIR_IDENTITY.md","REFERENCE","参考文档",413,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fcold_outreach_sequence\u002F_DIR_IDENTITY.md",{"path":78,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":79,"sourceHtmlUrl":80},"skill_oc.md",2869,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fcold_outreach_sequence\u002Fskill_oc.md",[82,122,143,170,186,213],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":102,"publishedAt":43},"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",[88,91,94,99],{"categoryNo":89,"categoryName":90,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":100,"categoryName":101,"taxonomyType":97,"taxonomyTypeDesc":98},"01JBSEEDCAT000000000000033","数据分析师",[103,104,105,106,107,108,109,110,111,112,113,114,115,116,34,117,118,119,120,121],"ux","ui","ui ux pro max","max","pro","ui ux","design","component","search","analysis","team","rd","ui-ux","active","scripts","pattern extraction","sources","advanced","data-driven",{"skillNo":123,"name":124,"nameZh":6,"description":125,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":126,"categories":127,"keywords":129,"publishedAt":43},"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",[128],{"categoryNo":95,"categoryName":96,"taxonomyType":97,"taxonomyTypeDesc":98},[130,104,131,132,110,133,134,135,136,113,137,138,139,116,140,141,142,41],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":152,"publishedAt":43},"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",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[153,154,155,156,157,158,159,160,161,162,163,164,32,165,166,167,142,168,169],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","patterns","separation","middleware","action","implementing",{"skillNo":171,"name":154,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":43},"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",[],[154,176,160,177,161,178,179,163,180,32,181,182,183,155,142,184,185,168,169],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"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":196,"publishedAt":43},"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",[192,195],{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":92,"categoryName":93,"taxonomyType":21,"taxonomyTypeDesc":22},[197,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":214,"name":215,"nameZh":6,"description":216,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":217,"categories":218,"keywords":219,"publishedAt":43},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[197,220,221,203,222,223,224,225,226,227,228,229,230,231,232,233,234],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]