agentsclimarketplace

Content strategist

Skill EditorialOS/editorial-os/skills/content-strategist

Editorial strategy system for Claude. 7 commands, 5 specialist skills — audit, competitor analysis, 90-day calendars, drafting, social repurposing. Your Google Drive folder is the configuration.

Install
npx -y skills add EditorialOS/editorial-os --skill content-strategist

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Apply strategic content judgment — pillar health assessment, gap identification, opportunity prioritization, and recommendation sequencing. Frame findings in terms of business goals, not content metrics. Content metrics are inputs. Business outcomes are the output. Used by /audit and /calendar.

SKILL.md

12.7 KB, ~2.8k tokens by cl100k_base, as published. Nobody here has run it

Content Strategist

Frame every content decision in terms of business goals. Content metrics are inputs. Business outcomes are the output. A content audit that identifies 12 gaps is useless if it doesn't tell you which 3 to act on this month.

Strategic Judgment Framework

Four questions in order. Answer all four before making any recommendation. A recommendation that fails any single question gets cut.

Question 1 — Is This Gap Real?

Does the missing content type represent an actual audience need — or just an editorial preference?

Tests for reality:

  • Is there evidence the audience wants this? (search volume, engagement on adjacent content, community questions, segment preferences from client context)
  • Are competitors filling this need and getting engagement?
  • Has the audience explicitly asked for this? (survey data, email replies, social comments)

Red flags for invented gaps:

  • "We should write about X because everyone else does" (herd behavior, not audience signal)
  • "This topic is trending" with no connection to the client's audience
  • "We haven't covered X" without evidence the audience cares about X

Question 2 — Is It Winnable?

Given the team's constraints and publishing cadence, can this client actually execute on it?

Winnability assessment:

FactorWinnableStretchNot Winnable
Team has the expertiseDeep domain knowledgeCan research adequatelyOutside domain
Fits publishing cadenceNormal effort per pieceRequires extra timeWould need new capacity
Has source materialExisting research, data, interviewsCan acquire in timeBlocked by dependencies
Competitive landscapeUncontested or thin competitionContested but differentiatedCompetitor dominates, no angle

If two or more factors rate "Not Winnable" — cut the recommendation regardless of how good the gap is.

Question 3 — Does It Advance the Primary Goal?

If a gap doesn't connect to the primary business goal, deprioritize it — even if it's real and winnable.

Goal connection types:

ConnectionWeightExample
DirectHighGap in product education content → goal is reduce churn → direct connection
IndirectMediumGap in thought leadership → goal is lead generation → indirect (builds authority that supports lead gen)
TangentialLowGap in company culture content → goal is lead generation → tangential (nice to have, not a driver)
NoneCutGap exists but has no path to the business goal

Question 4 — Has It Been Tried?

Check content history before recommending anything. This is the filter most content strategies skip.

History check:

What You FindAction
Never triedGreen light — recommend with standard confidence
Tried once, inconclusiveGreen light — recommend with modified approach, note what to do differently
Tried and underperformedYellow flag — recommend only with a clear differentiation from the previous attempt
Tried repeatedly and failedRed flag — cut the recommendation, note why it keeps failing
Tried and workedBuild on it — recommend expansion, not repetition

Pillar Health Assessment

For each content pillar, assess across four dimensions:

Health Matrix

DimensionHealthyDevelopingThinUntested
Coverage10+ pieces, multiple angles, variety of formats5-10 pieces, developing depth< 5 pieces, single angle or format0 pieces
PerformanceAt least one top performer, consistent engagementSome engagement, no standout pieceBelow average engagement or no dataNo data
CompetitiveClear source authority for this topicPresence, but not the go-toCompetitors are stronger hereWide open — nobody owns it
Goal alignmentDirect line to primary business goalIndirect but meaningfulTangential at bestConnection is hypothetical

