[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JNGM63XZVB6YP6CEPFAHFE":3,"skill-same:01M6JNGM63XZVB6YP6CEPFAHFE":109},{"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":52,"commitSha":53,"skillDirectory":54,"forksCount":55,"repositoryHtmlUrl":56,"repositoryHomepageUrl":57,"ownerHtmlUrl":58,"ownerBlogUrl":59,"ownerDescription":6,"updatedAt":60,"install":61,"resources":74},"01M6JNGM63XZVB6YP6CEPFAHFE","cold_email",null,"Write B2B cold emails and follow-up sequences that earn replies. Use when creating outbound prospecting emails, SDR outreach, personalized opening lines, subject lines, CTAs, and multi-touch follow-up sequences.","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\u002Fcold_email\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"cold email","email","cold","unknown","github","earn","follow-up","replies","multi","touch","outreach","emails","b2b","outbound","up","use","write","prospecting","https","2026-11-10 10:12:30",false,"---\nname: cold_email\n\ndescription: \"Write B2B cold emails and follow-up sequences that earn replies. Use when creating outbound prospecting emails, SDR outreach, personalized opening lines, subject lines, CTAs, and multi-touch follow-up sequences.\"\nrisk: unknown\nsource: \"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills\"\ndate_added: \"2026-03-21\"\nmetadata:\n  version: 1.1.0\n---\n\n# Cold Email Writing\n\nYou are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.\n\n## When to Use\n\n- Use when writing outbound prospecting emails or cold follow-up sequences.\n- Use when the task is getting replies from people with no existing relationship.\n- Use when the user wants sharper subject lines, openings, CTAs, or personalization.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing-context.md` exists (or `.claude\u002Fproduct-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nUnderstand the situation (ask if not provided):\n\n1. **Who are you writing to?** — Role, company, why them specifically\n2. **What do you want?** — The outcome (meeting, reply, intro, demo)\n3. **What's the value?** — The specific problem you solve for people like them\n4. **What's your proof?** — A result, case study, or credibility signal\n5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes\n\nWork with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.\n\n---\n\n## Writing Principles\n\n### Write like a peer, not a vendor\n\nThe email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.\n\n### Every sentence must earn its place\n\nCold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.\n\n### Personalization must connect to the problem\n\nIf you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.\n\nSee [personalization.md](references\u002Fpersonalization.md) for the 4-level system and research signals.\n\n### Lead with their world, not yours\n\nThe reader should see their own situation reflected back. \"You\u002Fyour\" should dominate over \"I\u002Fwe.\" Don't open with who you are or what your company does.\n\n### One ask, low friction\n\nInterest-based CTAs (\"Worth exploring?\" \u002F \"Would this be useful?\") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.\n\n---\n\n## Voice & Tone\n\n**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.\n\n**Calibrate to the audience:**\n\n- C-suite: ultra-brief, peer-level, understated\n- Mid-level: more specific value, slightly more detail\n- Technical: precise, no fluff, respect their intelligence\n\n**What it should NOT sound like:**\n\n- A template with fields swapped in\n- A pitch deck compressed into paragraph form\n- A LinkedIn DM from someone you've never met\n- An AI-generated email (avoid the telltale patterns: \"I hope this email finds you well,\" \"I came across your profile,\" \"leverage,\" \"synergy,\" \"best-in-class\")\n\n---\n\n## Structure\n\nThere's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.\n\n**Common shapes that work:**\n\n- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?\n- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?\n- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?\n- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?\n\nFor the full catalog of frameworks with examples, see [frameworks.md](references\u002Fframeworks.md).\n\n---\n\n## Subject Lines\n\nShort, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.\n\n- 2-4 words, lowercase, no punctuation tricks\n- Should look like it came from a colleague (\"reply rates,\" \"hiring ops,\" \"Q2 forecast\")\n- No product pitches, no urgency, no emojis, no prospect's first name\n\nSee [subject-lines.md](references\u002Fsubject-lines.md) for the full data.\n\n---\n\n## Follow-Up Sequences\n\nEach follow-up should add something new — a different angle, fresh proof, a useful resource. \"Just checking in\" gives the reader no reason to respond.\n\n- 3-5 total emails, increasing gaps between them\n- Each email should stand alone (they may not have read the previous ones)\n- The breakup email is your last touch — honor it\n\nSee [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) for cadence, angle rotation, and breakup email templates.\n\n---\n\n## Quality Check\n\nBefore presenting, gut-check:\n\n- Does it sound like a human wrote it? (Read it aloud)\n- Would YOU reply to this if you received it?\n- Does every sentence serve the reader, not the sender?\n- Is the personalization connected to the problem?\n- Is there one clear, low-friction ask?\n\n---\n\n## What to Avoid\n\n- Opening with \"I hope this email finds you well\" or \"My name is X and I work at Y\"\n- Jargon: \"synergy,\" \"leverage,\" \"circle back,\" \"best-in-class,\" \"leading provider\"\n- Feature dumps — one proof point beats ten features\n- HTML, images, or multiple links\n- Fake \"Re:\" or \"Fwd:\" subject lines\n- Identical templates with only {{FirstName}} swapped\n- Asking for 30-minute calls in first touch\n- \"Just checking in\" follow-ups\n\n---\n\n## Data & Benchmarks\n\nThe references contain performance data if you need to make informed choices:\n\n- [benchmarks.md](references\u002Fbenchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes\n- [personalization.md](references\u002Fpersonalization.md) — 4-level personalization system, research signals\n- [subject-lines.md](references\u002Fsubject-lines.md) — Subject line data and optimization\n- [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) — Cadence, angles, breakup emails\n- [frameworks.md](references\u002Fframeworks.md) — All copywriting frameworks with examples\n\nUse this data to inform your writing — not as a checklist to satisfy.\n\n---\n\n## Related Skills\n\n- **copywriting**: For landing pages and web copy\n- **email-sequence**: For lifecycle\u002Fnurture email sequences (not cold outreach)\n- **social-content**: For LinkedIn and social posts\n- **product-marketing-context**: For establishing foundational positioning\n- **revops**: For lead scoring, routing, and pipeline management\n","# Cold Email Writing\n\nYou are an expert cold email writer. Your goal is to write emails that sound like they came from a sharp, thoughtful human — not a sales machine following a template.\n\n## When to Use\n\n- Use when writing outbound prospecting emails or cold follow-up sequences.\n- Use when the task is getting replies from people with no existing relationship.\n- Use when the user wants sharper subject lines, openings, CTAs, or personalization.\n\n## Before Writing\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing-context.md` exists (or `.claude\u002Fproduct-marketing-context.md` in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nUnderstand the situation (ask if not provided):\n\n1. **Who are you writing to?** — Role, company, why them specifically\n2. **What do you want?** — The outcome (meeting, reply, intro, demo)\n3. **What's the value?** — The specific problem you solve for people like them\n4. **What's your proof?** — A result, case study, or credibility signal\n5. **Any research signals?** — Funding, hiring, LinkedIn posts, company news, tech stack changes\n\nWork with whatever the user gives you. If they have a strong signal and a clear value prop, that's enough to write. Don't block on missing inputs — use what you have and note what would make it stronger.\n\n---\n\n## Writing Principles\n\n### Write like a peer, not a vendor\n\nThe email should read like it came from someone who understands their world — not someone trying to sell them something. Use contractions. Read it aloud. If it sounds like marketing copy, rewrite it.\n\n### Every sentence must earn its place\n\nCold email is ruthlessly short. If a sentence doesn't move the reader toward replying, cut it. The best cold emails feel like they could have been shorter, not longer.\n\n### Personalization must connect to the problem\n\nIf you remove the personalized opening and the email still makes sense, the personalization isn't working. The observation should naturally lead into why you're reaching out.\n\nSee [personalization.md](references\u002Fpersonalization.md) for the 4-level system and research signals.\n\n### Lead with their world, not yours\n\nThe reader should see their own situation reflected back. \"You\u002Fyour\" should dominate over \"I\u002Fwe.\" Don't open with who you are or what your company does.\n\n### One ask, low friction\n\nInterest-based CTAs (\"Worth exploring?\" \u002F \"Would this be useful?\") beat meeting requests. One CTA per email. Make it easy to say yes with a one-line reply.\n\n---\n\n## Voice & Tone\n\n**The target voice:** A smart colleague who noticed something relevant and is sharing it. Conversational but not sloppy. Confident but not pushy.\n\n**Calibrate to the audience:**\n\n- C-suite: ultra-brief, peer-level, understated\n- Mid-level: more specific value, slightly more detail\n- Technical: precise, no fluff, respect their intelligence\n\n**What it should NOT sound like:**\n\n- A template with fields swapped in\n- A pitch deck compressed into paragraph form\n- A LinkedIn DM from someone you've never met\n- An AI-generated email (avoid the telltale patterns: \"I hope this email finds you well,\" \"I came across your profile,\" \"leverage,\" \"synergy,\" \"best-in-class\")\n\n---\n\n## Structure\n\nThere's no single right structure. Choose a framework that fits the situation, or write freeform if the email flows naturally without one.\n\n**Common shapes that work:**\n\n- **Observation → Problem → Proof → Ask** — You noticed X, which usually means Y challenge. We helped Z with that. Interested?\n- **Question → Value → Ask** — Struggling with X? We do Y. Company Z saw [result]. Worth a look?\n- **Trigger → Insight → Ask** — Congrats on X. That usually creates Y challenge. We've helped similar companies with that. Curious?\n- **Story → Bridge → Ask** — [Similar company] had [problem]. They [solved it this way]. Relevant to you?\n\nFor the full catalog of frameworks with examples, see [frameworks.md](references\u002Fframeworks.md).\n\n---\n\n## Subject Lines\n\nShort, boring, internal-looking. The subject line's only job is to get the email opened — not to sell.\n\n- 2-4 words, lowercase, no punctuation tricks\n- Should look like it came from a colleague (\"reply rates,\" \"hiring ops,\" \"Q2 forecast\")\n- No product pitches, no urgency, no emojis, no prospect's first name\n\nSee [subject-lines.md](references\u002Fsubject-lines.md) for the full data.\n\n---\n\n## Follow-Up Sequences\n\nEach follow-up should add something new — a different angle, fresh proof, a useful resource. \"Just checking in\" gives the reader no reason to respond.\n\n- 3-5 total emails, increasing gaps between them\n- Each email should stand alone (they may not have read the previous ones)\n- The breakup email is your last touch — honor it\n\nSee [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) for cadence, angle rotation, and breakup email templates.\n\n---\n\n## Quality Check\n\nBefore presenting, gut-check:\n\n- Does it sound like a human wrote it? (Read it aloud)\n- Would YOU reply to this if you received it?\n- Does every sentence serve the reader, not the sender?\n- Is the personalization connected to the problem?\n- Is there one clear, low-friction ask?\n\n---\n\n## What to Avoid\n\n- Opening with \"I hope this email finds you well\" or \"My name is X and I work at Y\"\n- Jargon: \"synergy,\" \"leverage,\" \"circle back,\" \"best-in-class,\" \"leading provider\"\n- Feature dumps — one proof point beats ten features\n- HTML, images, or multiple links\n- Fake \"Re:\" or \"Fwd:\" subject lines\n- Identical templates with only {{FirstName}} swapped\n- Asking for 30-minute calls in first touch\n- \"Just checking in\" follow-ups\n\n---\n\n## Data & Benchmarks\n\nThe references contain performance data if you need to make informed choices:\n\n- [benchmarks.md](references\u002Fbenchmarks.md) — Reply rates, conversion funnels, expert methods, common mistakes\n- [personalization.md](references\u002Fpersonalization.md) — 4-level personalization system, research signals\n- [subject-lines.md](references\u002Fsubject-lines.md) — Subject line data and optimization\n- [follow-up-sequences.md](references\u002Ffollow-up-sequences.md) — Cadence, angles, breakup emails\n- [frameworks.md](references\u002Fframeworks.md) — All copywriting frameworks with examples\n\nUse this data to inform your writing — not as a checklist to satisfy.\n\n---\n\n## Related Skills\n\n- **copywriting**: For landing pages and web copy\n- **email-sequence**: For lifecycle\u002Fnurture email sequences (not cold outreach)\n- **social-content**: For LinkedIn and social posts\n- **product-marketing-context**: For establishing foundational positioning\n- **revops**: For lead scoring, routing, and pipeline management\n",{"name":5,"risk":27,"source":48,"metadata":49,"date_added":51,"description":7},"https:\u002F\u002Fgithub.com\u002Fcoreyhaines31\u002Fmarketingskills",{"version":50},"1.1.0","2026-03-21","main","c173cdffe08e788a99b91928a831b476b8434838","ecosystem\u002Fskills\u002Fcold_email",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":62,"prompt":72,"zipAvailable":73},[63,66,69],{"tool":64,"command":65},"npx","npx skills add LongLeo287\u002FOmniClaw --skill cold_email",{"tool":67,"command":68},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill cold_email",{"tool":70,"command":71},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill cold_email","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002FSKILL.md",true,[75,81,85,89,93,97,101,105],{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"_DIR_IDENTITY.md","REFERENCE","参考文档",142,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002F_DIR_IDENTITY.md",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"README.md",455,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002FREADME.md",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"references\u002Fbenchmarks.md",5817,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Freferences\u002Fbenchmarks.md",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"references\u002Ffollow_up_sequences.md",3875,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Freferences\u002Ffollow_up_sequences.md",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"references\u002Fframeworks.md",5403,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Freferences\u002Fframeworks.md",{"path":98,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":99,"sourceHtmlUrl":100},"references\u002Fpersonalization.md",4437,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Freferences\u002Fpersonalization.md",{"path":102,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":103,"sourceHtmlUrl":104},"references\u002Fsubject_lines.md",3015,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Freferences\u002Fsubject_lines.md",{"path":106,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":107,"sourceHtmlUrl":108},"schema.json",432,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fcold_email\u002Fschema.json",[110,151,173,200,216,243],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":130,"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",[116,119,122,127],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":128,"categoryName":129,"taxonomyType":125,"taxonomyTypeDesc":126},"01JBSEEDCAT000000000000033","数据分析师",[131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150],"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":152,"name":153,"nameZh":6,"description":154,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":155,"categories":156,"keywords":158,"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",[157],{"categoryNo":123,"categoryName":124,"taxonomyType":125,"taxonomyTypeDesc":126},[159,132,160,161,138,162,163,164,165,141,166,167,168,144,169,170,171,172],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","with","for",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":182,"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",[179],{"categoryNo":180,"categoryName":181,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[183,184,185,186,187,188,189,190,191,192,193,194,39,195,196,197,171,198,199],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","patterns","separation","middleware","action","implementing",{"skillNo":201,"name":184,"nameZh":6,"description":202,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":203,"categories":204,"keywords":205,"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",[],[184,206,190,207,191,208,209,193,210,39,211,212,213,185,171,214,215,198,199],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":217,"name":218,"nameZh":6,"description":219,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":220,"categories":221,"keywords":226,"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",[222,225],{"categoryNo":223,"categoryName":224,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":120,"categoryName":121,"taxonomyType":21,"taxonomyTypeDesc":22},[227,228,229,230,231,232,233,234,235,236,237,238,239,240,241,242],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":244,"name":245,"nameZh":6,"description":246,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":247,"categories":248,"keywords":249,"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",[],[227,250,251,233,252,253,254,255,256,257,258,40,259,260,261,262,263],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","clip","总结","工具","文案","sonnet"]