agentleFS
VercelKnown publishervercel/eve/apps/templates/marketing-team-eve-template/agent/subagents/content-marketer/skills/content-planning/SKILL.md

content-planning

Skill5.9k starsChanged 4 days agoApache-2.0View on GitHub

Use when deciding what content to write: matching topics to buyer stages, choosing between searchable and shareable pieces, and grouping topics into pillars and clusters.

3 other projects use a version of this.

Adopted by

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projectsWeek of Oct 25: 0 new projectsWeek of Nov 1: 0 new projectsWeek of Nov 8: 0 new projects
Sep 2026Oct 2026Nov 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.

Most recently taken up by

Who's talking about vercel/eve

The biggest 5 of 57 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 57

Talked about on GitHub and Bluesky (57 times).

On GitHub · 50

45 more on GitHub

On Bluesky · 7

2 more on Bluesky

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When deciding what to write, before writing it:

    line 7
  2. Distinctive:

    Start from why someone buys, not from a keyword list.

    line 9
  3. Distinctive:

    Check a topic isn't already covered before adding it.

    line 17
  4. Very specific:

    Read references/buyer-stage-topics.md for questions to mine at each stage and where to find them.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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 planning

When deciding what to write, before writing it:

  • Start from why someone buys, not from a keyword list. A topic earns a place if it either answers a question a buyer actually has or shows the product doing the thing they're stuck on. Volume without either is traffic that never converts.
  • Know which kind of piece you're writing. Searchable content answers a query someone typed and lives or dies on being findable: it needs the question in the title, a direct answer near the top, and durable structure. Shareable content earns attention on its own: an opinion, original data, a story with a specific outcome. Optimizing one as though it were the other produces a piece that does neither.
  • Match the piece to where the reader is:
    • Unaware of the problem: symptoms, not solutions. Name the thing they're experiencing.
    • Comparing approaches: how the options actually differ, including where yours is the wrong choice.
    • Comparing products: specifics. Pricing, migration, limits, what breaks.
    • Already sold: implementation, onboarding, getting to value.
  • Group topics rather than listing them. Pick a few pillars the team wants to be known for, then write clusters of related pieces under each that link to one another. Ten pieces on three pillars beats thirty scattered ones, because the cluster compounds and the scatter doesn't.
  • Check a topic isn't already covered before adding it. Two pieces answering the same question split the traffic and neither wins; strengthening the existing piece usually beats writing a second.
  • Prioritize honestly. The best next piece is the one with real demand, a clear tie to the product, and evidence you can actually get. When you're missing the evidence, either go find it or pick a different topic.

Read references/buyer-stage-topics.md for questions to mine at each stage and where to find them.

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.