agentleFS
moses607moses607/socialforge/skills/content-strategy-engine/SKILL.md

content-strategy-engine

Skill3 starsChanged 4 months agoMITView on GitHub

Turns a niche + audience into a repeatable content system — pillars, ratios, formats, a weekly calendar, and a repurposing loop — so output stays consistent instead of depending on one-off virality. Use when the user asks to plan content, build a content calendar or strategy, define pillars, or asks "what should I post" or "plan my month". Trigger on content plan/calendar/strategy/pillars/cadence requests. Works with any capable model.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Write your niche in one line: I help [audience] achieve [outcome] without [pain].

    line 11
  2. Distinctive:

    Never invert this. Promo-heavy feeds starve reach because they generate no saves or shares.

    line 22
  3. Very specific:

    Never post without a pillar tag and a job (value/story/proof/promo).

    line 67
  4. Distinctive:

    Every winner gets repurposed within 7 days.

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Content Strategy Engine

Virality is variance; a system is compounding. Growth comes from shipping predictable, on-theme content long enough for the algorithm and the audience to learn what you are for. First-principles: pick a narrow niche, own 3-5 topics, produce them on a fixed cadence in proven formats, and recycle every winner into five more assets. You are not chasing one hit — you are building a machine that makes hits likely.

1. Define pillars (the 3-5 topics you own)

  1. Write your niche in one line: I help [audience] achieve [outcome] without [pain].
  2. Derive 3-5 pillars — recurring topics you can post about for a year without repeating. Too broad = forgettable; more than 5 = diluted.
  3. Assign an output % split. Default: Pillar A 40% (your signature topic), B 25%, C 20%, D 15%. The 40% pillar is what you want to be known for.
  4. Pressure-test: each pillar must map to a real audience pain and a search or scroll intent. If you can't name the pain, cut it.

2. Set the content ratio (why you post, not just what)

Balance every week across four jobs so you earn the right to sell:

  • Value 50% — teach something usable in 60 seconds. Builds trust and saves/shares.
  • Story 25% — personal narrative, failure, behind-the-scenes. Builds connection and comments.
  • Social proof 15% — results, testimonials, case studies. Builds credibility.
  • Promo 10% — direct offer/CTA. You may only sell this hard because 90% gave first. Never invert this. Promo-heavy feeds starve reach because they generate no saves or shares.

3. Run the format library + repurposing loop

Rotate proven formats so pillars never feel repetitive:

  • Listicle — "7 X that Y". Fast, saveable.
  • Tutorial — step-by-step how-to. High save rate.
  • Story — problem → struggle → turn → lesson.
  • Contrarian take — "Everyone says X. They're wrong." High comments.
  • Reaction — respond to a trend/news in your niche.
  • Case study — one real result, deconstructed.

Repurposing loop — 1 pillar post becomes 5 assets:

  1. Long-form pillar (video/thread/article) = the source.
  2. Cut 2-3 short clips or standalone hooks.
  3. Pull 1 carousel/infographic from the key points.
  4. Extract 1 quote/text post.
  5. Reframe the comments/Q&A into a follow-up.

Output template

NICHE: I help ___ achieve ___ without ___
PILLARS:  A ___ (40%) | B ___ (25%) | C ___ (20%) | D ___ (15%)
RATIO:    Value 50 / Story 25 / Proof 15 / Promo 10

WEEKLY CALENDAR
Mon  Pillar A | Tutorial   | Value
Tue  Pillar B | Story      | Story
Wed  Pillar A | Listicle   | Value
Thu  Pillar C | Case study | Proof
Fri  Pillar A | Contrarian | Value
Sat  Pillar D | Reaction   | Story
Sun  Pillar B | Offer post | Promo

REPURPOSE: This week's pillar A post → 3 clips + 1 carousel + 1 quote

Platform variants

  • TikTok/Reels/Shorts: 1-3x/day, hook in 1s, native trends, lean Value + Story.
  • Instagram feed: 4-7x/week, carousels for saves, Stories daily for retention.
  • X/Threads: 2-5x/day, contrarian takes and story threads win.
  • LinkedIn: 3-5x/week, story + proof, no external links in the post body.
  • YouTube long: 1-2x/week, each becomes the source for a week of shorts.

Rules

  • Systems beat virality. A boring post shipped weekly outperforms a genius post shipped monthly.
  • Never post without a pillar tag and a job (value/story/proof/promo). Random posts train no one.
  • Protect the 40% pillar — dilution is the fastest way to be forgettable.
  • Earn the sell: keep promo at 10% or reach collapses.
  • Every winner gets repurposed within 7 days. Producing net-new content for every slot is amateur.
  • Cadence is a promise. Pick a frequency you can hold for 90 days, not your best week.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.