The first article in this series covered seven Claude Code skills for content creation and workflow: research briefs, editorial pipelines, SEO packaging, cross-channel repurposing, multi-property orchestration, voice consistency auditing, and research-to-brief synthesis. Those skills handle the “how to make content” side of operations.
This article covers the other half: strategy and optimization. The skills that answer “what should we make?” and “is what we already made still working?” These are the higher-leverage skills that don’t just save time—they change how you make content decisions.
If the first set of skills automates the production line, this set builds the control tower. Let’s look at each one.
Content teams make editorial decisions based on intuition, recent anecdotes, or whatever the CEO read in a newsletter last Tuesday. The Content Performance Forecaster replaces that with pattern recognition across your own performance history.
This skill analyzes historical content performance—GA4 traffic data, social engagement metrics, email CTRs, conversion events—and identifies the patterns that actually predict whether a piece of content will perform. Not generic “list posts do well” platitudes. Your audience’s specific behavior, in your specific categories, on your specific channels.
What the Skill Looks For
The forecaster doesn’t just look at which articles got the most pageviews. That’s a vanity metric masquerading as intelligence. It analyzes:
Format-to-performance mapping. Do your how-to guides outperform your list posts? Do case studies generate more conversions than trend pieces? The skill correlates content format with your actual success metrics, not industry averages.
Topic velocity patterns. Some topics produce steady, long-tail traffic for years. Others spike for three days and die. The forecaster identifies which clusters produce compounding returns and which ones are sprints with no endurance.
Channel-specific performance. A topic that bombs on your blog might be a newsletter home run. The forecaster breaks down performance by distribution channel so you can match topics to the right medium, not just the right calendar slot.
Angle effectiveness. Two articles on the same topic can perform 10x apart based on the angle. Contrarian takes, data-backed analysis, practitioner case studies, vendor comparison—the forecaster scores which angle types consistently win in each of your topic clusters.
Skill Architecture
---
description: Analyzes historical content performance and predicts which topics, formats, and angles will perform best. Use during editorial planning and before committing to major content investments.
tools: [Read, Write, WebFetch, WebSearch]
---
## Data Sources
- GA4 export: /data/analytics/ga4-content-export.csv
- Social engagement: /data/social/linkedin-post-performance.json
- Email performance: /data/email/newsletter-ctr-history.json
- Conversion data: /data/crm/content-attribution.csv
## Analysis Protocol
1. Load all data sources. Validate date ranges (minimum 90 days).
2. Group content by: format, topic cluster, angle type, channel.
3. Calculate performance scores per group:
- Traffic score: (pageviews × avg time on page) / bounce rate
- Engagement score: (social shares + comments) / impressions
- Conversion score: attributed conversions / pageviews
- Composite: weighted average based on team priorities
4. Identify top decile performers in each group.
5. Extract common characteristics from top performers.
6. Score upcoming content ideas against pattern library.
7. Output: ranked content recommendations with confidence scores.
## Prediction Output Format
For each recommended piece, output:
- Topic + Angle + Format combination
- Predicted performance range (low/medium/high)
- Confidence score (0-100%)
- Basis: which historical patterns support the prediction
- Risk factor: what could make this underperform
## Guardrails
- Never predict without >= 90 days of data.
- Flag predictions with confidence < 60% as speculative.
- Always note when a recommended angle contradicts a prior pattern.
- Update pattern library after every content batch publish.How to Use Predictions Without Over-Relying on Them
The trap with any forecasting tool is treating predictions as commands instead of inputs. The forecaster tells you “how-to guides about API integrations tend to outperform list posts about the same topic by 3.2x based on the last 90 days.” That’s useful. It doesn’t tell you “write this specific article.”
Practical application: use the forecaster to narrow your editorial options from 50 ideas to 10, then use editorial judgment to pick the 3 that align with your strategy, resources, and timing. The forecaster eliminates the bottom 80% of ideas with data. You eliminate the remaining 12 based on what only you know: upcoming product launches, partnerships, market shifts, team capacity.
The forecaster’s real value isn’t that it picks winners. It’s that it kills losers before you invest six hours writing them.
Most competitive content analysis looks like this: open a competitor’s blog, skim their last five posts, feel vaguely inadequate, and move on with your day. That’s not analysis. That’s anxiety scrolling.
The Competitive Content Gap Analyzer does something different. It systematically monitors what your competitors publish, categorizes their coverage, and identifies the topics they’re not writing about. The goal isn’t to copy what’s working for them. It’s to own the conversations they’re ignoring.
Competitor Selection Criteria
You don’t need to monitor 20 competitors. You need the right 5–7. The skill uses three selection filters:
Direct competitors solve the same problem for the same audience. If you sell content operations software, monitor other content operations companies. Obvious but necessary.
Audience competitors compete for the same reader attention even if they sell something different. A content strategy consultant should monitor CMI, Animalz, and Ahrefs’ blog—not because they compete on product, but because they compete for the same Google real estate and newsletter subscriptions.
Adjacent authorities cover topics one degree removed from your space. They signal where your audience’s interests are drifting. If analytics tools start publishing about AI content governance, that’s a signal your audience cares about it too.
Automated Monitoring Approach
The skill works by ingesting competitor content through multiple feeds:
Sitemap polling. Most sites expose an XML sitemap at /sitemap.xml or /post-sitemap.xml. The skill parses these weekly, diffs against the previous pull, and surfaces new URLs. No logins required, no API keys needed.
RSS feeds. When available, RSS provides cleaner data than sitemap parsing—it includes publish dates, categories, and author information natively. The skill checks RSS first, falls back to sitemaps when RSS isn’t available.
Manual URL lists. For competitors without sitemaps or RSS (looking at you, Substack-only newsletters), maintain a simple URL list that the skill fetches and diff-checks periodically.
Each new piece of competitor content gets: extracted full text, categorized by topic cluster, tagged by content format and angle type, and scored for depth (word count, data points, original research vs. opinion).
Gap Scoring Methodology
Not all content gaps are worth filling. The skill scores each identified gap on three dimensions:
Audience demand (0–10). Is there search volume? Social conversation? Questions in forums and communities? A gap nobody is searching for is a gap nobody will read.
Strategic fit (0–10). Does this topic connect to your product, service, or unique expertise? A high-demand gap that has nothing to do with what you sell is a distraction, not an opportunity.
Competitive density (0–10, inverted). How many competitors already cover this? Zero coverage = 10. Saturated market = 1. The best gaps are the ones with real demand but thin coverage.
The composite gap score is simply the product: Demand × Strategic Fit × Density / 100. The result is a 0–10 score where anything above 6 is a priority gap, above 4 is worth pursuing, and below 4 is noise.
Skill Architecture
---
description: Monitors competitor content publishing and identifies topic gaps where you can own the conversation. Use during editorial planning and content strategy reviews.
tools: [Read, Write, WebFetch, Glob]
---
## Competitor Registry
File: /data/competitive/competitor-registry.json
Structure: {name, type (direct|audience|adjacent), sitemapUrl, rssUrl, manualUrls[], lastScanned}
## Monitoring Protocol
1. For each competitor, fetch RSS feed (primary) or sitemap (fallback).
2. Diff new URLs against last scan index.
3. For each new URL: fetch full text, extract title + headings, categorize by topic cluster.
4. Append to competitor coverage map: /data/competitive/coverage-map.json
## Gap Identification Protocol
1. Load your content inventory by topic cluster.
2. Load competitor coverage maps.
3. For each topic cluster:
a. Count your coverage: articles, depth score, recency.
b. Count competitor coverage: total articles across all monitored competitors.
c. Identify sub-topics with competitor coverage < 2 articles.
d. Flag as candidate gap.
4. Score each candidate gap: Demand × Strategic Fit × Density / 100.
5. Sort by composite score descending.
6. Output: prioritized gap list with scores and rationale.
## Gap-to-Brief Conversion
For each priority gap (score >= 6):
- Generate a 1-paragraph article angle.
- List 3 potential data sources to research.
- Suggest the optimal content format based on audience demand patterns.
- Flag if this gap connects to an existing piece you own (cross-link opportunity).The gap analyzer pairs naturally with the content operations engine covered in our earlier architecture piece. Once the analyzer identifies a priority gap, the operations engine can take the resulting brief and run it through the full production pipeline: research, draft, edit, optimize, publish. End to end, the cycle from “nobody is writing about this” to “we own this topic” can close in under 72 hours with the right skill chain.
Here’s a stat that should make every content marketer uncomfortable: HubSpot found that 76% of their monthly blog views came from posts published more than six months ago. Old content drives the majority of results. But old content also decays. Stats become outdated. Examples lose relevance. Internal links break. Google slowly pushes stale pages down the rankings.
The Automated Content Refresh Scheduler is a skill that audits your existing content inventory, scores every post on freshness, performance, and SEO health, and produces a prioritized refresh queue with specific optimization instructions per post. It turns the annual content audit from a month-long spreadsheet slog into a weekly automated checkpoint.
Freshness Scoring Formula
The skill scores each piece of content on a composite freshness index. The formula weighs four factors:
Age decay (25%). Posts older than 12 months start losing points. Posts older than 24 months lose points faster. The decay isn’t linear—content that drives consistent traffic ages slower than content that doesn’t.
Performance trajectory (35%). Is traffic trending up, stable, or declining? The slope matters more than the absolute number. A post with 500 monthly visits that gained 20% month-over-month is healthier than a post with 2,000 visits that lost 15%.
SEO health (25%). Keyword rankings, click-through rate from SERPs, internal link count, backlink count, and mobile usability. These are structural signals that degrade over time as your site architecture changes and external links disappear.
Content accuracy risk (15%). Does the post reference specific years, product versions, pricing, or tool features that likely changed? The skill scans for date references, version numbers, dollar amounts, and tool names to flag high-risk content before a human even looks at it.
Update, Rewrite, or Retire?
The skill doesn’t just score—it triages into three action buckets:
Refresh (score ≥ 70). The post is fundamentally solid but needs tactical updates: replace outdated stats, add 1–2 new sections reflecting current developments, check and update all internal links, and republish with a new date. This is a 30–60 minute operation per post.
Rewrite (score 40–69). The topic is worth covering but the execution isn’t competitive anymore. The structure needs reworking, the depth needs increasing, or the angle needs shifting. This is a 2–4 hour operation. Treat it like a new article that happens to have research and an existing URL.
Retire (score < 40). The post has no meaningful traffic, no backlinks, and covers a topic that no longer matters. Redirect the URL to a relevant live page, or if no good redirect target exists, let it 410 (Gone). Keeping dead content live dilutes your site quality signals.
Skill Architecture
---
description: Audits content inventory, scores posts on freshness/performance/SEO health, and produces a prioritized refresh queue with optimization instructions. Use periodically (weekly recommended) to maintain content quality at scale.
tools: [Read, Write, WebFetch, Glob]
---
## Content Inventory
File: /data/content/inventory.json
Structure: {slug, title, publishDate, lastUpdated, category, url, wordCount}
## Data Sources
- GA4 traffic data: /data/analytics/ga4-page-performance.csv
- GSC data: /data/analytics/gsc-page-data.csv
- Internal link map: /data/content/internal-link-graph.json
## Scoring Algorithm
For each post in inventory:
1. Age Decay (0-25): score = 25 - (months_since_publish × 1.0), clamped at 0.
Traffic multiplier: if monthly_traffic > 500, reduce decay by 40%.
2. Performance Trajectory (0-35): calculate 90-day traffic slope.
Positive slope: score = 30 + (growth_pct × 5), capped at 35.
Negative slope: score = 30 - (decline_pct × 3), floor at 0.
3. SEO Health (0-25): keyword positions + CTR + internal links + backlinks.
4 factors, each 0-6.25. Sum for total.
4. Accuracy Risk (0-15): scan for dates, versions, prices, tool names.
Each outdated reference: -3 points from maximum 15.
5. Composite: sum of all four scores. Range: 0-100.
## Triage Rules
- Score >= 70: REFRESH — tactical updates, republish.
- Score 40-69: REWRITE — structural overhaul, treat as new.
- Score < 40: RETIRE — redirect or archive.
## Output Format
Prioritized queue with:
- Rank, Score, Post Title, URL, Action, Specific Instructions
- Instructions include: which stats to update, which sections to add,
which internal links to check, suggested new angle (for rewrites)Automating the Periodic Audit
The skill is designed to run on a schedule. Point it at your content inventory once a week, and it produces a ranked refresh queue without human intervention. The output lands in your editorial planning system—whether that’s a Notion database, a ClickUp list, or a spreadsheet you review in Monday standup.
For teams managing 100+ pieces of content, this is the difference between “we should really do a content audit someday” and “here’s the three posts to refresh this week.” Most content audits fail not because the methodology is wrong, but because the scope is overwhelming. Breaking it into weekly, automated, bite-sized recommendations makes refresh a habit instead of an annual panic attack.
For a manual approach to content auditing that complements this automated skill, see our 5-Point Content Audit framework—it covers the strategic decision-making layer that sits above the automated scoring.
Individually, each skill addresses a single pain point. Together, they form a strategic operations layer that closes the content decision loop:
The Forecaster tells you what to write next, based on what worked before. It narrows 50 content ideas to the 10 most likely to perform.
The Gap Analyzer tells you what your competitors aren’t covering. It finds the white space where you can own a conversation instead of fighting for scraps in a crowded room.
The Refresh Scheduler tells you which of your existing assets need attention. It ensures the content you already invested in doesn’t silently decay into irrelevance.
This is the flywheel. Each cycle through Plan → Create → Optimize → Learn tightens the feedback loop. The Forecaster gets smarter. The Gap Analyzer spots patterns faster. The Refresh Scheduler catches decay earlier. After three months of consistent use, your content operations stop being reactive and start being predictive.
The companion article gave you the production engine. These three skills give you the strategic cockpit. Together they form a complete content operations system—one that doesn’t just produce content faster, but produces better content decisions that compound over time.
For the full roadmap on building an AI-powered content operation from scratch, start with our practitioner guide to Claude Code skills, then layer on the content operations architecture, and finally deploy these three strategic skills to close the loop.