[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B2P9FBVXHT90D9DS623BHC":3,"skill-same:01M7B2P9FBVXHT90D9DS623BHC":50},{"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":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7B2P9FBVXHT90D9DS623BHC","marketing-campaign",null,"End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.","lytong760-cell\u002Fcompiler_ko","lytong760-cell","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F289977458?v=4","01M7B1YD239K88PFQRD4PVC9DW","Nguyên Games","01M7B1YD2RM70TZ71QNQ0XTN4R",2,"MIT","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fmarketing-campaign\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: marketing-campaign\ndescription: End-to-end marketing campaign planning and execution. Covers audience research, positioning, campaign angle definition, landing page copy, email sequences, social posts, ad copy, short-form video scripts, and content calendars. Use as the orchestration layer for multi-channel product launches. Use when planning or executing a multi-channel product launch, or producing landing page, email, social, or ad copy.\nmetadata:\n  origin: ECC\n---\n\n# Marketing Campaign\n\nPlan and execute launch campaigns that convert — not just campaigns that ship.\n\n## When to Activate\n\n- planning a product or feature launch\n- building a full content suite from a single product brief\n- defining positioning and campaign angle before writing any copy\n- orchestrating multiple content types across channels\n- reviewing copy for conversion quality and brand consistency\n\n## Non-Negotiables\n\n1. Define positioning before writing any copy. All copy flows from the angle.\n2. Research the audience before assuming you know their language or fears.\n3. Each deliverable must serve one clear purpose in the campaign arc.\n4. Specificity beats adjectives in every format and on every channel.\n5. The same voice must run across every channel and every piece.\n6. No copy ships without passing the quality gate.\n\n## Campaign Workflow\n\n### Phase 1: Research\n\nUse `market-research` to:\n- profile the target audience (jobs-to-be-done, fears, language, alternatives they use)\n- map 3+ direct or adjacent competitors (positioning, gaps, messaging weaknesses)\n- identify 1–3 audience insights the campaign angle will exploit\n\nDeliverable: a short research brief (audience profile + competitive summary + key insights).\n\n### Phase 2: Positioning\n\nProduce:\n- core benefit statement (one sentence, no feature list, no jargon)\n- positioning formula: \"[Product] helps [audience] [achieve outcome] by [mechanism]\"\n- campaign angle: the specific tension, insight, or moment the whole campaign lives in\n- tone profile: lock before writing (delegate to `brand-voice` for durable, session-reusable voice capture)\n\nDo not write any copy until positioning and angle are approved.\n\n### Phase 3: Content Production\n\nProduce in this order — each layer informs the next:\n\n1. **Landing page copy** (all sections: hero, problem, solution, features, how it works, proof, CTA)\n2. **Email sequence** (each email has one purpose; follow the arc: problem → education → agitation → solution → proof → urgency → final CTA)\n3. **Social posts** (platform-native via `content-engine`; LinkedIn and X are different formats, not the same copy resized)\n4. **Short-form video scripts** (timestamp-blocked; written for screen and ear, not the page)\n5. **Ad copy variants** (3–4 variants testing different angles or audience segments)\n6. **Content calendar** (day-by-day schedule with channel, type, timing, and dependencies)\n\n### Phase 4: Review\n\nGate every deliverable:\n- 5-second test on all hero \u002F above-fold copy (clear who it's for, what it does, why act now)\n- CTA audit (one per piece, specific, earned — not demanded)\n- Tone consistency check across all channels\n- Claim audit (every claim is specific and supportable)\n- Cross-channel consistency (ad claims match landing page; email body matches subject)\n\n## Output Contract\n\nA full campaign delivers:\n\n1. **Positioning brief** — angle, core benefit statement, tone profile\n2. **Landing page copy** — hero, problem, solution, features, how it works, proof, CTA\n3. **Email sequence** — subject + preview + body + CTA for each email, labelled by day and purpose\n4. **LinkedIn posts** — 3+ platform-native posts with distinct angles\n5. **X posts** — 5+ standalone posts + 1 thread\n6. **Short-form video scripts** — 2+ timestamp-blocked scripts with visual direction notes\n7. **Ad copy variants** — short headline \u002F long headline \u002F body per variant\n8. **Content calendar** — day-by-day schedule with channel, content type, timing, and dependencies\n9. **Copy review summary** — flagged issues and open questions before anything goes live\n\n## Quality Gate\n\nBefore delivering any piece:\n\n- every deliverable sounds like the same author\n- no hollow superlatives or filler adjectives remain\n- every CTA is specific and earned (never \"learn more\" or \"click here\")\n- no copy is duplicated verbatim across platforms\n- hero copy passes the 5-second test\n- email subjects match email body (no bait-and-switch)\n- ad claims match landing page claims exactly\n- no copy would work unchanged for any other product in the category\n\n## Hard Bans\n\nDelete and rewrite any:\n\n- \"game-changing\", \"revolutionary\", \"world-class\", \"cutting-edge\"\n- \"In today's competitive landscape\"\n- fake urgency not backed by a real deadline\n- hollow social proof without specifics (\"thousands trust us\")\n- generic CTAs (\"learn more\", \"find out more\", \"click here\")\n- copy that could be unplugged and dropped into a competitor's campaign unchanged\n\n## Related Skills\n\n- `brand-voice` — source-derived voice capture (run before content production)\n- `content-engine` — platform-native content production\n- `crosspost` — multi-platform distribution\n- `market-research` — audience and competitive intelligence\n- `seo` — on-page optimisation for landing page copy\n","# Marketing Campaign\n\nPlan and execute launch campaigns that convert — not just campaigns that ship.\n\n## When to Activate\n\n- planning a product or feature launch\n- building a full content suite from a single product brief\n- defining positioning and campaign angle before writing any copy\n- orchestrating multiple content types across channels\n- reviewing copy for conversion quality and brand consistency\n\n## Non-Negotiables\n\n1. Define positioning before writing any copy. All copy flows from the angle.\n2. Research the audience before assuming you know their language or fears.\n3. Each deliverable must serve one clear purpose in the campaign arc.\n4. Specificity beats adjectives in every format and on every channel.\n5. The same voice must run across every channel and every piece.\n6. No copy ships without passing the quality gate.\n\n## Campaign Workflow\n\n### Phase 1: Research\n\nUse `market-research` to:\n- profile the target audience (jobs-to-be-done, fears, language, alternatives they use)\n- map 3+ direct or adjacent competitors (positioning, gaps, messaging weaknesses)\n- identify 1–3 audience insights the campaign angle will exploit\n\nDeliverable: a short research brief (audience profile + competitive summary + key insights).\n\n### Phase 2: Positioning\n\nProduce:\n- core benefit statement (one sentence, no feature list, no jargon)\n- positioning formula: \"[Product] helps [audience] [achieve outcome] by [mechanism]\"\n- campaign angle: the specific tension, insight, or moment the whole campaign lives in\n- tone profile: lock before writing (delegate to `brand-voice` for durable, session-reusable voice capture)\n\nDo not write any copy until positioning and angle are approved.\n\n### Phase 3: Content Production\n\nProduce in this order — each layer informs the next:\n\n1. **Landing page copy** (all sections: hero, problem, solution, features, how it works, proof, CTA)\n2. **Email sequence** (each email has one purpose; follow the arc: problem → education → agitation → solution → proof → urgency → final CTA)\n3. **Social posts** (platform-native via `content-engine`; LinkedIn and X are different formats, not the same copy resized)\n4. **Short-form video scripts** (timestamp-blocked; written for screen and ear, not the page)\n5. **Ad copy variants** (3–4 variants testing different angles or audience segments)\n6. **Content calendar** (day-by-day schedule with channel, type, timing, and dependencies)\n\n### Phase 4: Review\n\nGate every deliverable:\n- 5-second test on all hero \u002F above-fold copy (clear who it's for, what it does, why act now)\n- CTA audit (one per piece, specific, earned — not demanded)\n- Tone consistency check across all channels\n- Claim audit (every claim is specific and supportable)\n- Cross-channel consistency (ad claims match landing page; email body matches subject)\n\n## Output Contract\n\nA full campaign delivers:\n\n1. **Positioning brief** — angle, core benefit statement, tone profile\n2. **Landing page copy** — hero, problem, solution, features, how it works, proof, CTA\n3. **Email sequence** — subject + preview + body + CTA for each email, labelled by day and purpose\n4. **LinkedIn posts** — 3+ platform-native posts with distinct angles\n5. **X posts** — 5+ standalone posts + 1 thread\n6. **Short-form video scripts** — 2+ timestamp-blocked scripts with visual direction notes\n7. **Ad copy variants** — short headline \u002F long headline \u002F body per variant\n8. **Content calendar** — day-by-day schedule with channel, content type, timing, and dependencies\n9. **Copy review summary** — flagged issues and open questions before anything goes live\n\n## Quality Gate\n\nBefore delivering any piece:\n\n- every deliverable sounds like the same author\n- no hollow superlatives or filler adjectives remain\n- every CTA is specific and earned (never \"learn more\" or \"click here\")\n- no copy is duplicated verbatim across platforms\n- hero copy passes the 5-second test\n- email subjects match email body (no bait-and-switch)\n- ad claims match landing page claims exactly\n- no copy would work unchanged for any other product in the category\n\n## Hard Bans\n\nDelete and rewrite any:\n\n- \"game-changing\", \"revolutionary\", \"world-class\", \"cutting-edge\"\n- \"In today's competitive landscape\"\n- fake urgency not backed by a real deadline\n- hollow social proof without specifics (\"thousands trust us\")\n- generic CTAs (\"learn more\", \"find out more\", \"click here\")\n- copy that could be unplugged and dropped into a competitor's campaign unchanged\n\n## Related Skills\n\n- `brand-voice` — source-derived voice capture (run before content production)\n- `content-engine` — platform-native content production\n- `crosspost` — multi-platform distribution\n- `market-research` — audience and competitive intelligence\n- `seo` — on-page optimisation for landing page copy\n",{"name":5,"metadata":24,"description":7},{"origin":25},"ECC","main","c32dc0b68600587f78aff3310f3bbd4212173ab3",".kilo\u002Fskills\u002Fmarketing-campaign",1,"https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko","https:\u002F\u002Fko-lang.ai.studio","https:\u002F\u002Fgithub.com\u002Flytong760-cell","hanaminikata.com","hello ","2026-11-05 18:26:32",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add lytong760-cell\u002Fcompiler_ko --skill marketing-campaign",{"tool":42,"command":43},"bunx","bunx skills add lytong760-cell\u002Fcompiler_ko --skill marketing-campaign",{"tool":45,"command":46},"pnpm","pnpm dlx skills add lytong760-cell\u002Fcompiler_ko --skill marketing-campaign","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fmarketing-campaign\u002FSKILL.md",true,[],[51,58,65,72,79,86],{"skillNo":52,"name":53,"nameZh":6,"description":54,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M7B36K22Z7155PTGEGTSDNJ4","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fx-api\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7B36HCAE9ESGBVS6J0FR52F","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7B36DYH4ZFJ3GZHPAEMVQAY","workspace-surface-audit","Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup, then recommend the highest-value ECC-native skills, hooks, agents, and operator workflows. Use when the user wants help setting up Claude Code or understanding what capabilities are actually available in their environment.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fworkspace-surface-audit\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7B36A1QXMEZT8VZMFVQNR5E","wizard","Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwizard\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7B364EK3N88VQQJ6HFATJQE","windows-desktop-e2e","E2E testing for Windows native desktop apps (WPF, WinForms, Win32\u002FMFC, Qt) using pywinauto and Windows UI Automation. Use when writing E2E tests for a Windows native desktop app with pywinauto or UI Automation.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwindows-desktop-e2e\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7B360YF7GGNAF21KT4QB5PG","wayfinder","Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.","https:\u002F\u002Fgithub.com\u002Flytong760-cell\u002Fcompiler_ko\u002Fblob\u002Fmain\u002F.kilo\u002Fskills\u002Fwayfinder\u002FSKILL.md",[],[]]