Content Strategy
Builds a content strategy a small team can execute: audience needs backed by counted evidence, an audit of what is already published, a topic map with one page per search intent, a scored backlog, a 90-day calendar sized to real capacity, and the numbers that will show whether it worked. Use when someone asks "what should we write about", "plan our blog", "content strategy", "content plan for next quarter", "topic clusters", "content audit", "our blog traffic is falling", or wants a pile of content ideas turned into a prioritised plan.
Install
npx skills add TerminalSkills/skills --skill content-strategygit clone --depth 1 https://github.com/TerminalSkills/skills.git /tmp/skills
mkdir -p ~/.claude/skills
cp -r /tmp/skills/skills/content-strategy ~/.claude/skills/content-strategyPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Content Strategy ## Overview A content strategy is a set of decisions: who the content is for, which of their needs it will meet, what will not be covered, what gets published first, and how the team will know it worked. The deliverable is one file, `docs/content-strategy.md`, short enough that the people writing the content will read it. Its sections follow the steps below: outcome and audience, needs with their evidence, a decision for each existing URL, the topic map, the scored backlog, the calendar, the measurement plan, and what will not be covered. Two things separate a usable plan from a list of ideas. Every topic traces back to counted evidence that real people need it. And the calendar fits the hours the team actually has. This skill enforces both. ## Instructions ### 1. Gather the inputs Ask for what is missing; read the rest from the project (content folder, sitemap, analytics notes, any positioning document). - **The business outcome** content is meant to move, as one number: trial signups, demo requests, orders, qualified leads. "Traffic" and "awareness" are not outcomes. - **The buyer and the user**, when they differ, and what they are doing instead of using the product today. - **Capacity**: who writes, who reviews for accuracy, hours per week, and which formats are realistic (articles, templates, video, data). - **Raw material nobody else has**: usage data, customer stories, staff expertise, internal tools, photographs, test results.
Details
- Skill name
content-strategy- Repository
- TerminalSkills/skills
- Path
skills/content-strategy/SKILL.md- License
- Apache-2.0
- Repo updated
- 8 November 2026
FAQ
What does the Content Strategy skill do?
Builds a content strategy a small team can execute: audience needs backed by counted evidence, an audit of what is already published, a topic map with one page per search intent, a scored backlog, a 90-day calendar sized to real capacity, and the numbers that will show whether it worked. Use when someone asks "what should we write about", "plan our blog", "content strategy", "content plan for next quarter", "topic clusters", "content audit", "our blog traffic is falling", or wants a pile of content ideas turned into a prioritised plan.
How do I install the Content Strategy skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add TerminalSkills/skills --skill content-strategy. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Content Strategy popular?
It lives in TerminalSkills/skills, which has 213 GitHub stars and 34 forks.
Related skills
3dsmax Rendering
213TerminalSkills/skills
Scripts and configures production rendering in Autodesk 3ds Max with the V-Ray and Corona renderers: output size and files, render elements, denoising, light mix, batch and command-line rendering, and network rendering. Use when a user asks to set up a production render, render several cameras in one batch, render from the command line or on a render farm, add render passes for compositing, or cut render time for archviz and product shots.
3dsmax Scripting
213TerminalSkills/skills
Covers scripting Autodesk 3ds Max, the 3D modeling and rendering application, with MAXScript and Python (pymxs): scene manipulation, object creation, material assignment, camera and light setup, batch operations, and file I/O. Use when tasks involve automating repetitive 3ds Max workflows, batch processing scenes, running scripts headless with 3dsmaxbatch, creating custom tools, or scripting scene setup for archviz, product visualization, or VFX.
3proxy
213TerminalSkills/skills
3proxy is a small open-source proxy server that runs HTTP/HTTPS, SOCKS4/5, SNI and TCP/UDP port-mapping proxies from one config file. Use when a user asks to set up an HTTP or SOCKS5 proxy, add proxy users and passwords, write 3proxy access rules, chain or rotate upstream (parent) proxies, limit bandwidth, connections or monthly traffic per user, run 3proxy in Docker, or fix a 3proxy.cfg that will not start.
Content Writer
213TerminalSkills/skills
Research topics and write content like blog posts, articles, and marketing copy. Use when a user asks to write a blog post, create an article, draft marketing copy, write website content, create a newsletter, produce thought leadership content, or write any long-form or short-form copy.
Constraint Based Creativity
200lyndonkl/claude
Turns limitations into creative fuel by strategically imposing constraints that force novel thinking, break habitual patterns, and reveal unexpected solutions. Covers resource constraints (budget/time/tools), format constraints (length/medium), rule-based constraints, and perspective constraints. Use when brainstorming feels stuck or generates obvious ideas, working with limited resources, designing with specific limitations, or when user mentions "think outside the box", "we're stuck", "same old ideas", "tight constraints", or "limited budget/time".
Contentful
213TerminalSkills/skills
Contentful is an API-first headless CMS: content lives in typed content models and is served through the Content Delivery API (published, CDN), the Content Preview API (drafts) and the Content Management API (writes). Use when a user wants to fetch Contentful entries in a website or app, type them in TypeScript, render rich text, resolve linked entries and assets, preview drafts, write or publish entries from a script, or trigger rebuilds with webhooks.
Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.