[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6JM30ECG6Z9DZ8B2AJEAC8J":3,"skill-same:01M6JM30ECG6Z9DZ8B2AJEAC8J":115},{"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":26,"publishedAt":37,"linkOnly":38,"markdownContent":39,"markdownBody":40,"frontMatter":41,"refName":42,"commitSha":43,"skillDirectory":44,"forksCount":45,"repositoryHtmlUrl":46,"repositoryHomepageUrl":47,"ownerHtmlUrl":48,"ownerBlogUrl":49,"ownerDescription":6,"updatedAt":50,"install":51,"resources":64},"01M6JM30ECG6Z9DZ8B2AJEAC8J","newsletter-creation-curation",null,"Industry-adaptive B2B newsletter creation with stage, role, and geography-aware workflows","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\u002Fnewsletter_creation_curation\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000005","邮件与沟通","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[27,28,29,30,31,32,33,34,35,36],"newsletter","newsletter creation curation","creation","curation","workflows","b2b","stage","with","industry","role","2026-11-10 10:12:30",false,"---\nname: newsletter-creation-curation\ndescription: Industry-adaptive B2B newsletter creation with stage, role, and geography-aware workflows\n---\n\n# Newsletter Creation & Curation Skill\n\nUse this skill to create B2B newsletters that match business context, not generic content templates.\n\nDeep strategic guidance is in `PLAYBOOK.md`.\nUse this file as the executable operating manual.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"Outline only, full edition, or full edition + calendar?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | Edition outline + 3 lead story angles, no writing | Planning, editorial direction |\n| `standard` | Full newsletter edition, all sections written | Publishing this week |\n| `deep` | Full edition + 4-week content calendar + audience segmentation recommendations | Launching or systematizing a newsletter |\n\n**Default: `standard`** — use `quick` if they're still deciding what to write. Use `deep` if they're building a newsletter from scratch or scaling.\n\n---\n\n## Context Loading Gates\n\n**Before generating any newsletter content, collect:**\n\n- [ ] **Company context:** What product\u002Fservice? Who is the ICP?\n- [ ] **Newsletter goal:** Lead gen \u002F thought leadership \u002F personal brand \u002F category ownership\n- [ ] **Industry vertical:** Sales Tech \u002F HR Tech \u002F Fintech \u002F Operations Tech\n- [ ] **Company stage:** Series A \u002F Series B \u002F Series C+\n- [ ] **Role:** Founder \u002F VP-Director \u002F PMM-Content \u002F Enterprise employee\n- [ ] **Geography:** US-first \u002F India-first\n- [ ] **Prior issues:** Any existing issues to maintain consistency and voice?\n- [ ] **Approval constraints:** Does this need legal\u002Fbrand\u002Fmanager review?\n\n**Structured intake — answer all 5 dimensions before proceeding:**\n\n```\nGoal: [lead_gen | thought_leadership | personal_brand | category_ownership]\nIndustry: [sales_tech | hr_tech | fintech | ops_tech]\nStage: [series_a | series_b | series_c_plus]\nRole: [founder | vp_director | pmm_content | enterprise_employee]\nGeography: [us_first | india_first]\n```\n\n---\n\n## Phase 1: Context Analysis\n\nBefore drafting, reason through:\n\n1. **Template match:** Which industry template best fits? (Sales Tech = data-heavy; HR Tech = research-led; Fintech = compliance-aware; Ops Tech = practical)\n2. **Cadence match:** Series A = weekly\u002Fbi-weekly for simplicity; Series B = weekly with process; Series C+ = media-grade weekly with pillars\n3. **Role constraints:** Founder = direct POV allowed; Employee = approval checkpoint required before final draft\n4. **Geography adjustments:** India-first = IST timing + local examples; US-first = EST\u002FPST + US benchmarks\n5. **Goal-content alignment:** Lead gen needs a clear conversion CTA; thought leadership needs original insight, not general content\n\nOutput one-line strategy statement:\n> `For [ICP], we publish [cadence] to achieve [goal] with [format].`\n\n---\n\n## Phase 2: Issue Blueprint\n\nBefore writing full draft, produce an issue blueprint:\n\n```markdown\n## Issue Blueprint\n\n**Strategy:** For [ICP], [cadence] to achieve [goal].\n**Industry tone:** [tactical\u002Fresearch-led\u002Fcompliance-aware\u002Fpractical]\n**Approval required:** [yes\u002Fno — who]\n\n**Sections:**\n1. Subject lines (3 options) — [~words each]\n2. Hook — [target ~75 words]\n3. Core insight — [target ~200 words]\n4. Actionable playbook — [target ~150 words, 3-5 steps]\n5. CTA — [1 sentence, singular action]\n```\n\nGet confirmation or proceed to draft.\n\n---\n\n## Phase 3: Full Issue Draft\n\nGenerate complete publish-ready draft. Required structure — every issue:\n\n### Subject Line Options (3 required)\nProduce 3 distinct angles:\n- A: Curiosity\u002Fopen loop (\"The metric most [ICP] ignore\")\n- B: Specific + benefit (\"How [Company type] achieves [X] in [timeframe]\")  \n- C: Contrarian\u002Fbold (\"Stop [common behavior]. Do this instead.\")\n\n### Hook\n- First 2 sentences must earn the read\n- Lead with the problem + stakes\n- Target: busy reader can extract the point in 60 seconds\n\n### Core Insight\n- One primary takeaway per issue — not three\n- Support with: data, framework, or named pattern\n- Include specific numbers or named examples wherever possible\n\n### Actionable Playbook\n- 3-5 steps or checklist items\n- Each step must be implementable, not just conceptual\n- Series A = simpler steps; Series C+ = more sophisticated process\n\n### CTA\n- ONE measurable action only\n- Options: reply with [X], click [link], share [asset], book [demo]\n- Never use vague CTAs (\"Learn more\")\n\n---\n\n## Phase 4: Refinement Checklist\n\nRun before delivering:\n\n- [ ] `Clarity`: Can a busy reader extract value in 60 seconds?\n- [ ] `Specificity`: Does each section include concrete guidance or evidence?\n- [ ] `Relevance`: Does tone match industry and role constraints?\n- [ ] `Compliance`: For fintech\u002Femployee-led, is a legal\u002Fmanager review step included?\n- [ ] `Consistency`: Does voice align with prior issues (if any were provided)?\n- [ ] `CTA`: Is there exactly ONE measurable CTA — not two, not zero?\n\n---\n\n## Phase 5: Self-Critique Pass (REQUIRED)\n\nAfter completing the draft, evaluate:\n\n- [ ] Does the subject line A option create genuine curiosity without being clickbait?\n- [ ] Does the hook deliver a problem + stakes in the first 2 sentences?\n- [ ] Is the core insight something subscribers couldn't get from a generic AI prompt?\n- [ ] Does the playbook have steps that are specific to this audience, not generic \"tips\"?\n- [ ] Is the CTA actually measurable — i.e., can they track whether it worked?\n- [ ] For fintech\u002Femployee contexts: is there an explicit approval checkpoint?\n\nFlag any issue: \"The playbook steps are too generic for a Series B SaaS audience — they read as beginner content. Revised to assume existing process maturity.\"\n\n---\n\n## Iteration Protocol\n\nAfter delivering the draft:\n1. Ask: \"Does the hook earn the read? Does the playbook feel actionable for your audience?\"\n2. If hook is weak → rewrite using a different angle (data-led, story-led, or contrarian)\n3. If playbook is too generic → ask for a specific example from their own experience to ground it\n4. For next issue: \"Want me to save these content themes so the next issue builds on this one?\"\n\n---\n\n## Output Structure\n\n```markdown\n## Newsletter Issue: [Name] — Issue #[X] — [Date]\n**Strategy:** For [ICP], [cadence] to achieve [goal].\n\n---\n\n### Subject Line Options\nA) [Curiosity\u002Fopen loop]\nB) [Specific + benefit]  \nC) [Contrarian\u002Fbold]\n**Recommended:** [A\u002FB\u002FC] — [reason]\n\n---\n\n### Hook\n[2-3 sentences — problem + stakes]\n\n---\n\n### Core Insight\n[200-300 words — data, framework, or named pattern]\n\n---\n\n### Actionable Playbook\n1. [Step]\n2. [Step]\n3. [Step]\n\n---\n\n### CTA\n[Single measurable action]\n\n---\n\n### Distribution Plan\n- **Send time:** [Day, Time, Timezone]\n- **LinkedIn amplification:** [Post angle \u002F hook]\n- **Secondary channel:** [Platform + angle]\n\n### KPI Targets\n- Open rate goal: [%]\n- CTR goal: [%]\n- Primary metric: [SQLs \u002F subscribers \u002F replies]\n\n### Approval Required\n[Yes — [who] | No]\n\n### Self-Critique Notes\n[Issues flagged + revisions made]\n```\n\n---\n\n## Playbook Map (Deep Dives in `PLAYBOOK.md`)\n\n- Sales Tech strategy: `SECTION A`\n- HR Tech strategy: `SECTION B`\n- Fintech strategy: `SECTION C`\n- Operations Tech strategy: `SECTION D`\n- Role approvals and geography tactics: `CROSS-CUTTING: UNIVERSAL FRAMEWORKS`\n\n---\n\n*Skill by Brian Wagner | AI Marketing Architect | brianrwagner.com*\n","# Newsletter Creation & Curation Skill\n\nUse this skill to create B2B newsletters that match business context, not generic content templates.\n\nDeep strategic guidance is in `PLAYBOOK.md`.\nUse this file as the executable operating manual.\n\n---\n\n## Mode\n\nDetect from context or ask: *\"Outline only, full edition, or full edition + calendar?\"*\n\n| Mode | What you get | Best for |\n|------|-------------|----------|\n| `quick` | Edition outline + 3 lead story angles, no writing | Planning, editorial direction |\n| `standard` | Full newsletter edition, all sections written | Publishing this week |\n| `deep` | Full edition + 4-week content calendar + audience segmentation recommendations | Launching or systematizing a newsletter |\n\n**Default: `standard`** — use `quick` if they're still deciding what to write. Use `deep` if they're building a newsletter from scratch or scaling.\n\n---\n\n## Context Loading Gates\n\n**Before generating any newsletter content, collect:**\n\n- [ ] **Company context:** What product\u002Fservice? Who is the ICP?\n- [ ] **Newsletter goal:** Lead gen \u002F thought leadership \u002F personal brand \u002F category ownership\n- [ ] **Industry vertical:** Sales Tech \u002F HR Tech \u002F Fintech \u002F Operations Tech\n- [ ] **Company stage:** Series A \u002F Series B \u002F Series C+\n- [ ] **Role:** Founder \u002F VP-Director \u002F PMM-Content \u002F Enterprise employee\n- [ ] **Geography:** US-first \u002F India-first\n- [ ] **Prior issues:** Any existing issues to maintain consistency and voice?\n- [ ] **Approval constraints:** Does this need legal\u002Fbrand\u002Fmanager review?\n\n**Structured intake — answer all 5 dimensions before proceeding:**\n\n```\nGoal: [lead_gen | thought_leadership | personal_brand | category_ownership]\nIndustry: [sales_tech | hr_tech | fintech | ops_tech]\nStage: [series_a | series_b | series_c_plus]\nRole: [founder | vp_director | pmm_content | enterprise_employee]\nGeography: [us_first | india_first]\n```\n\n---\n\n## Phase 1: Context Analysis\n\nBefore drafting, reason through:\n\n1. **Template match:** Which industry template best fits? (Sales Tech = data-heavy; HR Tech = research-led; Fintech = compliance-aware; Ops Tech = practical)\n2. **Cadence match:** Series A = weekly\u002Fbi-weekly for simplicity; Series B = weekly with process; Series C+ = media-grade weekly with pillars\n3. **Role constraints:** Founder = direct POV allowed; Employee = approval checkpoint required before final draft\n4. **Geography adjustments:** India-first = IST timing + local examples; US-first = EST\u002FPST + US benchmarks\n5. **Goal-content alignment:** Lead gen needs a clear conversion CTA; thought leadership needs original insight, not general content\n\nOutput one-line strategy statement:\n> `For [ICP], we publish [cadence] to achieve [goal] with [format].`\n\n---\n\n## Phase 2: Issue Blueprint\n\nBefore writing full draft, produce an issue blueprint:\n\n```markdown\n## Issue Blueprint\n\n**Strategy:** For [ICP], [cadence] to achieve [goal].\n**Industry tone:** [tactical\u002Fresearch-led\u002Fcompliance-aware\u002Fpractical]\n**Approval required:** [yes\u002Fno — who]\n\n**Sections:**\n1. Subject lines (3 options) — [~words each]\n2. Hook — [target ~75 words]\n3. Core insight — [target ~200 words]\n4. Actionable playbook — [target ~150 words, 3-5 steps]\n5. CTA — [1 sentence, singular action]\n```\n\nGet confirmation or proceed to draft.\n\n---\n\n## Phase 3: Full Issue Draft\n\nGenerate complete publish-ready draft. Required structure — every issue:\n\n### Subject Line Options (3 required)\nProduce 3 distinct angles:\n- A: Curiosity\u002Fopen loop (\"The metric most [ICP] ignore\")\n- B: Specific + benefit (\"How [Company type] achieves [X] in [timeframe]\")  \n- C: Contrarian\u002Fbold (\"Stop [common behavior]. Do this instead.\")\n\n### Hook\n- First 2 sentences must earn the read\n- Lead with the problem + stakes\n- Target: busy reader can extract the point in 60 seconds\n\n### Core Insight\n- One primary takeaway per issue — not three\n- Support with: data, framework, or named pattern\n- Include specific numbers or named examples wherever possible\n\n### Actionable Playbook\n- 3-5 steps or checklist items\n- Each step must be implementable, not just conceptual\n- Series A = simpler steps; Series C+ = more sophisticated process\n\n### CTA\n- ONE measurable action only\n- Options: reply with [X], click [link], share [asset], book [demo]\n- Never use vague CTAs (\"Learn more\")\n\n---\n\n## Phase 4: Refinement Checklist\n\nRun before delivering:\n\n- [ ] `Clarity`: Can a busy reader extract value in 60 seconds?\n- [ ] `Specificity`: Does each section include concrete guidance or evidence?\n- [ ] `Relevance`: Does tone match industry and role constraints?\n- [ ] `Compliance`: For fintech\u002Femployee-led, is a legal\u002Fmanager review step included?\n- [ ] `Consistency`: Does voice align with prior issues (if any were provided)?\n- [ ] `CTA`: Is there exactly ONE measurable CTA — not two, not zero?\n\n---\n\n## Phase 5: Self-Critique Pass (REQUIRED)\n\nAfter completing the draft, evaluate:\n\n- [ ] Does the subject line A option create genuine curiosity without being clickbait?\n- [ ] Does the hook deliver a problem + stakes in the first 2 sentences?\n- [ ] Is the core insight something subscribers couldn't get from a generic AI prompt?\n- [ ] Does the playbook have steps that are specific to this audience, not generic \"tips\"?\n- [ ] Is the CTA actually measurable — i.e., can they track whether it worked?\n- [ ] For fintech\u002Femployee contexts: is there an explicit approval checkpoint?\n\nFlag any issue: \"The playbook steps are too generic for a Series B SaaS audience — they read as beginner content. Revised to assume existing process maturity.\"\n\n---\n\n## Iteration Protocol\n\nAfter delivering the draft:\n1. Ask: \"Does the hook earn the read? Does the playbook feel actionable for your audience?\"\n2. If hook is weak → rewrite using a different angle (data-led, story-led, or contrarian)\n3. If playbook is too generic → ask for a specific example from their own experience to ground it\n4. For next issue: \"Want me to save these content themes so the next issue builds on this one?\"\n\n---\n\n## Output Structure\n\n```markdown\n## Newsletter Issue: [Name] — Issue #[X] — [Date]\n**Strategy:** For [ICP], [cadence] to achieve [goal].\n\n---\n\n### Subject Line Options\nA) [Curiosity\u002Fopen loop]\nB) [Specific + benefit]  \nC) [Contrarian\u002Fbold]\n**Recommended:** [A\u002FB\u002FC] — [reason]\n\n---\n\n### Hook\n[2-3 sentences — problem + stakes]\n\n---\n\n### Core Insight\n[200-300 words — data, framework, or named pattern]\n\n---\n\n### Actionable Playbook\n1. [Step]\n2. [Step]\n3. [Step]\n\n---\n\n### CTA\n[Single measurable action]\n\n---\n\n### Distribution Plan\n- **Send time:** [Day, Time, Timezone]\n- **LinkedIn amplification:** [Post angle \u002F hook]\n- **Secondary channel:** [Platform + angle]\n\n### KPI Targets\n- Open rate goal: [%]\n- CTR goal: [%]\n- Primary metric: [SQLs \u002F subscribers \u002F replies]\n\n### Approval Required\n[Yes — [who] | No]\n\n### Self-Critique Notes\n[Issues flagged + revisions made]\n```\n\n---\n\n## Playbook Map (Deep Dives in `PLAYBOOK.md`)\n\n- Sales Tech strategy: `SECTION A`\n- HR Tech strategy: `SECTION B`\n- Fintech strategy: `SECTION C`\n- Operations Tech strategy: `SECTION D`\n- Role approvals and geography tactics: `CROSS-CUTTING: UNIVERSAL FRAMEWORKS`\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\u002Fnewsletter_creation_curation",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":52,"prompt":62,"zipAvailable":63},[53,56,59],{"tool":54,"command":55},"npx","npx skills add LongLeo287\u002FOmniClaw --skill newsletter-creation-curation",{"tool":57,"command":58},"bunx","bunx skills add LongLeo287\u002FOmniClaw --skill newsletter-creation-curation",{"tool":60,"command":61},"pnpm","pnpm dlx skills add LongLeo287\u002FOmniClaw --skill newsletter-creation-curation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002FSKILL.md",true,[65,71,75,79,83,87,91,95,99,103,107,111],{"path":66,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":69,"sourceHtmlUrl":70},"_DIR_IDENTITY.md","REFERENCE","参考文档",443,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002F_DIR_IDENTITY.md",{"path":72,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":73,"sourceHtmlUrl":74},"examples\u002F_DIR_IDENTITY.md",401,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Fexamples\u002F_DIR_IDENTITY.md",{"path":76,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":77,"sourceHtmlUrl":78},"examples\u002Fexample_hr_tech_issue.md",2899,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Fexamples\u002Fexample_hr_tech_issue.md",{"path":80,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":81,"sourceHtmlUrl":82},"examples\u002Fexample_sales_tech_issue.md",2796,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Fexamples\u002Fexample_sales_tech_issue.md",{"path":84,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":85,"sourceHtmlUrl":86},"playbook.md",55225,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Fplaybook.md",{"path":88,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":89,"sourceHtmlUrl":90},"README.md",2242,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002FREADME.md",{"path":92,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":93,"sourceHtmlUrl":94},"skill_oc.md",3159,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Fskill_oc.md",{"path":96,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":97,"sourceHtmlUrl":98},"templates\u002F_DIR_IDENTITY.md",406,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Ftemplates\u002F_DIR_IDENTITY.md",{"path":100,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":101,"sourceHtmlUrl":102},"templates\u002Ffintech_template.md",1512,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Ftemplates\u002Ffintech_template.md",{"path":104,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":105,"sourceHtmlUrl":106},"templates\u002Fhr_tech_template.md",1484,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Ftemplates\u002Fhr_tech_template.md",{"path":108,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":109,"sourceHtmlUrl":110},"templates\u002Fops_tech_template.md",1463,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Ftemplates\u002Fops_tech_template.md",{"path":112,"resourceType":67,"resourceTypeDesc":68,"sizeBytes":113,"sourceHtmlUrl":114},"templates\u002Fsales_tech_template.md",1397,"https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fai_marketing_claude_code_skills\u002Fnewsletter_creation_curation\u002Ftemplates\u002Fsales_tech_template.md",[116,155,176,204,220,247],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":120,"categories":121,"keywords":134,"publishedAt":37},"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",[122,125,126,131],{"categoryNo":123,"categoryName":124,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000032","设计师","PROFESSION","适用职业",{"categoryNo":132,"categoryName":133,"taxonomyType":129,"taxonomyTypeDesc":130},"01JBSEEDCAT000000000000033","数据分析师",[135,136,137,138,139,140,141,142,143,144,145,146,147,148,149,150,151,152,153,154],"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":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":162,"publishedAt":37},"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",[161],{"categoryNo":127,"categoryName":128,"taxonomyType":129,"taxonomyTypeDesc":130},[163,136,164,165,142,166,167,168,169,145,170,171,172,148,173,174,34,175],"shadcn","shadcn ui","components","core","best practices","applications","discovery","customization","guidance","expert","installation","ui components","for",{"skillNo":177,"name":178,"nameZh":6,"description":179,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":180,"categories":181,"keywords":185,"publishedAt":37},"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",[182],{"categoryNo":183,"categoryName":184,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",[186,187,188,189,190,191,192,193,194,195,196,197,198,199,200,201,34,202,203],"zustand store ts","zustand","store","typescript","microsoft","react","create","state management","state","react state management","management","global","use","patterns","separation","middleware","action","implementing",{"skillNo":205,"name":187,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":209,"publishedAt":37},"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",[],[187,210,193,211,194,212,213,196,214,198,215,216,217,188,34,218,219,202,203],"development","code","actions","src","guide","implementation","zustand state","triggers","questions","zustand state management",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":230,"publishedAt":37},"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",[226,229],{"categoryNo":227,"categoryName":228,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[231,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246],"youtube","youtube summarizer","summarizer","generate","metadata","messaging","Video","fetch","telegram","transcription","summarization","structured","full","insights","transcripts","summaries",{"skillNo":248,"name":249,"nameZh":6,"description":250,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":251,"categories":252,"keywords":253,"publishedAt":37},"01M6JQZN3QJB6B77JGKJD62DQT","youtube_clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FLongLeo287\u002FOmniClaw\u002Fblob\u002Fmain\u002Fecosystem\u002Fskills\u002Fyoutube_clipper\u002FSKILL.md",[],[231,254,255,237,256,257,258,259,260,261,262,263,264,265,266,267,268],"clipper","youtube clipper","Bash","下载","视频","生成","关键词","翻译","read","write","clip","总结","工具","文案","sonnet"]