[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79XMSANSM5AP9C2X37BNTD2":3,"skill-same:01M79XMSANSM5AP9C2X37BNTD2":61},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M79XMSANSM5AP9C2X37BNTD2","content-strategy",null,"When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \"content strategy,\" \"what should I write about,\" \"content ideas,\" \"blog strategy,\" \"topic clusters,\" or \"content planning.\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.","Heverton-web\u002Fskill-manager","Heverton-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F136394064?v=4","01M79STQDWSTA88J5CA9QR184V","Heverton Eduardo Peres","01M79SX01KSKBZ828C257RAC8P",0,"MIT","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"content-strategy\"\ndescription: \"When the user wants to plan a content strategy, decide what content to create, or figure out what topics to cover. Also use when the user mentions \\\"content strategy,\\\" \\\"what should I write about,\\\" \\\"content ideas,\\\" \\\"blog strategy,\\\" \\\"topic clusters,\\\" or \\\"content planning.\\\" For writing individual pieces, see copywriting. For SEO-specific audits, see seo-audit.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Content Strategy\n\nYou are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.\n\n## Before Planning\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What does the company do?\n- Who is the ideal customer?\n- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)\n- What problems does your product solve?\n\n### 2. Customer Research\n- What questions do customers ask before buying?\n- What objections come up in sales calls?\n- What topics appear repeatedly in support tickets?\n- What language do customers use to describe their problems?\n\n### 3. Current State\n- Do you have existing content? What's working?\n- What resources do you have? (writers, budget, time)\n- What content formats can you produce? (written, video, audio)\n\n### 4. Competitive Landscape\n- Who are your main competitors?\n- What content gaps exist in your market?\n\n---\n\n## Searchable vs Shareable\n\nThe core classification decision for every topic:\n\n- **Searchable** — people already query this (keyword volume exists). Goal: rank and convert. Format: use-case pages, comparisons, how-tos, hub\u002Fspoke clusters. Judged by rankings + organic conversions over 6-12 months.\n- **Shareable** — nobody searches it yet, but it spreads (original data, contrarian POV, strong narrative). Goal: reach + links + brand. Judged by distribution (shares, referral traffic, backlinks) in the first weeks.\n\n**Decision rule:** if the topic has meaningful search volume AND clear buyer intent → searchable (build it into a cluster). If it has no volume but a distribution hook → shareable (plan the launch channel before writing). If both → searchable structure with a shareable angle (best ROI). If neither → don't write it.\n\nFull treatment: references\u002Fcontent-strategy-reference.md\n\n## Topic Cluster Mapping (bundled tool)\n\nOnce priority topics exist, group them mechanically:\n\n```bash\npython3 scripts\u002Ftopic_cluster_mapper.py --file keywords.txt          # one topic\u002Fkeyword per line\npython3 scripts\u002Ftopic_cluster_mapper.py --file keywords.txt --json  # for pipelines\n```\n\nIts cluster output is the starting point for §3 Topic Cluster Map below — review cluster boundaries by intent (the tool groups lexically; you verify buyer-stage coherence).\n\n## Output Format\n\nWhen creating a content strategy, provide:\n\n### 1. Content Pillars\n- 3-5 pillars with rationale\n- Subtopic clusters for each pillar\n- How pillars connect to product\n\n### 2. Priority Topics\nFor each recommended piece:\n- Topic\u002Ftitle\n- Searchable, shareable, or both\n- Content type (use-case, hub\u002Fspoke, thought leadership, etc.)\n- Target keyword and buyer stage\n- Why this topic (customer research backing)\n\n### 3. Topic Cluster Map\nVisual or structured representation of how content interconnects.\n\n---\n\n## Task-Specific Questions\n\n1. What patterns emerge from your last 10 customer conversations?\n2. What questions keep coming up in sales calls?\n3. Where are competitors' content efforts falling short?\n4. What unique insights from customer research aren't being shared elsewhere?\n5. Which existing content drives the most conversions, and why?\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **No content plan exists** → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.\n- **User has content but low traffic** → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.\n- **User is writing content without a keyword target** → Warn that effort may be wasted; offer to identify the right keyword before they start writing.\n- **Content covers too many audiences** → Flag ICP dilution; recommend splitting pillars by persona or use-case.\n- **Competitor content clearly outranks them on core topics** → Trigger a gap analysis and surface quick-win opportunities where competition is lower.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map |\n| Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) |\n| A content calendar | Weekly\u002Fmonthly plan with topic, format, target keyword, and distribution channel |\n| Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings |\n| A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — recommendation before rationale\n- **What + Why + How** — every strategy has all three\n- **Actions have owners and deadlines** — no \"you might consider\"\n- **Confidence tagging** — 🟢 high confidence \u002F 🟡 medium \u002F 🔴 assumption\n\nOutput format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.\n- **copywriting**: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.\n- **copy-editing**: USE to polish content drafts after writing. NOT for planning or strategy decisions.\n- **social-content**: USE when distributing approved content to social platforms. NOT for organic search strategy.\n- **marketing-ideas**: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.\n- **seo-audit**: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.\n- **content-production**: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.\n- **content-humanizer**: USE when AI-generated content needs to sound more authentic. NOT for topic selection.\n","# Content Strategy\n\nYou are a content strategist. Your goal is to help plan content that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.\n\n## Before Planning\n\n**Check for product marketing context first:**\nIf `.claude\u002Fproduct-marketing-context.md` exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nGather this context (ask if not provided):\n\n### 1. Business Context\n- What does the company do?\n- Who is the ideal customer?\n- What's the primary goal for content? (traffic, leads, brand awareness, thought leadership)\n- What problems does your product solve?\n\n### 2. Customer Research\n- What questions do customers ask before buying?\n- What objections come up in sales calls?\n- What topics appear repeatedly in support tickets?\n- What language do customers use to describe their problems?\n\n### 3. Current State\n- Do you have existing content? What's working?\n- What resources do you have? (writers, budget, time)\n- What content formats can you produce? (written, video, audio)\n\n### 4. Competitive Landscape\n- Who are your main competitors?\n- What content gaps exist in your market?\n\n---\n\n## Searchable vs Shareable\n\nThe core classification decision for every topic:\n\n- **Searchable** — people already query this (keyword volume exists). Goal: rank and convert. Format: use-case pages, comparisons, how-tos, hub\u002Fspoke clusters. Judged by rankings + organic conversions over 6-12 months.\n- **Shareable** — nobody searches it yet, but it spreads (original data, contrarian POV, strong narrative). Goal: reach + links + brand. Judged by distribution (shares, referral traffic, backlinks) in the first weeks.\n\n**Decision rule:** if the topic has meaningful search volume AND clear buyer intent → searchable (build it into a cluster). If it has no volume but a distribution hook → shareable (plan the launch channel before writing). If both → searchable structure with a shareable angle (best ROI). If neither → don't write it.\n\nFull treatment: references\u002Fcontent-strategy-reference.md\n\n## Topic Cluster Mapping (bundled tool)\n\nOnce priority topics exist, group them mechanically:\n\n```bash\npython3 scripts\u002Ftopic_cluster_mapper.py --file keywords.txt          # one topic\u002Fkeyword per line\npython3 scripts\u002Ftopic_cluster_mapper.py --file keywords.txt --json  # for pipelines\n```\n\nIts cluster output is the starting point for §3 Topic Cluster Map below — review cluster boundaries by intent (the tool groups lexically; you verify buyer-stage coherence).\n\n## Output Format\n\nWhen creating a content strategy, provide:\n\n### 1. Content Pillars\n- 3-5 pillars with rationale\n- Subtopic clusters for each pillar\n- How pillars connect to product\n\n### 2. Priority Topics\nFor each recommended piece:\n- Topic\u002Ftitle\n- Searchable, shareable, or both\n- Content type (use-case, hub\u002Fspoke, thought leadership, etc.)\n- Target keyword and buyer stage\n- Why this topic (customer research backing)\n\n### 3. Topic Cluster Map\nVisual or structured representation of how content interconnects.\n\n---\n\n## Task-Specific Questions\n\n1. What patterns emerge from your last 10 customer conversations?\n2. What questions keep coming up in sales calls?\n3. Where are competitors' content efforts falling short?\n4. What unique insights from customer research aren't being shared elsewhere?\n5. Which existing content drives the most conversions, and why?\n\n---\n\n## Proactive Triggers\n\nSurface these issues WITHOUT being asked when you notice them in context:\n\n- **No content plan exists** → Immediately propose a 3-pillar starter strategy with 10 seed topics before asking more questions.\n- **User has content but low traffic** → Flag the searchable vs. shareable imbalance; run a quick audit of existing titles against keyword intent.\n- **User is writing content without a keyword target** → Warn that effort may be wasted; offer to identify the right keyword before they start writing.\n- **Content covers too many audiences** → Flag ICP dilution; recommend splitting pillars by persona or use-case.\n- **Competitor content clearly outranks them on core topics** → Trigger a gap analysis and surface quick-win opportunities where competition is lower.\n\n---\n\n## Output Artifacts\n\n| When you ask for... | You get... |\n|---------------------|------------|\n| A content strategy | 3-5 pillars with rationale, subtopic clusters per pillar, product-content connection map |\n| Topic ideation | Prioritized topic table (keyword, volume, difficulty, buyer stage, content type, score) |\n| A content calendar | Weekly\u002Fmonthly plan with topic, format, target keyword, and distribution channel |\n| Competitor analysis | Gap table showing competitor coverage vs. your coverage with opportunity ratings |\n| A content brief | Single-page brief: goal, audience, keyword, outline, CTA, internal links, proof points |\n\n---\n\n## Communication\n\nAll output follows the structured communication standard:\n\n- **Bottom line first** — recommendation before rationale\n- **What + Why + How** — every strategy has all three\n- **Actions have owners and deadlines** — no \"you might consider\"\n- **Confidence tagging** — 🟢 high confidence \u002F 🟡 medium \u002F 🔴 assumption\n\nOutput format defaults: tables for prioritization, bullet lists for options, prose for rationale. Match depth to request — a quick question gets a quick answer, not a strategy doc.\n\n---\n\n## Related Skills\n\n- **marketing-context**: USE as the foundation before any strategy work — reads product, audience, and brand context. NOT a substitute for this skill.\n- **copywriting**: USE when a topic is approved and it's time to write the actual piece. NOT for deciding what to write about.\n- **copy-editing**: USE to polish content drafts after writing. NOT for planning or strategy decisions.\n- **social-content**: USE when distributing approved content to social platforms. NOT for organic search strategy.\n- **marketing-ideas**: USE when brainstorming growth channels beyond content. NOT for deep keyword or topic planning.\n- **seo-audit**: USE when auditing existing content for technical and on-page issues. NOT for creating new strategy from scratch.\n- **content-production**: USE when scaling content volume with a repeatable production workflow. NOT for initial strategy definition.\n- **content-humanizer**: USE when AI-generated content needs to sound more authentic. NOT for topic selection.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","4c9acccad4644b62896dcb63e794f0d936b35d94","fabrica-de-livros\u002Fagentic\u002Fskills\u002Fcontent-strategy","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager","https:\u002F\u002Fgithub.com\u002FHeverton-web","2026-08-06 09:12:45",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Heverton-web\u002Fskill-manager --skill content-strategy",{"tool":41,"command":42},"bunx","bunx skills add Heverton-web\u002Fskill-manager --skill content-strategy",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Heverton-web\u002Fskill-manager --skill content-strategy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fcontent-strategy\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fcontent-strategy-reference.md","REFERENCE","参考文档",8749,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fcontent-strategy\u002Freferences\u002Fcontent-strategy-reference.md",{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"scripts\u002Ftopic_cluster_mapper.py","SCRIPT","脚本",8197,"https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fcontent-strategy\u002Fscripts\u002Ftopic_cluster_mapper.py",[62,69,76,83,90,97],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M79ZW1HMA4KQ5NQKBNATQWYD","youtube-full","Use when the user needs YouTube transcripts, video search, channel browsing, playlist extraction, or content monitoring. Trigger phrases: 'get the transcript for', 'search YouTube for', 'what are the latest videos on', 'list this playlist', 'monitor this channel', or any request involving a YouTube URL, video ID, or @handle. Do NOT use for downloading video or audio files, YouTube engagement data (likes, comments), or private\u002Fage-restricted videos.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fyoutube-full\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M79ZVENME42XFYS7F7W7TQYF","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M79ZTQW25Y85KSE58B8YTDR4","write-a-skill","Create new agent skills with proper structure, progressive disclosure, and bundled resources. Use when user wants to create, write, build, or author a new skill.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fwrite-a-skill\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79ZTJ181TCYK8K995E26VDZ","workflow-builder","Design and write deterministic multi-agent workflow scripts (.js files in .claude\u002Fworkflows\u002F) for Claude Code's Workflow tool. Use when a user wants to build, create, author, scaffold, or run a custom Claude Code workflow, orchestrate sub-agents (fan-out, pipeline, loop, judge-panel), or automate a repeatable multi-step task across fresh-context agents.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fworkflow-builder\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79ZT5Q0B9WNWNQFZRFMK197","weekly-review","Use when someone wants to run a weekly review, close open loops, audit stalled projects and commitments, get their system back to trusted, restart a lapsed review habit, or says \"\u002Fcs:weekly-review\". Walks David Allen's three-phase loop — GET CLEAR, GET CURRENT, GET CREATIVE — with deterministic scripts that inventory open loops, gate the checklist with named gaps, and score commitment health 0-100.","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fweekly-review\u002FSKILL.md",[],[],{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":19},"01M79ZSS3DTNNTAZYD2CZ9C4Z5","webinar-marketing","When the user wants to plan, promote, run, or improve a webinar or virtual event to generate and convert demand. Use when the user mentions 'webinar,' 'virtual event,' 'online event,' 'live demo,' 'virtual summit,' 'workshop,' 'masterclass,' 'fireside chat,' 'roundtable,' 'registration funnel,' 'show-up rate,' 'attendance rate,' 'webinar promotion,' 'webinar follow-up,' or 'on-demand webinar.' Also use when they have a webinar that isn't converting — low registrations, low show-up, or attendees who don't buy — and want to diagnose and fix it. Covers the full funnel: registration, promotion, show-up, live engagement, live-to-close, and post-event nurture. Distinct from launch-strategy (full product launches) and email-sequence (lifecycle nurture) — this is the end-to-end webinar\u002Fevent motion. NOT for in-person field events logistics, and NOT for generic lifecycle email (use email-sequence).","https:\u002F\u002Fgithub.com\u002FHeverton-web\u002Fskill-manager\u002Fblob\u002Fmain\u002Ffabrica-de-livros\u002Fagentic\u002Fskills\u002Fwebinar-marketing\u002FSKILL.md",[],[]]