--- name: content-strategy description: "Content Strategy workflow skill. Use this skill when the user needs Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off." version: "0.0.1" category: content-media tags: ["content-strategy", "plan", "content", "strategy", "topic", "clusters", "editorial", "roadmap"] complexity: advanced risk: safe tools: ["codex-cli", "claude-code", "cursor", "gemini-cli", "opencode"] source: community author: "sickn33" date_added: "2026-04-14" date_updated: "2026-04-25" --- # Content Strategy ## Overview This public intake copy packages `plugins/antigravity-awesome-skills-claude/skills/content-strategy` from `https://github.com/sickn33/antigravity-awesome-skills` into the native Omni Skills editorial shape without hiding its origin. Use it when the operator needs the upstream workflow, support files, and repository context to stay intact while the public validator and private enhancer continue their normal downstream flow. This intake keeps the copied upstream files intact and uses the `external_source` block in `metadata.json` plus `ORIGIN.md` as the provenance anchor for review. # Content Strategy You 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. Imported source sections that did not map cleanly to the public headings are still preserved below or in the support files. Notable imported sections: Before Planning, Searchable vs Shareable, Content Types, Content Pillars and Topic Clusters, Keyword Research by Buyer Stage, Content Ideation Sources. ## When to Use This Skill Use this section as the trigger filter. It should make the activation boundary explicit before the operator loads files, runs commands, or opens a pull request. - Use when deciding what content to create, in what order, and for which audience. - Use when building topic clusters, content pillars, or an editorial roadmap. - Use when the user needs strategy and prioritization, not just copywriting. - Use when the request clearly matches the imported source intent: Plan a content strategy, topic clusters, editorial roadmap, and content mix for traffic, authority, and lead generation. Use when deciding what to publish, what topics to prioritize, or how to structure a content program. - Use when the operator should preserve upstream workflow detail instead of rewriting the process from scratch. - Use when provenance needs to stay visible in the answer, PR, or review packet. ## Operating Table | Situation | Start here | Why it matters | | --- | --- | --- | | First-time use | `metadata.json` | Confirms repository, branch, commit, and imported path through the `external_source` block before touching the copied workflow | | Provenance review | `ORIGIN.md` | Gives reviewers a plain-language audit trail for the imported source | | Workflow execution | `references/headless-cms.md` | Starts with the smallest copied file that materially changes execution | | Supporting context | `evals/evals.json` | Adds the next most relevant copied source file without loading the entire package | | Handoff decision | `## Related Skills` | Helps the operator switch to a stronger native skill when the task drifts | ## Workflow This workflow is intentionally editorial and operational at the same time. It keeps the imported source useful to the operator while still satisfying the public intake standards that feed the downstream enhancer flow. 1. Confirm the user goal, the scope of the imported workflow, and whether this skill is still the right router for the task. 2. Read the overview and provenance files before loading any copied upstream support files. 3. Load only the references, examples, prompts, or scripts that materially change the outcome for the current request. 4. Execute the upstream workflow while keeping provenance and source boundaries explicit in the working notes. 5. Validate the result against the upstream expectations and the evidence you can point to in the copied files. 6. Escalate or hand off to a related skill when the work moves out of this imported workflow's center of gravity. 7. Before merge or closure, record what was used, what changed, and what the reviewer still needs to verify. ### Imported Workflow Notes #### Imported: Before Planning **Check for product marketing context first:** If `.agents/product-marketing-context.md` exists (or `.claude/product-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. Gather this context (ask if not provided): ### 1. Business Context - What does the company do? - Who is the ideal customer? - What's the primary goal for content? (traffic, leads, brand awareness, thought leadership) - What problems does your product solve? ### 2. Customer Research - What questions do customers ask before buying? - What objections come up in sales calls? - What topics appear repeatedly in support tickets? - What language do customers use to describe their problems? ### 3. Current State - Do you have existing content? What's working? - What resources do you have? (writers, budget, time) - What content formats can you produce? (written, video, audio) ### 4. Competitive Landscape - Who are your main competitors? - What content gaps exist in your market? --- ## Examples ### Example 1: Ask for the upstream workflow directly ```text Use @content-strategy to handle . Start from the copied upstream workflow, load only the files that change the outcome, and keep provenance visible in the answer. ``` **Explanation:** This is the safest starting point when the operator needs the imported workflow, but not the entire repository. ### Example 2: Ask for a provenance-grounded review ```text Review @content-strategy against metadata.json and ORIGIN.md, then explain which copied upstream files you would load first and why. ``` **Explanation:** Use this before review or troubleshooting when you need a precise, auditable explanation of origin and file selection. ### Example 3: Narrow the copied support files before execution ```text Use @content-strategy for . Load only the copied references, examples, or scripts that change the outcome, and name the files explicitly before proceeding. ``` **Explanation:** This keeps the skill aligned with progressive disclosure instead of loading the whole copied package by default. ### Example 4: Build a reviewer packet ```text Review @content-strategy using the copied upstream files plus provenance, then summarize any gaps before merge. ``` **Explanation:** This is useful when the PR is waiting for human review and you want a repeatable audit packet. ## Best Practices Treat the generated public skill as a reviewable packaging layer around the upstream repository. The goal is to keep provenance explicit and load only the copied source material that materially improves execution. - Keep the imported skill grounded in the upstream repository; do not invent steps that the source material cannot support. - Prefer the smallest useful set of support files so the workflow stays auditable and fast to review. - Keep provenance, source commit, and imported file paths visible in notes and PR descriptions. - Point directly at the copied upstream files that justify the workflow instead of relying on generic review boilerplate. - Treat generated examples as scaffolding; adapt them to the concrete task before execution. - Route to a stronger native skill when architecture, debugging, design, or security concerns become dominant. ## Troubleshooting ### Problem: The operator skipped the imported context and answered too generically **Symptoms:** The result ignores the upstream workflow in `plugins/antigravity-awesome-skills-claude/skills/content-strategy`, fails to mention provenance, or does not use any copied source files at all. **Solution:** Re-open `metadata.json`, `ORIGIN.md`, and the most relevant copied upstream files. Check the `external_source` block first, then restate the provenance before continuing. ### Problem: The imported workflow feels incomplete during review **Symptoms:** Reviewers can see the generated `SKILL.md`, but they cannot quickly tell which references, examples, or scripts matter for the current task. **Solution:** Point at the exact copied references, examples, scripts, or assets that justify the path you took. If the gap is still real, record it in the PR instead of hiding it. ### Problem: The task drifted into a different specialization **Symptoms:** The imported skill starts in the right place, but the work turns into debugging, architecture, design, security, or release orchestration that a native skill handles better. **Solution:** Use the related skills section to hand off deliberately. Keep the imported provenance visible so the next skill inherits the right context instead of starting blind. ## Related Skills - `@00-andruia-consultant` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@00-andruia-consultant-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith` - Use when the work is better handled by that native specialization after this imported skill establishes context. - `@10-andruia-skill-smith-v2` - Use when the work is better handled by that native specialization after this imported skill establishes context. ## Additional Resources Use this support matrix and the linked files below as the operator packet for this imported skill. They should reflect real copied source material, not generic scaffolding. | Resource family | What it gives the reviewer | Example path | | --- | --- | --- | | `references` | copied reference notes, guides, or background material from upstream | `references/headless-cms.md` | | `examples` | worked examples or reusable prompts copied from upstream | `examples/n/a` | | `scripts` | upstream helper scripts that change execution or validation | `scripts/n/a` | | `agents` | routing or delegation notes that are genuinely part of the imported package | `agents/n/a` | | `assets` | supporting assets or schemas copied from the source package | `assets/n/a` | - [headless-cms.md](references/headless-cms.md) - [evals.json](evals/evals.json) - [headless-cms.md](references/headless-cms.md) ### Imported Reference Notes #### Imported: References - **[Headless CMS Guide](references/headless-cms.md)**: CMS selection, content modeling for marketing, editorial workflows, platform comparison (Sanity, Contentful, Strapi) --- #### Imported: Searchable vs Shareable Every piece of content must be searchable, shareable, or both. Prioritize in that order—search traffic is the foundation. **Searchable content** captures existing demand. Optimized for people actively looking for answers. **Shareable content** creates demand. Spreads ideas and gets people talking. ### When Writing Searchable Content - Target a specific keyword or question - Match search intent exactly—answer what the searcher wants - Use clear titles that match search queries - Structure with headings that mirror search patterns - Place keywords in title, headings, first paragraph, URL - Provide comprehensive coverage (don't leave questions unanswered) - Include data, examples, and links to authoritative sources - Optimize for AI/LLM discovery: clear positioning, structured content, brand consistency across the web ### When Writing Shareable Content - Lead with a novel insight, original data, or counterintuitive take - Challenge conventional wisdom with well-reasoned arguments - Tell stories that make people feel something - Create content people want to share to look smart or help others - Connect to current trends or emerging problems - Share vulnerable, honest experiences others can learn from --- #### Imported: Content Types ### Searchable Content Types **Use-Case Content** Formula: [persona] + [use-case]. Targets long-tail keywords. - "Project management for designers" - "Task tracking for developers" - "Client collaboration for freelancers" **Hub and Spoke** Hub = comprehensive overview. Spokes = related subtopics. ``` /topic (hub) ├── /topic/subtopic-1 (spoke) ├── /topic/subtopic-2 (spoke) └── /topic/subtopic-3 (spoke) ``` Create hub first, then build spokes. Interlink strategically. **Note:** Most content works fine under `/blog`. Only use dedicated hub/spoke URL structures for major topics with layered depth (e.g., Atlassian's `/agile` guide). For typical blog posts, `/blog/post-title` is sufficient. **Template Libraries** High-intent keywords + product adoption. - Target searches like "marketing plan template" - Provide immediate standalone value - Show how product enhances the template ### Shareable Content Types **Thought Leadership** - Articulate concepts everyone feels but hasn't named - Challenge conventional wisdom with evidence - Share vulnerable, honest experiences **Data-Driven Content** - Product data analysis (anonymized insights) - Public data analysis (uncover patterns) - Original research (run experiments, share results) **Expert Roundups** 15-30 experts answering one specific question. Built-in distribution. **Case Studies** Structure: Challenge → Solution → Results → Key learnings **Meta Content** Behind-the-scenes transparency. "How We Got Our First $5k MRR," "Why We Chose Debt Over VC." For programmatic content at scale, see **programmatic-seo** skill. --- #### Imported: Content Pillars and Topic Clusters Content pillars are the 3-5 core topics your brand will own. Each pillar spawns a cluster of related content. Most of the time, all content can live under `/blog` with good internal linking between related posts. Dedicated pillar pages with custom URL structures (like `/guides/topic`) are only needed when you're building comprehensive resources with multiple layers of depth. ### How to Identify Pillars 1. **Product-led**: What problems does your product solve? 2. **Audience-led**: What does your ICP need to learn? 3. **Search-led**: What topics have volume in your space? 4. **Competitor-led**: What are competitors ranking for? ### Pillar Structure ``` Pillar Topic (Hub) ├── Subtopic Cluster 1 │ ├── Article A │ ├── Article B │ └── Article C ├── Subtopic Cluster 2 │ ├── Article D │ ├── Article E │ └── Article F └── Subtopic Cluster 3 ├── Article G ├── Article H └── Article I ``` ### Pillar Criteria Good pillars should: - Align with your product/service - Match what your audience cares about - Have search volume and/or social interest - Be broad enough for many subtopics --- #### Imported: Keyword Research by Buyer Stage Map topics to the buyer's journey using proven keyword modifiers: ### Awareness Stage Modifiers: "what is," "how to," "guide to," "introduction to" Example: If customers ask about project management basics: - "What is Agile Project Management" - "Guide to Sprint Planning" - "How to Run a Standup Meeting" ### Consideration Stage Modifiers: "best," "top," "vs," "alternatives," "comparison" Example: If customers evaluate multiple tools: - "Best Project Management Tools for Remote Teams" - "Asana vs Trello vs Monday" - "Basecamp Alternatives" ### Decision Stage Modifiers: "pricing," "reviews," "demo," "trial," "buy" Example: If pricing comes up in sales calls: - "Project Management Tool Pricing Comparison" - "How to Choose the Right Plan" - "[Product] Reviews" ### Implementation Stage Modifiers: "templates," "examples," "tutorial," "how to use," "setup" Example: If support tickets show implementation struggles: - "Project Template Library" - "Step-by-Step Setup Tutorial" - "How to Use [Feature]" --- #### Imported: Content Ideation Sources ### 1. Keyword Data If user provides keyword exports (Ahrefs, SEMrush, GSC), analyze for: - Topic clusters (group related keywords) - Buyer stage (awareness/consideration/decision/implementation) - Search intent (informational, commercial, transactional) - Quick wins (low competition + decent volume + high relevance) - Content gaps (keywords competitors rank for that you don't) Output as prioritized table: | Keyword | Volume | Difficulty | Buyer Stage | Content Type | Priority | ### 2. Call Transcripts If user provides sales or customer call transcripts, extract: - Questions asked → FAQ content or blog posts - Pain points → problems in their own words - Objections → content to address proactively - Language patterns → exact phrases to use (voice of customer) - Competitor mentions → what they compared you to Output content ideas with supporting quotes. ### 3. Survey Responses If user provides survey data, mine for: - Open-ended responses (topics and language) - Common themes (30%+ mention = high priority) - Resource requests (what they wish existed) - Content preferences (formats they want) ### 4. Forum Research Use web search to find content ideas: **Reddit:** `site:reddit.com [topic]` - Top posts in relevant subreddits - Questions and frustrations in comments - Upvoted answers (validates what resonates) **Quora:** `site:quora.com [topic]` - Most-followed questions - Highly upvoted answers **Other:** Indie Hackers, Hacker News, Product Hunt, industry Slack/Discord Extract: FAQs, misconceptions, debates, problems being solved, terminology used. ### 5. Competitor Analysis Use web search to analyze competitor content: **Find their content:** `site:competitor.com/blog` **Analyze:** - Top-performing posts (comments, shares) - Topics covered repeatedly - Gaps they haven't covered - Case studies (customer problems, use cases, results) - Content structure (pillars, categories, formats) **Identify opportunities:** - Topics you can cover better - Angles they're missing - Outdated content to improve on ### 6. Sales and Support Input Extract from customer-facing teams: - Common objections - Repeated questions - Support ticket patterns - Success stories - Feature requests and underlying problems --- #### Imported: Prioritizing Content Ideas Score each idea on four factors: ### 1. Customer Impact (40%) - How frequently did this topic come up in research? - What percentage of customers face this challenge? - How emotionally charged was this pain point? - What's the potential LTV of customers with this need? ### 2. Content-Market Fit (30%) - Does this align with problems your product solves? - Can you offer unique insights from customer research? - Do you have customer stories to support this? - Will this naturally lead to product interest? ### 3. Search Potential (20%) - What's the monthly search volume? - How competitive is this topic? - Are there related long-tail opportunities? - Is search interest growing or declining? ### 4. Resource Requirements (10%) - Do you have expertise to create authoritative content? - What additional research is needed? - What assets (graphics, data, examples) will you need? ### Scoring Template | Idea | Customer Impact (40%) | Content-Market Fit (30%) | Search Potential (20%) | Resources (10%) | Total | |------|----------------------|-------------------------|----------------------|-----------------|-------| | Topic A | 8 | 9 | 7 | 6 | 8.0 | | Topic B | 6 | 7 | 9 | 8 | 7.1 | --- #### Imported: Output Format When creating a content strategy, provide: ### 1. Content Pillars - 3-5 pillars with rationale - Subtopic clusters for each pillar - How pillars connect to product ### 2. Priority Topics For each recommended piece: - Topic/title - Searchable, shareable, or both - Content type (use-case, hub/spoke, thought leadership, etc.) - Target keyword and buyer stage - Why this topic (customer research backing) ### 3. Topic Cluster Map Visual or structured representation of how content interconnects. --- #### Imported: Task-Specific Questions 1. What patterns emerge from your last 10 customer conversations? 2. What questions keep coming up in sales calls? 3. Where are competitors' content efforts falling short? 4. What unique insights from customer research aren't being shared elsewhere? 5. Which existing content drives the most conversions, and why? --- #### Imported: Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.