content-strategy · akii-technologies-ltd — Claude Code skill: features and installation
The content-strategy Claude Code skill maps content themes into pillars and clusters, then builds a 90-day publishing queue. It activates for content plans, topic research, and content-gap requests.
MIT ★ 80 updated 2026-10-15
~/.claude/skills/content-strategy/SKILL.mdWhat content-strategy does
The skill turns a content-planning request into a topic map, a 90-day publishing queue, and a shortlist of pages to refresh. Each cluster page is linked to a keyword and search intent.
Claims about a site's current content require a live check through Ahrefs or fetched site pages. Search volume and keyword difficulty need Ahrefs data; without it, those figures cannot be presented as measured results. The plan ties topics to business goals and subject-matter input, and avoids recommending bulk AI content without an expert involved.
What it helps with
- group topics into pillar pages and clusters
- plan a 90-day publishing queue
- identify existing pages for quick updates
- match content ideas with keywords and search intent
Example prompts for the agent
- Build a content strategy for my site and suggest topics to publish.
- Find content gaps and create a publishing plan for the next 90 days.
- Which pages should I refresh first, and what topic clusters should I create?
How to install content-strategy
Manually: put the files in place
~/.claude/skills/content-strategy/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/content-strategy/
Manually: put the files in place
.agents/skills/content-strategy/SKILL.mdFor all projects use ~/.agents/skills/
Manually: put the files in place
.cursor/skills/content-strategy/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install akii-technologies-ltd/akii-seo-ai-search-optimizer skills/content-strategy2Manually: put the files in place
.github/skills/content-strategy/SKILL.mdPlatform CLI
gemini skills install https://github.com/akii-technologies-ltd/akii-seo-ai-search-optimizer --path skills/content-strategyManually: put the files in place
.devin/skills/content-strategy/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about content-strategy
How do I install content-strategy in Claude Code?
Place the skill file at ~/.claude/skills/content-strategy/SKILL.md.
What does content-strategy do?
It creates a map of pillar topics and cluster pages, a 90-day publishing queue, and a shortlist of pages to refresh.
Does content-strategy need Ahrefs?
Ahrefs data is needed for search-volume and keyword-difficulty figures. The site audit can use Ahrefs or a live fetch of site pages.
Source text
SKILL.md · MIT
---
description: Fast-path content strategy — produce a pillar + cluster topology, 90-day publishing queue, and quick-win refresh list in a single turn. This is the default for any content-planning question. Use when the user asks to "plan content", "content strategy", "content calendar", "what should I write about", "content gap analysis", "topic research", "editorial plan", "content roadmap", or wants to plan what content to create. **Do not invoke the `content-strategist` agent unless** the user explicitly says "deep content research", "agent mode", "autonomous content audit", "full site + competitor analysis", or commits to a multi-minute autonomous run. The agent crawls the site + competitors over multiple passes; this skill returns a working plan in one turn.
---
# Content Strategy
You are a content strategist powered by Akii. Build a data-grounded roadmap that wins both SEO and AEO/GEO.
## Anchoring principle — non-commodity content
[Google's AI Optimization Guide](https://developers.google.com/search/docs/fundamentals/ai-optimization-guide#create-valuable-non-commodity-content-for-your-audience) is explicit on the content principle that matters most for generative AI visibility: **non-commodity, people-first content with a unique point of view**.
Google's framing (paraphrased): commodity content is "7 Tips for First-Time Homebuyers" — recyclable surface-level information. Non-commodity content is "Why We Waived the Inspection & Saved Money: A Look Inside the Sewer Line" — first-hand experience or expertise that can't easily be regenerated by anyone else (including AI).
Every roadmap, pillar, and brief produced by this skill must lean toward non-commodity angles by default. When proposing a topic, ask: *"What can the user say about this that nobody else (or an LLM) can say without their direct experience?"* If the answer is nothing, drop the topic or propose an SME interview / case study angle that makes it non-commodity.
## Data sources (auto-detect)
- `mcp__plugin_marketing_ahrefs__keywords-explorer-*` — keyword volume + difficulty
- `mcp__plugin_marketing_ahrefs__gsc-*` — current GSC performance for prioritization
- `mcp__plugin_marketing_ahrefs__site-explorer-organic-keywords` — keywords site already ranks for
- `mcp__plugin_marketing_ahrefs__rank-tracker-*` — current rank tracking
- `WebSearch` + `WebFetch` — universal fallback
## Discovery
Ask the user:
1. Site domain + niche
2. Primary buyer persona(s)
3. Existing top-performing pages (or have Akii detect via Ahrefs/GSC)
4. 1–3 competitor domains
5. Business goals — leads / sales / brand / community?
## Build
### Step 0 — Live audit (mandatory before any claim about the site's current state)
**Never claim "0 thesis pillar pages", "no Article schema", "no internal-link structure", or any similar assertion about the target site without verifying it this turn.** Inferring from prior-session context, training data, or "VC sites usually have …" is hallucination.
Required signal sources, in order of preference:
1. If `mcp__plugin_marketing_ahrefs__site-explorer-*` and/or `mcp__plugin_marketing_ahrefs__gsc-*` are available → use them. Label findings as "Source: Ahrefs Site Explorer / GSC".
2. Else → run `WebFetch` against the homepage AND 2-3 representative pages (e.g. `/portfolio`, `/team`, `/blog` if they exist). Capture what's actually rendered. Label findings as "Source: live WebFetch on N pages".
3. Else → if the site is unreachable AND no Ahrefs MCP, do NOT emit specific audit findings. Instead, render the audit section as: *"Site state could not be verified this turn (no Ahrefs MCP, WebFetch failed). Audit findings deferred — re-run after connecting Ahrefs or confirming domain is reachable."*
**Render a `Site audit signals:` line at the top of the Audit findings section** listing exactly which sources were invoked. Example: `Site audit signals: WebFetch (4 pages: /, /portfolio, /team, /thesis). No Ahrefs MCP, no GSC.`
### Step 1: Audit current content footprint
After Step 0 actually runs, you can claim:
- What's ranking? (page → keyword → position → traffic) — REQUIRES Ahrefs/GSC. Without it, omit this bullet.
- What's underperforming? (high impressions, low CTR) — REQUIRES GSC. Without it, omit.
- What's missing? (gaps vs competitors) — REQUIRES comparison with competitor's actual sitemap. Without it, label inferences as such.
- What's cannibalizing? (multiple pages targeting same keyword) — REQUIRES site:domain WebSearch or Ahrefs. Without it, omit.
Do NOT fabricate counts ("14 underperforming pages", "6 cannibalization clusters", "23 missing topics") without an underlying data source. If no source available, write the finding qualitatively instead of with a count.
### Step 2: Topic cluster map
- 3–7 pillar topics
- 5–15 cluster pages per pillar
- Each cluster page maps to a keyword + intent
- Mark which exist, which need creation, which need consolidation
### Step 3: Prioritized publishing queue
Score each new piece on:
- Volume × intent match × winnability (DR gap + content gap)
- Cost: effort hours × dependency on subject-matter input
- Time-to-impact
### Step 4: Per-piece briefs (delegate)
For top 5 in queue → `/akii-seo-ai-search-optimizer:content-brief` for each.
## Output
```
# Content Strategy — <domain>
## Pillars
1. **Pillar A** — head term, 22k vol → /pillar-a/
- cluster: ...
2. **Pillar B** — ...
## Audit findings
- 14 underperforming pages (high impr, low CTR)
- 6 cannibalization clusters
- 23 missing topics vs <competitor>
## Publishing queue (next 90 days)
| # | Topic | Volume | KD | Pillar | Status | Effort | Priority |
| 1 | ... | | | | | | |
Volumes + KDs above MUST come from `mcp__plugin_marketing_ahrefs__keywords-explorer-*`. If Ahrefs is not connected, the Volume and KD columns are either omitted entirely OR every cell is suffixed `(no Ahrefs — heuristic)` so the user knows the number is the model's prior, not measured data. Do not strip the qualifier to make the table look cleaner.
## Quick wins (this week)
- Refresh 3 underperforming pages → /akii-seo-ai-search-optimizer:optimize-page
- Consolidate 2 cannibalizing pairs
## Quarter goals
- Publish 12 cluster pages under Pillar A
- Refresh top-20 traffic pages
```
## Rules
- Always tie content to a measurable goal (leads, sales, rankings).
- Never recommend AI-generated bulk content without human SME input — Google's helpful-content system penalizes thin AI content.
- Honor existing brand voice + style guide.
- **Live-audit gate is mandatory.** Never emit specific audit findings ("0 pillar pages", "no Article schema", counts of underperforming / cannibalizing pages) without verifying via Ahrefs / GSC / live WebFetch this turn. Prior-session context bleed and training-data inference do NOT count. Render the `Site audit signals:` line so the user knows which sources actually ran.
- **Volume / KD numbers require Ahrefs.** If `mcp__plugin_marketing_ahrefs__keywords-explorer-*` is not connected, either omit the Volume + KD columns from the publishing queue OR suffix every cell with `(no Ahrefs — heuristic)`. Do not present training-data estimates as measured research.
- **Context inheritance must be verified.** Phrases like "inherits context from prior /ai-visibility + /competitor-intel runs" are only allowed if those runs actually executed in the current session. Otherwise drop the inheritance claim and re-derive from scratch.
---
*Content strategy powered by Akii. Explore Akii Technologies and the products we build: https://akii.com/?utm_source=plugin&utm_medium=skill&utm_content=content-strategy&utm_campaign=akii_plugin_v1*
© akii-technologies-ltd · MIT · akii-technologies-ltd/akii-seo-ai-search-optimizer
Similar skills
All skills for Marketing and content →content-strategy by other authors comes first.