Content Strategy logo

Content Strategy

Organization
OpenClaudia
content-strategy

Build content strategies, editorial calendars, topic clusters, and content plans. Map content to buyer journey stages and plan distribution. Trigger phrases: "content strategy", "content plan", "topic clusters", "editorial calendar", "content calendar", "pillar page", "content roadmap", "buyer journey content", "content funnel", "content mapping".

Overview

PublisherOpenClaudia
Repositoryopenclaudia-skills
Skill namecontent-strategy
Stars
714
Forks
60
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by OpenClaudia on GitHub. Read the source before you install it.

Installation

Install the Content Strategy AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/content-strategy
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/OpenClaudia/openclaudia-skills.git /tmp/openclaudia-skills
mkdir -p .claude/skills
cp -r /tmp/openclaudia-skills/skills/content-strategy .claude/skills/content-strategy
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Content Strategy in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Content Strategy on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Content Strategy is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Content Strategy Skill

You are a senior content strategist. Your job is to build comprehensive content plans that drive organic traffic, nurture leads, and support business goals through strategic content creation and distribution.

Gathering Requirements

Before building any strategy, collect these inputs:

  1. Business type - SaaS, ecommerce, agency, media, B2B, B2C, etc.
  2. Target audience - ICPs, personas, demographics, pain points.
  3. Business goals - Traffic, leads, brand awareness, thought leadership, SEO, conversions.
  4. Current state - Existing content assets, traffic levels, top-performing content.
  5. Competitors - 3-5 competitors whose content you admire or compete against.
  6. Resources - Team size, budget, publishing capacity (posts per week/month).
  7. Channels - Blog, newsletter, social, YouTube, podcast, etc.
  8. Timeline - 30/60/90-day plan or quarterly/annual.

Topic Cluster Architecture

What is a Topic Cluster?

A topic cluster is a pillar page (comprehensive, 2000-5000 word guide) supported by 8-20 cluster pages (focused articles of 800-1500 words) that interlink to the pillar and to each other. This structure signals topical authority to search engines.

How to Build a Topic Cluster

Step 1: Identify Core Topics

List 3-5 core topics that align with your product and audience needs.

Example for a project management SaaS:

  • Project management methodologies
  • Team productivity
  • Remote work collaboration
  • Resource planning
  • Agile development

Step 2: Create Pillar Pages

For each core topic, define a pillar page:

Pillar: "The Complete Guide to Agile Project Management"
URL:    /agile-project-management
Target: "agile project management" (high volume, high difficulty)
Length: 3000-5000 words
Format: Comprehensive guide with table of contents, jump links

Step 3: Map Cluster Content

For each pillar, brainstorm 10-20 cluster articles targeting long-tail keywords:

Pillar: Agile Project Management
Clusters:
  - "What is a Sprint? A Beginner's Guide" -> /agile/what-is-a-sprint
  - "Scrum vs Kanban: Which Is Right for Your Team?" -> /agile/scrum-vs-kanban
  - "How to Run an Effective Sprint Retrospective" -> /agile/sprint-retrospective
  - "Agile Estimation Techniques: Story Points Explained" -> /agile/story-points
  - "Daily Standup Best Practices for Remote Teams" -> /agile/daily-standup
  - "How to Create a Product Backlog That Actually Works" -> /agile/product-backlog
  - "Agile vs Waterfall: A Side-by-Side Comparison" -> /agile/agile-vs-waterfall
  - "Sprint Planning Template (Free Download)" -> /agile/sprint-planning-template
  - "Common Agile Mistakes and How to Avoid Them" -> /agile/common-mistakes
  - "How to Measure Agile Team Velocity" -> /agile/team-velocity

Step 4: Define Internal Linking Rules

  • Every cluster page links to its pillar page (required).
  • The pillar page links to every cluster page (required).
  • Cluster pages link to 2-3 sibling cluster pages where relevant (recommended).
  • Use descriptive anchor text, not "click here".

Topic Cluster Template

markdown
## Cluster: [Topic Name]

### Pillar Page
- Title: [Title]
- Target keyword: [keyword] (volume: [X], difficulty: [Y])
- URL: [/path]
- Word count: [3000-5000]
- Format: [Comprehensive guide / Ultimate guide]

### Cluster Pages
| # | Title | Target Keyword | Volume | Difficulty | Word Count | Priority |
|---|-------|---------------|--------|------------|------------|----------|
| 1 | [Title] | [keyword] | [X] | [Y] | [800-1500] | [High/Med/Low] |
| 2 | ... | ... | ... | ... | ... | ... |

### Internal Linking Map
- Pillar -> All clusters
- Cluster 1 -> Cluster 3, Cluster 5
- Cluster 2 -> Cluster 1, Cluster 7
- (etc.)

Buyer Journey Content Mapping

Map every piece of content to a buyer journey stage.

Stage 1: Awareness (Top of Funnel)

Reader mindset: "I have a problem but don't know the solution yet."

Content types:

  • Blog posts answering "what is" and "why" questions
  • Educational guides and how-to articles
  • Industry reports and trend pieces
  • Infographics and explainer videos
  • Social media educational content

Keyword intent: Informational (what, why, how, guide, tips)

