Works with
Packaged from the source skill for Claude, Codex and 4 more.
What it does
Turns business goals, customer questions and existing performance into content pillars, buyer-stage topics and a prioritized cluster map. It balances searchable and shareable formats, production capacity and distribution rather than simply listing keywords.
Practical limits
Research quality and available production resources constrain the plan; topic selection does not establish search demand or guarantee leads.
What is inside the skill
Section headings from the original SKILL.md (about 2,703 words of instructions). Read the full text in the source repository before installing.
- Before Planning
- 1. Business Context
- 2. Customer Research
- 3. Current State
- 4. Competitive Landscape
- Treat Content Like a Product
- Searchable vs Shareable
- When Writing Searchable Content
- When Writing Shareable Content
- Content Types
- Searchable Content Types
- Shareable Content Types
- Link-Earning Formats
- Content Pillars and Topic Clusters
- How to Identify Pillars
- Pillar Structure
- Pillar Criteria
- Keyword Research by Buyer Stage
- Awareness Stage
- Consideration Stage
- Decision Stage
- Implementation Stage
- Content Ideation Sources
- 1. Keyword Data
Bundled files
evals/evals.jsonreferences/content-distribution.mdreferences/headless-cms.mdLICENSE
Example prompts
- Plan three content pillars for a payroll SaaS using these sales-call objections.
- Prioritize our 40 article ideas for a two-writer team and map internal links between clusters.
How to install Content Strategy
Claude Packaged
- Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files.
- For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
- For Claude apps, upload the ZIP in the Skills section of the capabilities settings.
- Start a new session and describe the task in your own words. Claude picks the skill when the request matches its description.
Codex Packaged
- Download the Codex package. The ZIP contains one folder named after the skill, with SKILL.md and bundled resources.
- Unpack the complete folder into .agents/skills/ inside your repository, or into ~/.agents/skills/ for personal use. Preserve its relative reference-file paths.
- Start a new Codex session and invoke the skill by name or with $skill-name, or describe a matching task.
- AGENTS.md is separate project guidance. The ZIP does not generate or modify that file.
GPT Packaged
- Download the GPT package from the skill page.
- Create or edit a custom GPT (or a ChatGPT project) and paste the contents of SKILL.md into the instructions field.
- Upload the bundled reference files as knowledge so the GPT can consult them.
- Test with one of the example prompts from the skill page and adjust the instructions if your use case differs.
Gemini Packaged
- Download the Gemini package from the skill page.
- For a project, unpack the complete folder into .gemini/skills/ or .agents/skills/. For personal use, use ~/.gemini/skills/ or ~/.agents/skills/.
- Run /skills reload in Gemini CLI, then /skills list to check discovery. There is no need to paste the skill into GEMINI.md.
- Test a matching task and verify the referenced tools and files are available.
Cursor Packaged
- Download the Cursor package from the skill page.
- Unpack the complete skill folder into .cursor/skills/ or .agents/skills/ in your project. For personal local use, ~/.cursor/skills/ and ~/.agents/skills/ are also supported.
- Start a new Cursor session. Type / in Agent chat and select the skill name, or describe a matching task.
- Commit the skill folder and resources for team use. Personal local skills are not automatically available to remote agents or automation runs.
OpenCode Packaged
- Download the OpenCode package from the skill page.
- Unpack the complete folder into .opencode/skills/ in your project, or ~/.config/opencode/skills/ for personal use. OpenCode also supports .agents/skills/ and .claude/skills/ compatibility locations.
- Keep supporting files at their original relative paths. AGENTS.md is separate project-wide guidance and is not generated by this ZIP.
- Start OpenCode in the project and test a matching task with the model and permissions you use.
Permissions & security
Inspect the source, license and declared permissions before use. Read the scripts before running them. Review method
Content Strategy FAQ
What does the Content Strategy skill do?
Turns business goals, customer questions and existing performance into content pillars, buyer-stage topics and a prioritized cluster map. It balances searchable and shareable formats, production capacity and distribution rather than simply listing keywords.
Which AI agents can use Content Strategy?
Packages for Claude, Codex and 4 more are built from the same source instructions.
How do I install Content Strategy in Claude?
Download the Claude package from the skill page. The ZIP contains one folder named after the skill, with SKILL.md and any bundled reference files. For Claude Code, unpack the folder into ~/.claude/skills/ to use it in every project, or into .claude/skills/ inside a repository to share it with your team.
Who made Content Strategy and what is the license?
Content Strategy is published by Corey Haines under the MIT license. The source is https://github.com/coreyhaines31/marketingskills/tree/main/skills/content-strategy. The catalog keeps the original attribution.
What permissions does Content Strategy need?
Declared permissions: read project files, write generated skill files. Risk level: low. Check the scripts in the source before running them.