agentleFS
NadavShanun-designNadavShanun-design/opengtm/skills/content-marketing-engine/SKILL.md

content-marketing-engine

Skill4 starsChanged 29 days agoMITView on GitHub

Use when planning content that generates and warms demand - choosing topics from real buyer questions, picking formats, setting a sustainable publishing cadence, and distributing/repurposing across channels (LinkedIn, Reddit, X, Substack, email, blog). Covers the create-once-distribute-many model, channel norms, community engagement that isn't spammy, and how content feeds both inbound and GEO.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are 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.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every piece should map to a buyer stage: awareness (their problem), consideration (approaches), decision (you vs alternatives).

    line 30
  2. Distinctive:

    Do start from real buyer questions and plan distribution before writing.

    line 77
  3. Distinctive:

    Keep it earned and authentic - Chronos posts as you, so the brand-safety rules above are yours to keep.

    line 96

≈ “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 marketing engine

Overview

Content is the compounding half of GTM: unlike outbound, it keeps working after you publish. A content engine (not random posts) turns your expertise into demand - it warms future outbound, earns inbound, and produces the quotable material AI answer engines cite (see generative-engine-optimization).

Core model: create once, distribute many. The writing is a fraction of the work; distribution is where most teams under-invest and most of the return lives.

Strategy - start from buyer questions

  • Mine the real questions your ICP asks (sales calls, support tickets, Reddit/ Quora threads, "people also ask," AI-prompt phrasing).
  • Organize into topic clusters tied to your positioning (see positioning-and-messaging and seo-fundamentals): a pillar piece + supporting pieces, interlinked.
  • Every piece should map to a buyer stage: awareness (their problem), consideration (approaches), decision (you vs alternatives).

Formats

Long-form guides (SEO/GEO anchors), short social posts, comparison/"vs" and "alternatives" pages (high buyer intent + AI-citation magnets), original data/ research (the most linkable + quotable asset), case studies (proof), and video/podcast (repurpose into everything else).

Cadence

Sustainable beats sporadic. A consistent weekly rhythm you can hold for a year compounds; a two-week sprint that burns out does nothing. Set a cadence the team can actually sustain, then protect it.

Distribution & repurposing (where the ROI is)

One pillar asset becomes: a LinkedIn post series, a few X threads, a Reddit answer where relevant, a newsletter issue, short video clips, and an SEO/GEO page. Plan the atomization before you write, so one effort feeds every channel.

Channel norms (respect them or get ignored)

  • LinkedIn - professional, story + insight, native (no "link in first comment" gaming beyond what's natural); engage in others' threads.
  • Reddit - give before you take. Communities punish self-promotion; be genuinely useful, disclose affiliation, earn the right to mention your product. (Reddit is also heavily cited by AI answer engines - authentic help compounds.)
  • X - fast, opinionated, thread-friendly; reply to be seen.
  • Substack / newsletter - owned audience, deeper takes, your highest-trust channel.

Community engagement

Earned, not extracted. Show up consistently, help without immediately pitching, and let the product come up naturally. Never seed fake posts, buy engagement, or astroturf - it's brittle, against platform rules, and torches trust (see the off-site rules in generative-engine-optimization).

Measurement

  • Leading: engagement, subscribers, shares, branded search lift, returning readers.
  • Lagging: content-influenced pipeline and closed-won, AI-citation presence.
  • Attribution is fuzzy - judge the engine over quarters, not posts over days.

Do / Don't

  • Do start from real buyer questions and plan distribution before writing.
  • Do give value first in communities; disclose affiliation.
  • Don't publish into the void - distribution is the job, not the afterthought.
  • Don't astroturf, buy engagement, or spam communities.

Common mistakes

  • Random acts of content with no cluster/strategy.
  • Writing a great piece and sharing it once.
  • Self-promotion in communities that expect give-first.
  • A cadence that burns the team out in a month.

Go live with Chronos (optional)

  • geo_twitter_post / geo_twitter_reply - publish and engage on X.
  • geo_reddit_post / geo_reddit_comment - contribute authentically where your buyers are.
  • geo_substack_post - publish to your owned newsletter audience.
  • geo_get_seo_geo_ideas / geo_implement_seo_idea - turn content gaps into shipped pages.

Keep it earned and authentic - Chronos posts as you, so the brand-safety rules above are yours to keep.

Connect in ~30s → CONNECT-CHRONOS.md. Free, no card.

See also: generative-engine-optimization, seo-fundamentals, positioning-and-messaging.

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.