Reading the Matrix

  • All four Healthy → Maintain and defend this pillar. Don't over-invest — protect the lead.
  • Coverage Thin but Competitive is Wide Open → This is the highest-leverage opportunity. Build here.
  • Performance Healthy but Coverage Thin → You have a winner. Create more content in this pillar.
  • Coverage Healthy but Performance Thin → The content exists but isn't landing. Angle or format problem.
  • Goal Alignment is Tangential → Even if coverage and performance are healthy, deprioritize. Don't cut — but don't grow.
  • All four Thin or Untested → Decide: is this pillar worth investing in, or should it be retired?

Gap Typing

Not all gaps are equal. Label each gap by type — the type determines the solution.

Six Gap Types

Gap TypeWhat's MissingSolution DirectionTypical Effort
Format gapRight topic, wrong format. Audience wants video; you're publishing text.Produce the content in the format the audience actually consumes.Medium-High (new production capability)
Depth gapCoverage exists but is superficial. Competitors go deeper.Create definitive, comprehensive content on the topic.Medium (research and writing time)
Recency gapTopic is covered but content is outdated.Update and republish with current information.Low (refresh, not create)
Angle gapSame topic, better angle available. Positioning isn't differentiated.Find the angle only this brand can own.Low-Medium (reframing, not new research)
Segment gapPillar is covered but only for one segment. Others are underserved.Create segment-specific versions of existing strong content.Medium (adaptation, not creation from scratch)
Pillar gapEntire theme missing from content strategy.Build the pillar from scratch with a 90-day development plan.High (sustained investment)

Gap Type Determines Priority Approach

Gap TypeTypical HorizonWhy
Recency gap30 days (quick win)Refresh existing content — lowest effort, immediate value
Angle gap30 days (quick win)Reframe existing knowledge — no new research needed
Segment gap30-90 daysAdapt existing content — moderate effort
Depth gap90 daysCreate comprehensive content — sustained effort
Format gap90-180 daysMay require new production capabilities
Pillar gap180 daysBuild a new content territory from scratch

Content Value Scoring

When there are more than 3 candidate recommendations, score each to prioritize ruthlessly.

Scoring Dimensions

DimensionScore 1Score 2Score 3
Goal alignmentTangential connection to primary goalIndirect connectionDirect, measurable connection
EffortHigh effort — new capability, significant productionModerate effort — within current capability, requires dedicated timeLow effort — refresh, adapt, or repurpose existing content
DifferentiationCompetitors could publish this verbatimSome differentiation but not defensibleOnly this brand can own this angle
Audience fitServes a low-priority or well-served segmentServes a moderate-priority segmentServes an underserved or high-value segment

Sum = priority score (max 12).

ScorePriorityAction
9-12P1Execute in the next 30 days
6-8P2Plan for 30-90 day horizon
3-5P3Backlog — revisit next quarter
< 3CutDon't recommend

Scoring Rules

  • Show the score breakdown explicitly — the user should see the math, not just the result
  • If two recommendations score equally, prefer the one with lower effort (faster to market)
  • If a P1 recommendation exceeds team capacity, flag the capacity conflict — don't silently downgrade
  • Never score more than 8 recommendations — if you have more candidates, tighten the four-question filter

Recommendation Sequencing

Always sequence recommendations across three horizons. This prevents the "everything is urgent" trap.

30 Days — Quick Wins

CriteriaMust Meet ALL
Executable without new resourcesNo new hires, tools, or capabilities required
Uses tools already availableDon't recommend video if the team has no video capability
Does not repeat previously failed approachesHistory check passed
Highest business impact per hour of effortScore ≥ 9, effort dimension ≥ 2

Typical 30-day actions:

  • Refresh outdated high-performing content (recency gap)
  • Reframe existing content for underserved segment (segment gap)
  • Adapt a strong piece to a new angle (angle gap)
  • Publish the "obvious" piece that's been missing from a healthy pillar

90 Days — Strategic Build

CriteriaMust Meet ALL
Requires sustained effort but not new headcountWithin current team capability
Builds pillar position, not just individual piecesMultiple pieces contributing to one territory
Connects to quarterly business goalsDirect or indirect goal alignment

Typical 90-day actions:

  • Develop a Thin pillar with 4-6 coordinated pieces
  • Build a content series around a depth gap
  • Create segment-specific content tracks
  • Establish a regular cadence for an Untested pillar

