content-engine

Use it when:: You want posts, threads, video scripts or a newsletter built from something you already have, such as an article, demo, changelog or transcript.
It does:: Pulls 3 to 7 claims from the source, ranks them, gives each output one idea, and adapts the format per platform but not the voice.
You get:: Platform-native drafts, the core angle, a short voice profile when voice matters, and the gaps to fill before publishing.
Bans:: Stock hype such as "game-changer", reply-farming questions at the end, and engagement padding that wasn't in the source.
Works with:: ECC's brand-voice skill for a reusable voice profile; drafting only, it posts nothing itself.

TL;DR

ECC's social writing skill starts from what you already have, not from post formulas. It gathers the source set first: articles, notes, demos, docs, changelogs, transcripts, screenshots and the author's earlier posts. When voice matters across several outputs, or the content is a launch or reputation-sensitive, it runs ECC's brand-voice skill first and reuses its voice profile. To repurpose, it picks an anchor asset, extracts 3 to 7 atomic claims or scenes, ranks them by sharpness, novelty and proof, and assigns one idea per output. Each platform gets its own rules: X opens with the strongest claim and every thread post advances the argument; LinkedIn expands only enough for outsiders to follow, with no fake lesson posts or corporate inspiration cadence; short video is scripted around the visuals and shows the payoff in the first seconds; YouTube shows the result early; newsletters open with the point. A quality gate checks that every draft sounds like the author, carries a real claim, repeats no copy across platforms, and has only CTAs you approved.

Summarizes the skill at d2ef268.

npx skills add https://github.com/affaan-m/ecc --skill content-engine

skills.sh page Source on GitHub All skills from affaan-m/ecc

Total Downloads: 5,700 on skills.sh, Nov 9, 2026
Repo stars: 299,776 affaan-m/ecc
First seen: May 19, 2026 on skills.sh

Weekly Downloads

457

+71% over the 8 weeks to Nov 9

Weekly values

Week to	Installs
Sep 21	268
Sep 28	178
Oct 5	154
Oct 12	246
Oct 19	427
Oct 26	410
Nov 2	484
Nov 9	457

Category	category:marketing category:writing SEO, copy, conversion, social media and e-commerce. Articles, docs, internal comms, research write-ups and prose that doesn't read as generated.
Type	type:workflow A multi-step process the agent follows: interview, debug, run a TDD loop, review.
Effect	effect:none Adds no side effects of its own. It shapes how the agent thinks, writes or reviews. Guidelines and routers are always effect:none, even when the task they support edits code.
Needs	needs:none Instructions only. Works in any agent that supports skills.
Publisher	by:community Everyone else. Unverified vendor claims default to community.
Topics	social-media copywriting writing
Stack	stack:x-twitter stack:linkedin stack:tiktok stack:youtube

SKILL.md

From affaan-m/ecc at d2ef268. Checked daily, last changed Nov 6, 2026.

Frontmatter

name: content-engine
description: 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.
metadata:
  origin: ECC

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.

Voice Handling

brand-voice is the canonical voice layer.

Run it first when:

there are multiple downstream outputs
the user explicitly cares about writing style
the content is launch, outreach, or reputation-sensitive

Reuse the resulting VOICE PROFILE here instead of rebuilding a second voice model. If the user wants Affaan / ECC voice specifically, still treat brand-voice as the source of truth and feed it the best live or source-derived material available.

Hard Bans

Delete and rewrite any of these:

"In today's rapidly evolving landscape"
"game-changer", "revolutionary", "cutting-edge"
"here's why this matters" unless it is followed immediately by something concrete
ending with a LinkedIn-style question just to farm replies
forced casualness on LinkedIn
fake engagement padding that was not present in the source material

Platform Adaptation Rules

X

open with the strongest claim, artifact, or tension
keep the compression if the source voice is compressed
if writing a thread, each post must advance the argument
do not pad with context the audience does not need

expand only enough for people outside the immediate niche to follow
do not turn it into a fake lesson post unless the source material actually is reflective
no corporate inspiration cadence
no praise-stacking, no "journey" filler

Short Video

script around the visual sequence and proof points
first seconds should show the result, problem, or punch
do not write narration that sounds better on paper than on screen

YouTube

show the result or tension early
organize by argument or progression, not filler sections
use chaptering only when it helps clarity

open with the point, conflict, or artifact
do not spend the first paragraph warming up
every section needs to add something new

Repurposing Flow

Pick the anchor asset.
Extract 3 to 7 atomic claims or scenes.
Rank them by sharpness, novelty, and proof.
Assign one strong idea per output.
Adapt structure for each platform.
Strip platform-shaped filler.
Run the quality gate.

Deliverables

When asked for a campaign, return:

a short voice profile if voice matching matters
the core angle
platform-native drafts
posting order only if it helps execution
gaps that must be filled before publishing

Quality Gate

Before delivering:

every draft sounds like the intended author, not the platform stereotype
every draft contains a real claim, proof point, or concrete observation
no generic hype language remains
no fake engagement bait remains
no duplicated copy across platforms unless requested
any CTA is earned and user-approved

Related Skills

brand-voice for source-derived voice profiles
crosspost for platform-specific distribution
x-api for sourcing recent posts and publishing approved X output