Content Engine

This is for when you need to turn one piece of source material into platform-specific content without just changing the line breaks. It adapts voice and structure for X, LinkedIn, TikTok, YouTube, and newsletters by starting from actual source docs, transcripts, or prior posts rather than generic templates. The skill enforces hard bans on engagement bait and corporate slop phrases, and it integrates with brand-voice when you need consistency across multiple outputs. Use it when you're repurposing a launch asset, demo, or article and want each platform to get something native instead of a cross-post with emoji swapped in.

skills.sh installs: 5.2K
GitHub stars: 229.1K
last updated: Jul 14, 2026

View on GitHub

Install

$ npx -y skills add affaan-m/everything-claude-code --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.