agentleFS
Sign inStart free
RojiosRojios/everything-claude-code/.cursor/skills/content-engine/SKILL.md

content-engine

Skill1 starsChanged 7 months agoMITView on GitHub

Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.

59 other projects use a version of this, 8 of them edited.

Adopted by

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

Week of Sep 13: 0 new projectsWeek 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 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

Used with

Projects with it also use brand-discovery, everything-claude-code and 1 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • ysyecustSkill

    brand-discovery

    Use when a brand needs to discover or articulate its identity through structured multi-session interviews. Covers purpose, positioning, audience, personality, voice, narrative, and founder-brand tension across 8 modules using laddering, 5 Whys, and projective techniques. Produces a resumable session with disk-persisted state and a master brandbook (90_SYNTHESIS.md).

    Also in 6 projects that use this

  • InfopibeSkill

    everything-claude-code

    Also in 11 projects that use this

  • renepfSkill

    orch-pipeline

    Shared orchestration engine for the orch-* skill family. Defines the gated Research-Plan-TDD-Review-Commit pipeline, the size classifier, the agent map, and the two human gates that the orch-* operation skills delegate to. Not usually invoked directly.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

8 rules. 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 27 edited versions we read keep these.

  • 8

    Distinctive

    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 post should carry one clear idea.

    line 31
  2. Distinctive:

    Use specifics over slogans.

    line 32
  3. Distinctive:

    Keep the ask small and clear.

    line 33
  4. Distinctive:

    keep links out of the main body unless necessary

    line 40
  5. Distinctive:

    keep the opening paragraph doing real work

    line 61
  6. Distinctive:

    When asked for a campaign, return:

    line 74
  7. Distinctive:

    no generic hype language

    line 86
  8. Distinctive:

    no duplicated copy across platforms unless requested

    line 87

“Common” is measured: kept by at least 6 in 10 of the 27 edited versions of this file we could read. “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 Engine

Turn one idea into strong, platform-native content instead of posting the same thing everywhere.

When to Activate

  • writing X posts or threads
  • drafting LinkedIn posts or launch updates
  • scripting short-form video or YouTube explainers
  • repurposing articles, podcasts, demos, or docs into social content
  • building a lightweight content plan around a launch, milestone, or theme

First Questions

Clarify:

  • source asset: what are we adapting from
  • audience: builders, investors, customers, operators, or general audience
  • platform: X, LinkedIn, TikTok, YouTube, newsletter, or multi-platform
  • goal: awareness, conversion, recruiting, authority, launch support, or engagement

Core Rules

  1. Adapt for the platform. Do not cross-post the same copy.
  2. Hooks matter more than summaries.
  3. Every post should carry one clear idea.
  4. Use specifics over slogans.
  5. Keep the ask small and clear.

Platform Guidance

X

  • open fast
  • one idea per post or per tweet in a thread
  • keep links out of the main body unless necessary
  • avoid hashtag spam

LinkedIn

  • strong first line
  • short paragraphs
  • more explicit framing around lessons, results, and takeaways

TikTok / Short Video

  • first 3 seconds must interrupt attention
  • script around visuals, not just narration
  • one demo, one claim, one CTA

YouTube

  • show the result early
  • structure by chapter
  • refresh the visual every 20-30 seconds

Newsletter

  • deliver one clear lens, not a bundle of unrelated items
  • make section titles skimmable
  • keep the opening paragraph doing real work

Repurposing Flow

Default cascade:

  1. anchor asset: article, video, demo, memo, or launch doc
  2. extract 3-7 atomic ideas
  3. write platform-native variants
  4. trim repetition across outputs
  5. align CTAs with platform intent

Deliverables

When asked for a campaign, return:

  • the core angle
  • platform-specific drafts
  • optional posting order
  • optional CTA variants
  • any missing inputs needed before publishing

Quality Gate

Before delivering:

  • each draft reads natively for its platform
  • hooks are strong and specific
  • no generic hype language
  • no duplicated copy across platforms unless requested
  • the CTA matches the content and audience

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.

Check your setup, free