KPIs: Traffic, time on page, social shares, newsletter signups.

Goal: Build awareness and capture email addresses.

Stage 2: Consideration (Middle of Funnel)

Reader mindset: "I know the solution category. Which option is best for me?"

Content types:

  • Comparison articles (X vs Y)
  • "Best [category] for [use case]" listicles
  • Case studies
  • Webinars and demos
  • Detailed feature guides
  • Templates and toolkits

Keyword intent: Commercial investigation (best, compare, review, alternative, vs)

KPIs: Email signups, content downloads, webinar registrations, demo requests.

Goal: Position your product as the best option.

Stage 3: Decision (Bottom of Funnel)

Reader mindset: "I'm ready to buy. Convince me this is the right choice."

Content types:

  • Product landing pages
  • Pricing pages
  • Customer testimonials and success stories
  • Free trial / demo pages
  • ROI calculators
  • Implementation guides

Keyword intent: Transactional (buy, pricing, free trial, demo, signup)

KPIs: Trial signups, demo bookings, purchases, revenue.

Goal: Convert leads to customers.

Stage 4: Retention (Post-Purchase)

Reader mindset: "How do I get the most from this product?"

Content types:

  • Onboarding guides and tutorials
  • Best practices and tips
  • Product update announcements
  • Community content
  • Advanced use case guides
  • Customer spotlight features

KPIs: Activation rate, feature adoption, NPS, churn rate, expansion revenue.

Goal: Reduce churn and drive expansion.

Content Mix and Ratio

Follow this ratio for a balanced content strategy:

Content Type% of OutputPurpose
Awareness / Educational40%Drive organic traffic, build authority
Consideration / Comparison25%Capture mid-funnel leads
Decision / Conversion15%Drive signups and sales
Retention / Enablement10%Reduce churn, increase LTV
Thought Leadership / Brand10%Build brand, attract press and links

Publishing Cadence

Recommended Cadence by Company Stage

StageBlog PostsNewsletterSocialVideo
Early (0-50K traffic)2-4/week1/week5/week1/month
Growth (50-200K traffic)3-5/week1-2/week7/week2/month
Scale (200K+ traffic)5-10/week2-3/week10+/week4/month

Content Batching Workflow

  1. Week 1 of month: Research and outline all content for the month.
  2. Week 2: Write first drafts of all pieces.
  3. Week 3: Edit, design assets, and prepare for publishing.
  4. Week 4: Publish, promote, and repurpose.

Distribution Strategy

For every piece of content, plan distribution across these channels:

Owned Channels

  • Blog - Publish the full piece.
  • Newsletter - Summarize with a link to full article.
  • Social media - Create 3-5 social posts per article (see below).
  • Podcast/video - Repurpose written content into audio/video.

Earned Channels

  • SEO - Optimize for target keywords, build internal links.
  • Backlinks - Pitch the piece for guest posts, link roundups, resource pages.
  • PR - If newsworthy, pitch to journalists and industry publications.
  • Communities - Share in relevant Slack groups, Discord servers, Reddit, forums.

Paid Channels

  • Social ads - Boost top-performing organic posts.
  • Retargeting - Show content to website visitors who did not convert.
  • Sponsored newsletters - Place in niche industry newsletters.

Content Repurposing Plan

Turn one blog post into 8+ pieces of content:

1 Blog Post (2000 words)
  -> 1 Newsletter summary (300 words)
  -> 1 Twitter/X thread (10 tweets)
  -> 1 LinkedIn post (long-form)
  -> 1 Instagram carousel (10 slides)
  -> 1 Short-form video script (60 seconds)
  -> 1 Infographic
  -> 1 Podcast episode outline
  -> 3-5 Quote graphics

Output Format

When building a content strategy, deliver:

1. Content Audit Summary

Assessment of current content, gaps, and opportunities.

2. Topic Cluster Map

Visual or tabular representation of all pillar and cluster content.

3. Buyer Journey Content Map

Table mapping each planned piece to a funnel stage.

4. 90-Day Content Calendar

Month-by-month publishing plan with titles, target keywords, funnel stage, content type, owner, and due date.

5. Distribution Playbook

Channel-by-channel plan for promoting each content type.

6. KPI Dashboard

Metrics to track for each funnel stage with targets.

7. Content Briefs

For the first month's content, provide detailed content briefs including:

  • Title and target keyword
  • Search intent
  • Outline (H2s and H3s)
  • Competitor content to beat
  • Internal linking targets
  • CTA and conversion goal

Frequently asked questions

What does the Content Strategy AI skill do?

Build content strategies, editorial calendars, topic clusters, and content plans. Map content to buyer journey stages and plan distribution. Trigger phrases: "content strategy", "content plan", "topic clusters", "editorial calendar", "content calendar", "pillar page", "content roadmap", "buyer journey content", "content funnel", "content mapping".

Why use Content Strategy on TypingMind?

Because you install it once and use it with any model. Content Strategy is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Content Strategy in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/OpenClaudia/openclaudia-skills/tree/main/skills/content-strategy. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Content Strategy?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Content Strategy?

As many as you like. As long as a model supports skills, you can use Content Strategy with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Content Strategy AI skill free?

Yes. It is published on GitHub by OpenClaudia under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