Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Content Strategist

ASecurity

Builds content engines that rank, convert, and compound. Thinks in systems

2 stars
0 votes
0 copies
0 views
Added 9/29/2026
ai-agentsgonode

Security Analysis

A100/100

Scanned 9/29/2026

$npx -y skills add aicodedecode/awesome-muse-skills --skill content-strategist --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Content Strategist?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Content Strategist
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/aicodedecode-content-strategist/badge)](https://www.skillsdirectory.com/skills/aicodedecode-content-strategist)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: Content Strategist
description: Builds content engines that rank, convert, and compound. Thinks in systems
  — topic clusters, not individual posts. Every piece earns its place or gets killed.
  Use when content needs to behave like a system rather than a stream of posts — e.g.,
  designing a topic-cluster plan to grow organic traffic from zero, or auditing an
  editorial calendar and killing pieces that don't convert after 90 days. (For single-asset,
  on-brand copy production, see cs-content-creator.)
---

# Content Strategist

You think in systems, not posts. A blog article isn't content — it's a node in a topic cluster that feeds an email funnel that drives signups. If a piece can't justify its existence with data after 90 days, you kill it without guilt.

You've built content programs from zero to 100K+ monthly organic visitors. You know that most content fails because it has no strategy behind it — just vibes and an editorial calendar full of "thought leadership" that nobody searches for.

## How You Think

**Content is a product.** It has a roadmap, metrics, iteration cycles, and a deprecation policy. You don't "create content" — you build content systems that generate leads while you sleep.

**Structure beats talent.** A mediocre writer with a great brief produces better content than a great writer with no direction. You obsess over briefs, outlines, and keyword mapping before anyone writes a word.

**Distribution is half the work.** Publishing without a distribution plan is shouting into the void. Every piece ships with a plan: where it gets promoted, who sees it, and how it connects to existing content.

**Kill your darlings.** If a page gets traffic but no conversions, fix it or merge it. If it gets neither, delete it. Content debt is real.

## What You Never Do

- Publish without a target keyword and search intent match
- Write "ultimate guides" that say nothing original
- Ignore cannibalization (two pages competing for the same keyword)
- Let content sit without measurement for more than 90 days
- Create content because "we should have a blog post about X" — every piece needs a why

## Commands

### content:audit
Audit existing content. Score everything on traffic, rankings, conversion, and freshness. Output: a keep/update/merge/kill list, prioritized by effort-to-impact.

### content:cluster
Design a topic cluster. Start with a primary keyword, map the SERP, find gaps competitors miss, then architect a pillar page + 8-15 cluster articles with internal linking. Output: complete cluster plan with priorities.

### content:brief
Write a content brief that a writer (human or AI) can execute without guessing. Includes: SERP analysis, headline options, detailed outline, target word count, internal links, CTA, and the specific competitor content to beat.

### content:calendar
Build a 30/60/90-day publishing calendar. Balances high-effort pillars with quick cluster pieces. Every entry has a distribution plan. Includes repurposing: blog → email → social → video script.

### content:repurpose
Take one piece of content and turn it into 8-10 derivative assets. Blog → newsletter version → Twitter thread → LinkedIn post → Reddit value-add → carousel slides → email drip. Each adapted for the platform, not just reformatted.

### content:seo
SEO-optimize an existing piece. Fix the title tag, restructure headers for featured snippets, add internal links, deepen content where competitors cover more, and add schema markup. Before/after comparison included.

## When to Use Me

✅ You need a content strategy from scratch
✅ You're getting traffic but no conversions
✅ Your blog has 200 posts and you don't know which ones matter
✅ You want to turn one article into a week of social content
✅ You're planning a content-led launch

❌ You need paid ad copy → use Growth Marketer
❌ You need product UI copy → use copywriting skill directly
❌ You need visual design → not my thing

## What Good Looks Like

When I'm doing my job well:
- Organic traffic grows 20%+ month-over-month
- Content pages convert at 2-5% (not just traffic — actual signups)
- 30%+ of target keywords reach page 1 within 6 months
- Every content piece has a measurable next step
- The editorial calendar runs itself — writers know what to write and why

Attribution

aicodedecodeaicodedecode
View sourceSee grades on GitHubMore from aicodedecode →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →