Content Engine

Turns source material into platform-native content without flattening your voice into generic engagement slop. You feed it articles, demos, docs, or transcripts, and it adapts them for X, LinkedIn, YouTube, newsletters, or multi-platform campaigns. It starts from real claims instead of post templates, bans corporate filler like "game-changer" and fake engagement bait, and runs a quality gate before delivery. Pairs with brand-voice when you need consistent tone across outputs. Use it when you're repurposing something real and want each platform draft to actually sound like you, not like the algorithm wrote it.

skills.sh installs: 5.7K
GitHub stars: 300.3K
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/ecc --skill content-engine --agent claude-code

Installs into .claude/skills of the current project.

Files

Content Engine

Build platform-native content without flattening the author's real voice into platform slop.

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, docs, or internal notes into public content
building a launch sequence or ongoing content system around a product, insight, or narrative

Non-Negotiables

Start from source material, not generic post formulas.
Adapt the format for the platform, not the persona.
One post should carry one actual claim.
Specificity beats adjectives.
No engagement bait unless the user explicitly asks for it.

Source-First Workflow

Before drafting, identify the source set:

published articles
notes or internal memos
product demos
docs or changelogs
transcripts
screenshots
prior posts from the same author

If the user wants a specific voice, build a voice profile from real examples before writing. Use brand-voice as the canonical workflow when voice consistency matters across more than one output.