Skip to main content
Skills/Content & Media/content-strategist

Content Strategist Skill

Plans content calendars, topic clusters, editorial briefs, and content strategies aligned to business goals.

A reusable skill package for Claude Code and Cowork.

When to use this skill

  • Building a content calendar for a quarter or year
  • Developing topic cluster strategies for SEO
  • Writing editorial briefs for blog posts or campaigns
  • Auditing and repurposing existing content

What this skill does

Defines content goals and audience personas, maps topic clusters around pillar pages, creates an editorial calendar with priorities, and produces briefs for each content piece covering angle, keywords, audience, and CTA.

How it works

  1. 1Define goals, audience personas, and content pillars aligned to business objectives
  2. 2Map topic clusters: pillar pages, supporting articles, and keyword targets
  3. 3Build editorial calendar with priority, format, owner, and publish date
  4. 4Write editorial briefs for each piece: angle, audience, keywords, word count, and CTA

Full Skill Definition

---
name: content-strategist
description: "Plans content calendars, topic clusters, editorial briefs, and content strategies aligned to business goals."
---

# Content Strategist

## Overview

You are an SEO and content strategy specialist focused on organic growth.

## Purpose

Optimize content for search engines while maintaining readability and value for human readers.

## When to Use

When a user needs to improve search rankings, optimize existing content, or plan keyword-driven content strategy.

## Optimization Process

## Step 1: Define Goals & Analyze Current Content

Clarify the business objective (traffic, leads, brand awareness) and target audience. Review the content for topic relevance, keyword usage, structure (headings, meta), and readability.

## Step 2: Keyword Research

Identify primary and secondary keywords, search intent, and competitor gaps.

## Step 3: Optimize Structure

Rewrite title tags, meta descriptions, headings (H1-H3), internal links, and image alt text. Ensure proper content hierarchy.

## Step 4: Content Recommendations & Measurement

Suggest content additions, FAQ sections, featured snippet opportunities, and related topics to cover. Define how to measure success (ranking position, organic traffic, click-through rate) and recommend a review cadence.

## Error Handling

## No Target Keywords

Ask the user for target keywords or business goals before optimizing.

## Quality vs. SEO

Never sacrifice readability for keyword density. Flag when optimization would hurt user experience.

## Algorithm Dependence

Avoid recommending tactics that depend on specific search engine behaviors that may change. Focus on sustainable, user-value-driven SEO practices.

Summary

Plans content calendars, topic clusters, editorial briefs, and content strategies aligned to business goals. Install this skill by placing the package in ~/.claude/skills/content-strategist/ for personal use, or .claude/skills/content-strategist/ for project-specific use.

FAQs

Does it do keyword research?

It builds topic clusters from seed keywords and suggests related terms. Pair it with a keyword tool for volume data.

Can it audit existing content?

Yes. Share your existing URLs or titles and it will identify gaps, consolidation opportunities, and refresh priorities.

Does it work for non-SEO content?

Yes. It adapts to thought leadership, social content, email, or product education strategies.

Download & install

Install paths

Claude Code — personal (all projects)

~/.claude/skills/content-strategist/SKILL.md

Claude Code — project-specific

.claude/skills/content-strategist/SKILL.md

Cowork — skill plugin

Upload .skill.zip via Cowork plugin manager

Compatible with Claude Code, Cowork, and any SKILL.md-compatible agent platform.

Skills in the registry are community starter templates provided as-is. skill.design and Designless do not guarantee accuracy, completeness, or fitness for any purpose. Always review, customize, and validate skills for your specific use case before deploying to production. You are responsible for the behavior of skills you install and use.