6 Months — Position Ownership

CriteriaWhat to Define
Concrete definition of "winning"What does owning this pillar look like in measurable terms?
DefensibilityWhat would a competitor need to do to overtake you? How hard is that?
Audience recognitionWould your audience associate this topic with your brand first?
Sustainable advantageDoes your position get stronger over time (compounding) or require constant reinvestment?

Content Performance Benchmarks

Use these only when no real client data is available from ~~docs or ~~email. Always label as "industry benchmarks."

Blog/Website Content

MetricStrongAverageWeak
Time on page> 4 minutes2-4 minutes< 2 minutes
Bounce rate< 40%40-65%> 65%
Scroll depth> 75%50-75%< 50%
Social shares per post> 5010-50< 10
Organic traffic growth (MoM)> 10%3-10%Flat or declining

Email Newsletter

MetricStrongAverageWeak
Open rate> 30%18-30%< 18%
Click rate> 4%2-4%< 2%
Unsubscribe rate< 0.2%0.2-0.5%> 0.5%
List growth (monthly)> 5%2-5%< 2% or declining

Social Media (Organic)

MetricStrongAverageWeak
LinkedIn engagement rate> 3%1-3%< 1%
Twitter/X engagement rate> 1.5%0.5-1.5%< 0.5%
Instagram engagement rate> 3%1-3%< 1%

Always Do

  • Run all four strategic questions before making any recommendation
  • Check content history before recommending anything
  • Size every recommendation to team capacity
  • Connect every gap to a specific audience segment who's underserved by it
  • Score recommendations explicitly when there are more than 3 options
  • Show the priority math — users need to see why one recommendation outranks another
  • Sequence recommendations across 30/90/180 day horizons
  • Use real performance data when available, industry benchmarks when not

Never Do

  • Recommend publishing cadence that exceeds team capacity without flagging it
  • Frame competitor strengths as weaknesses — be honest
  • Recommend a pillar that doesn't connect to business goals
  • Suggest tools the team doesn't have without flagging the resource gap
  • Skip the history check — this is how strategies repeat past failures
  • Score more than 8 candidates — if you have more, tighten the filter
  • Present industry benchmarks as if they're the client's real data
  • Recommend "more content" as a strategy — more is not a strategy, better-targeted is

Cross-Skill Dependencies

  • Receives from: editorial-config (all client context — pillars, competitors, segments, constraints, history, goals)
  • Used by: /audit (strategic framing of gaps, scoring, sequencing)
  • Used by: /calendar (priority recommendations drive Month 1 planning)
  • Feeds into: competitive-intel (strategic context for battlefield analysis)

Gives 0 of the 12 instructions most roadmap strategy skills give in ~2.8k tokens

Counted across 591 of the 672 authors here whose files we hold, read 2026-08-07

  • read product marketing context before asking questionsin 21 of 591, across 10 files
  • base price on perceived value, not costin 15 of 591, across 4 files
  • compact after finalizing a planin 14 of 591, across 9 files
  • differentiate tiers using features, limits, or supportin 14 of 591, across 3 files
  • use Van Westendorp to find acceptable price rangein 13 of 591, across 2 files
  • use MaxDiff to identify highly valued featuresin 13 of 591, across 2 files
  • map topics to buyer journey stagesin 12 of 591, across 6 files
  • Extract domain capabilities and classify subdomainsin 11 of 591, across 1 file
  • Define bounded contexts around consistency and ownershipin 11 of 591, across 1 file
  • Establish a ubiquitous language glossary and anti-termsin 11 of 591, across 1 file
  • Capture context boundaries in ADRs before implementationin 11 of 591, across 1 file
  • Open the strategic design template if neededin 11 of 591, across 1 file

Said here and by no other author read

  • frame decisions in terms of business goals
  • check content history before recommending
  • size every recommendation to team capacity
  • connect every gap to an underserved audience segment
  • score recommendations explicitly when there are over three options
  • show the priority math breakdown

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.