borghei/content-strategy
> funnel mapping, and content audits. Use when deciding what content to create, building a content calendar, planning topic clusters, or finding content gaps.
npx skills add https://github.com/borghei/Claude-Skills --skill content-strategy
Strategic content planning that drives traffic, builds authority, and generates leads by being either searchable, shareable, or both.
content strategy, content planning, content pillars, topic clusters, content calendar, audience research, content audit, funnel mapping, content gaps, editorial planning, blog strategy, content ideas, topic ideation, SEO content strategy, content roadmap, content marketing strategy, content performance, keyword research, buyer journey content, search intent mapping
Before building the strategy, confirm these inputs. If any is unknown or vague, ASK — do not assume:
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Step 1: Business Context Gathering
Before planning content, understand the business foundation:
## Strategy Context
- Business goal for content: [Traffic / Leads / Brand awareness / Thought leadership]
- Product/service: [What you sell and to whom]
- Ideal customer profile: [Industry, company size, role, seniority]
- Sales cycle: [Self-serve / Sales-assisted / Enterprise]
- Current content state: [Starting fresh / Some content / Mature library]
- Resources: [Writers, budget, publishing capacity per week/month]
- Competitors producing content: [Top 3-5 competitor blogs]
Step 2: Customer Research for Content
Mine these sources for content topics:
| Source | What to Extract | How to Use |
|--------|----------------|-----------|
| Sales call recordings | Questions prospects ask before buying | Create content answering each question |
| Support tickets | Recurring problems and confusion | Tutorial and troubleshooting content |
| Customer interviews | Language they use to describe problems | Use their exact words in headlines and copy |
| Product reviews (yours + competitors) | Praise and complaints | Content addressing concerns, amplifying strengths |
| Community forums (Reddit, Slack, Discord) | Questions, debates, misconceptions | Topic ideas with proven demand |
| Search console queries | What people search to find you | Optimize for highest-potential queries |
Step 3: Define Content Pillars
Pillars are the 3-5 broad topic areas your content focuses on. Each pillar should:
Step 4: Build Topic Clusters
For each pillar, develop a cluster of 10-25 topics:
## Pillar: [Topic Area]
Pillar page: [Comprehensive guide serving as the hub]
### Supporting Topics
1. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
2. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
3. [Topic] — KW: [keyword], Vol: [X], Diff: [X], Intent: [Info/Commercial]
...
### Internal Linking Plan
- All supporting topics link to pillar page
- Pillar page links to all supporting topics
- Related supporting topics cross-link to each other
Step 5: Prioritize Topics
Score each topic on a priority matrix:
| Factor | Weight | Scoring |
|--------|--------|---------|
| Search volume | 25% | High (3), Medium (2), Low (1) |
| Keyword difficulty | 20% | Easy (3), Medium (2), Hard (1) |
| Business relevance | 30% | Direct product connection (3), Adjacent (2), Tangential (1) |
| Competitive gap | 15% | No good content exists (3), Beatable content (2), Strong competitors (1) |
| Content asset value | 10% | Evergreen + repurposable (3), Seasonal (2), One-time (1) |
Priority score = weighted sum. Execute highest scores first.
Step 1: Inventory All Content
Build a content inventory spreadsheet:
| URL | Title | Pillar | Format | Publish Date | Last Updated | Monthly Traffic | Avg Time on Page | Conversions | Target Keyword | Ranking Position |
|-----|-------|--------|--------|-------------|-------------|----------------|-----------------|-------------|---------------|-----------------|
Step 2: Classify Each Piece
For each piece, determine:
Step 3: Score Performance
| Score | Traffic | Engagement | Conversion | Action |
|-------|---------|-----------|------------|--------|
| A (top 20%) | High traffic | Above avg time on page | Drives conversions | Protect, repurpose, update regularly |
| B (middle 40%) | Moderate | Average engagement | Some conversions | Optimize, improve, interlink |
| C (next 30%) | Low | Below average | Minimal | Update or consolidate |
| D (bottom 10%) | Near zero | High bounce | None | Redirect, remove, or completely rewrite |
Step 4: Build Remediation Plan
| Action | When | How |
|--------|------|-----|
| Update | Content is B or C tier with good topic but outdated info | Refresh data, add new sections, update publish date |
| Consolidate | Multiple thin pieces on same topic | Merge into one comprehensive piece, redirect old URLs |
| Remove | Content is irrelevant, duplicate, or unfixable | 301 redirect to most relevant remaining page |
| Create new | Gap exists in pillar coverage | Add to editorial calendar with priority score |
| Optimize | Content ranks #4-20 for target keyword | On-page SEO improvements, better intro, internal links |
Example Pillar Structure for a SaaS Product:
| Pillar | Business Connection | Audience Need | Content Types |
|--------|-------------------|--------------|---------------|
| [Core problem you solve] | Direct product relevance | Actively searching for solutions | How-to guides, tutorials, comparisons |
| [Industry your audience works in] | Thought leadership | Staying current on trends | Analysis, predictions, benchmarks |
| [Adjacent skill your audience needs] | Trust building | Professional development | Frameworks, templates, playbooks |
| [Use case deep dives] | Product education | Understanding applications | Case studies, walkthroughs, examples |
Each pillar should have a comprehensive hub page (2,000-4,000 words) that:
| Method | Time Required | Quality | Best For |
|--------|-------------|---------|----------|
| Customer interview analysis | 2-4 hours | Highest | Understanding language, pain points, objections |
| Sales call review | 1-2 hours | High | Identifying pre-purchase questions |
| Support ticket mining | 1-2 hours | High | Finding confusion points and tutorial needs |
| Competitor comment analysis | 1 hour | Medium | Discovering unmet content needs |
| Community forum research | 1-2 hours | Medium | Finding real questions and debates |
| Search console analysis | 30 min | Medium | Understanding what queries already reach you |
| Keyword research tools | 1-2 hours | Medium | Quantifying demand for topics |
The most valuable output of audience research is exact language:
| Customer Says | Content Opportunity |
|--------------|-------------------|
| "I wish I knew..." | Educational content using their exact framing |
| "The hardest part is..." | Tutorial content addressing that specific difficulty |
| "I always forget to..." | Checklist or template content |
| "Everyone says to do X, but..." | Contrarian or nuanced content |
| "Is it worth it to..." | ROI analysis or comparison content |
| "What's the difference between..." | Comparison or explainer content |
| Stage | Reader Mindset | Content Goal | Content Types | Metrics |
|-------|---------------|-------------|---------------|---------|
| Awareness | "I have a problem" | Attract and educate | Blog posts, videos, infographics, social content | Traffic, impressions, shares |
| Consideration | "What are my options?" | Build trust and differentiate | Comparisons, case studies, guides, webinars | Time on page, email signups, return visits |
| Decision | "Is this the right solution?" | Convert | Product pages, demos, free trials, ROI calculators | Signups, trials, demo requests, purchases |
For each content pillar, ensure coverage across all funnel stages:
## Pillar: [Topic]
### Awareness Topics (attract new visitors)
- [Topic targeting broad informational keyword]
- [Topic answering common beginner question]
- [Topic providing industry data or benchmark]
### Consideration Topics (build trust and preference)
- [Topic comparing approaches or solutions]
- [Topic showing how to evaluate options]
- [Case study demonstrating results]
### Decision Topics (drive conversion)
- [Product-specific tutorial or walkthrough]
- [ROI calculator or assessment tool]
- [FAQ addressing buying objections]
| Dimension | Searchable Content | Shareable Content |
|-----------|-------------------|-------------------|
| Discovery | People search for it (keyword-driven) | People share it (social-driven) |
| Lifespan | Evergreen (months to years) | Timely (days to weeks) |
| Examples | "How to set up GA4 tracking" | "The state of marketing in 2026" |
| Traffic pattern | Steady, compounding | Spike, then decline |
| Optimization | SEO-first | Hook and emotion-first |
| Measurement | Organic traffic, rankings | Shares, engagement, referral traffic |
Most content strategies should be:
| Content Type | Searchable | Shareable | Both |
|-------------|-----------|-----------|------|
| How-to guides | High | Low | — |
| Original research | Medium | High | Yes |
| Comparisons | High | Medium | Yes |
| Thought leadership | Low | High | — |
| Templates/tools | High | Medium | Yes |
| Case studies | Medium | Medium | Yes |
| Industry news takes | Low | High | — |
| Tutorials | High | Low | — |
| Frameworks/playbooks | Medium | High | Yes |
For each top competitor:
## Competitor: [Name]
### Content Inventory
- Blog frequency: [Posts per week/month]
- Content types: [Formats they use]
- Average word count: [Length]
- Primary topics: [Their content pillars]
### Strengths
- [What they do well]
- [Topics where they dominate]
### Gaps
- [Topics they don't cover]
- [Angles they miss]
- [Outdated content that could be beaten]
### Opportunity
- [Where you can win with better content]
- [Underserved topics in their coverage]
| Topic | Competitor A | Competitor B | Competitor C | Your Coverage | Gap Score |
|-------|-------------|-------------|-------------|---------------|-----------|
| [Topic 1] | Strong | None | Weak | None | High opportunity |
| [Topic 2] | Strong | Strong | Strong | Weak | Improve existing |
| [Topic 3] | None | None | None | None | Blue ocean opportunity |
10. Measure quarterly — Content strategy is a 6-12 month investment. Monthly reviews for tactics, quarterly reviews for strategy adjustments.
| Problem | Likely Cause | Fix |
|---------|-------------|-----|
| Content published consistently but no organic traffic growth | Topics selected without keyword research or targeting zero-volume queries | Re-prioritize using search volume x business relevance x competitive gap scoring matrix |
| All content is awareness-stage, no leads generated | Over-indexing on top-of-funnel content without consideration/decision stage pieces | Audit funnel coverage per pillar; create 2-3 consideration and decision pieces per pillar |
| Topic cannibalization across content pieces | Multiple articles targeting the same keyword without differentiation | Map one primary keyword per page; consolidate competing pieces or differentiate angles |
| Content calendar frequently disrupted | Production timelines too tight or no buffer for reviews and revisions | Add 3-day buffer per piece; batch brief creation 4-6 pieces at a time |
| Competitor consistently outranks on shared topics | Competitor has stronger E-E-A-T signals or deeper content coverage | Analyze competitor content depth; add original data, expert quotes, and experience signals |
| Content audit reveals 70%+ of library is underperforming | Strategy was never defined — content was reactive, not planned | Start with 3 content pillars, build 10-15 cluster topics per pillar, then produce systematically |
In scope:
Out of scope:
Known limitations:
# Generate a content calendar plan from topic list
python scripts/content_calendar_planner.py --topics topics.csv --cadence weekly --json
# Analyze headlines for click-worthiness and SEO
python scripts/headline_analyzer.py --headlines headlines.txt --json
# Score content brief completeness
python scripts/content_brief_generator.py --keyword "cloud cost optimization" --json
Take borghei/content-strategy from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.