[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79MTTZ27AC7JWKMYGQKS7JS":3,"skill-same:01M79MTTZ27AC7JWKMYGQKS7JS":44},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":43},"01M79MTTZ27AC7JWKMYGQKS7JS","content-strategy",null,"Plan a topic map. OmniSkill Social crew — defines audience and goal, builds topic clusters from real demand, and turns them into a sustainable calendar.","IPedrax\u002FOmniSkill","IPedrax","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F64429409?v=4","01M79MSCRSKESGTTRZMGK54KW0","01M79MSCSDY16CNNHW0VRGZFHF",9,"MIT","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: content-strategy\ndescription: Plan a topic map. OmniSkill Social crew — defines audience and goal, builds topic clusters from real demand, and turns them into a sustainable calendar.\ndisable-model-invocation: true\n---\n\n# Content Strategy\n\n> Plans your topic map · OmniSkill Social crew\n\nDeciding what to make, before making it. Run this first for anything ongoing — publishing without a map produces volume, not compounding authority.\n\n## 1. Define the job\n\n**Who** — one primary audience, specifically. Their role, their problem, where they already look for answers.\n\n**What outcome** — organic acquisition, sales enablement, category authority, retention, or hiring. These produce genuinely different content, and a plan optimising for all of them optimises for none.\n\n**How success is measured** — pick the metric now. Qualified signups, assisted pipeline, branded search volume. \"Engagement\" is not a business outcome.\n\n## 2. Build topic clusters\n\nThe unit of strategy is the cluster, not the post: one **pillar** covering a broad topic comprehensively, plus **cluster pieces** covering sub-topics in depth, all interlinked.\n\nThis works because it demonstrates real coverage of a subject rather than isolated pages, and because internal links concentrate authority on the pillar.\n\nChoose 3–5 clusters. More than that spreads thin across every one.\n\nFor each cluster:\n- The pillar topic and target query\n- 5–15 cluster sub-topics from real search demand and real customer questions\n- How they interlink — clusters point to the pillar, pillar points to clusters\n\n## 3. Source topics from evidence\n\nIn rough order of value:\n\n1. **Customer questions** — sales calls, support tickets, onboarding confusion. Highest intent, and nobody else has this data.\n2. **Search demand** — keyword research for volume and difficulty. Start where difficulty is winnable, not where volume is largest.\n3. **Competitor gaps** — what ranks that could be done substantially better, and what nobody has covered.\n4. **Community discussion** — where the audience already argues about the category.\n5. **Original data** — proprietary numbers, surveys, benchmarks. The most defensible content there is, because it cannot be copied.\n\nRank by business relevance × winnability. High-volume terms owned by entrenched publishers are not winnable on a new site, and chasing them wastes the whole quarter.\n\n## 4. Match format to intent\n\nInformational → guide or explainer. Commercial → comparison or alternatives. Transactional → product or landing page. Navigational → docs.\n\nPublishing a product page against an informational query is the most common structural mismatch, and no promotion fixes it. See `\u002Fomniskill:seo-audit`.\n\n## 5. Build a sustainable calendar\n\nSet cadence at what can be sustained for a year, not what looks impressive for a month. One strong piece weekly beats five weekly for three weeks and then nothing.\n\nSequence by dependency: pillar first, then its clusters, then the distribution posts. Reserve roughly 20% of capacity for reactive and opportunistic work.\n\nPlan distribution *with* creation, not after. A piece with no distribution plan is a piece nobody reads. See `\u002Fomniskill:social`.\n\n## 6. Maintain what exists\n\nMost teams under-invest here. Updating a piece that already ranks usually beats writing a new one — the compounding is in the refresh, not the volume.\n\nSchedule quarterly review: refresh what is decaying, consolidate pieces competing for the same query, prune what has never earned traffic.\n\n## 7. Measure\n\nPer cluster, not per post — clusters compound and single posts are noisy. Track organic traffic, rankings for target queries, conversions, and assisted pipeline.\n\nGive it two to three months before judging. Content is a slow instrument and killing a cluster at week four is the most common self-inflicted failure.\n\n## Output\n\nAudience and goal statement, 3–5 clusters with pillars and sub-topics, format and intent per piece, a calendar with owners, a distribution plan, and the measurement framework.\n\n## Checks before delivering\n\n- One primary audience, named specifically.\n- Success metric is a business metric.\n- Topics sourced from evidence, not brainstormed.\n- Difficulty is winnable at current authority.\n- Cadence is honestly sustainable.\n- Distribution and maintenance are planned, not assumed.\n\nFeeds `\u002Fomniskill:pillar-content`, `\u002Fomniskill:social`, and `\u002Fomniskill:email-sequences`.\n","# Content Strategy\n\n> Plans your topic map · OmniSkill Social crew\n\nDeciding what to make, before making it. Run this first for anything ongoing — publishing without a map produces volume, not compounding authority.\n\n## 1. Define the job\n\n**Who** — one primary audience, specifically. Their role, their problem, where they already look for answers.\n\n**What outcome** — organic acquisition, sales enablement, category authority, retention, or hiring. These produce genuinely different content, and a plan optimising for all of them optimises for none.\n\n**How success is measured** — pick the metric now. Qualified signups, assisted pipeline, branded search volume. \"Engagement\" is not a business outcome.\n\n## 2. Build topic clusters\n\nThe unit of strategy is the cluster, not the post: one **pillar** covering a broad topic comprehensively, plus **cluster pieces** covering sub-topics in depth, all interlinked.\n\nThis works because it demonstrates real coverage of a subject rather than isolated pages, and because internal links concentrate authority on the pillar.\n\nChoose 3–5 clusters. More than that spreads thin across every one.\n\nFor each cluster:\n- The pillar topic and target query\n- 5–15 cluster sub-topics from real search demand and real customer questions\n- How they interlink — clusters point to the pillar, pillar points to clusters\n\n## 3. Source topics from evidence\n\nIn rough order of value:\n\n1. **Customer questions** — sales calls, support tickets, onboarding confusion. Highest intent, and nobody else has this data.\n2. **Search demand** — keyword research for volume and difficulty. Start where difficulty is winnable, not where volume is largest.\n3. **Competitor gaps** — what ranks that could be done substantially better, and what nobody has covered.\n4. **Community discussion** — where the audience already argues about the category.\n5. **Original data** — proprietary numbers, surveys, benchmarks. The most defensible content there is, because it cannot be copied.\n\nRank by business relevance × winnability. High-volume terms owned by entrenched publishers are not winnable on a new site, and chasing them wastes the whole quarter.\n\n## 4. Match format to intent\n\nInformational → guide or explainer. Commercial → comparison or alternatives. Transactional → product or landing page. Navigational → docs.\n\nPublishing a product page against an informational query is the most common structural mismatch, and no promotion fixes it. See `\u002Fomniskill:seo-audit`.\n\n## 5. Build a sustainable calendar\n\nSet cadence at what can be sustained for a year, not what looks impressive for a month. One strong piece weekly beats five weekly for three weeks and then nothing.\n\nSequence by dependency: pillar first, then its clusters, then the distribution posts. Reserve roughly 20% of capacity for reactive and opportunistic work.\n\nPlan distribution *with* creation, not after. A piece with no distribution plan is a piece nobody reads. See `\u002Fomniskill:social`.\n\n## 6. Maintain what exists\n\nMost teams under-invest here. Updating a piece that already ranks usually beats writing a new one — the compounding is in the refresh, not the volume.\n\nSchedule quarterly review: refresh what is decaying, consolidate pieces competing for the same query, prune what has never earned traffic.\n\n## 7. Measure\n\nPer cluster, not per post — clusters compound and single posts are noisy. Track organic traffic, rankings for target queries, conversions, and assisted pipeline.\n\nGive it two to three months before judging. Content is a slow instrument and killing a cluster at week four is the most common self-inflicted failure.\n\n## Output\n\nAudience and goal statement, 3–5 clusters with pillars and sub-topics, format and intent per piece, a calendar with owners, a distribution plan, and the measurement framework.\n\n## Checks before delivering\n\n- One primary audience, named specifically.\n- Success metric is a business metric.\n- Topics sourced from evidence, not brainstormed.\n- Difficulty is winnable at current authority.\n- Cadence is honestly sustainable.\n- Distribution and maintenance are planned, not assumed.\n\nFeeds `\u002Fomniskill:pillar-content`, `\u002Fomniskill:social`, and `\u002Fomniskill:email-sequences`.\n",{"name":5,"description":7,"disable-model-invocation":23},true,"main","cc238b48e3c4fe0061cad0b0475142fbff5b183d","skills\u002Fcontent-strategy",0,"https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill","https:\u002F\u002Fgithub.com\u002FIPedrax","2026-10-14 10:26:53",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":23},[33,36,39],{"tool":34,"command":35},"npx","npx skills add IPedrax\u002FOmniSkill --skill content-strategy",{"tool":37,"command":38},"bunx","bunx skills add IPedrax\u002FOmniSkill --skill content-strategy",{"tool":40,"command":41},"pnpm","pnpm dlx skills add IPedrax\u002FOmniSkill --skill content-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",[],[45,52,59,66,73,79],{"skillNo":46,"name":47,"nameZh":6,"description":48,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":49,"categories":50,"keywords":51,"publishedAt":18},"01M79N058MCJZPHNFYZCPJG3ZZ","xlsx","Excel with live formulas. OmniSkill Operations crew — adapter for the xlsx skill, which installs separately.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fxlsx\u002FSKILL.md",[],[],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M79N01GR5C5EK22CKGG38VYH","webapp-testing","Browser-test a web app. OmniSkill Developers crew — drives a real browser to verify user flows, catches console and network errors, and writes tests that do not flake.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M79MZZSJHFKJRE46BNEHCYZ3","web-artifacts","shadcn HTML artifacts. OmniSkill Design crew — bundled copy of the Web Artifacts skill.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fweb-artifacts\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M79MZXFMCV0QSQ2WN316JKGZ","video","Script and produce video. OmniSkill Social crew — structures short-form and long-form video around retention, with shot lists, captions, and platform-specific delivery.","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvideo\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":18},"01M79MZV8SR0N02YX539Z5PS5E","vgpu","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fvgpu\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M79MZS7JG9X0T4T5TGA4MMJS","uisfx","https:\u002F\u002Fgithub.com\u002FIPedrax\u002FOmniSkill\u002Fblob\u002Fmain\u002Fskills\u002Fuisfx\u002FSKILL.md",[],[]]