Content Engine
Turn demos, docs, and real notes into platform-native posts, threads, scripts, and calendars for X, LinkedIn, TikTok, YouTube, and newsletters without generic slop.
Overview
Content Engine is an agent skill most often used in Grow (also Launch) that builds platform-native social and video content from real source material with optional brand-voice consistency.
Install
npx skills add https://github.com/affaan-m/everything-claude-code --skill content-engineWhat is this skill?
- Source-first workflow: articles, memos, demos, changelogs, transcripts, and prior posts before drafting
- Platform-native outputs for X, LinkedIn, TikTok, YouTube, newsletters, and multi-platform repurposing
- Five non-negotiables including one claim per post and no engagement bait unless requested
- Canonical voice layer via brand-voice when consistency matters across more than one output
- Launch sequences and ongoing content systems around a product, insight, or narrative
- 5 non-negotiable content rules
- 6+ platform formats (X, LinkedIn, TikTok, YouTube, newsletter, repurposed campaigns)
Adoption & trust: 4.6k installs on skills.sh; 210k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You have product truth in docs and demos but no disciplined way to turn it into credible, platform-specific posts without sounding like generic AI marketing.
Who is it for?
Founders running launch weeks or weekly content who will supply real artifacts (changelog, demo, article) and want one claim per piece per channel.
Skip if: Buyers who only want SEO technical audits, paid ad creative matrices, or engagement-bait viral hooks without source material.
When should I use this skill?
User wants social posts, threads, scripts, content calendars, launch sequences, or one source asset adapted across platforms.
What do I get? / Deliverables
You get draft posts, threads, scripts, or a repurposing plan grounded in your sources, with voice aligned via brand-voice when you need repeatability across platforms.
- Platform-native post or thread drafts
- Short-form or YouTube scripts
- Repurposing or calendar outline
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Ongoing content systems and repurposing compound audience after ship, so grow/content is the primary shelf though launch sequences start earlier. The skill is explicitly about drafting and adapting content formats—not analytics dashboards or support macros—matching the content subphase.
Where it fits
Sequence X and LinkedIn posts from a single launch narrative and demo recording.
Weekly calendar repurposing docs and changelogs into threads and short video scripts.
Draft clear public messaging while still refining positioning from internal notes.
How it compares
A content workflow from your actual ship artifacts—not a keyword-stuffing SEO generator or a single-platform copy template.
Common Questions / FAQ
Who is content-engine for?
Solo builders and small teams who ship product and need X, LinkedIn, short video, YouTube, or newsletter output that stays specific and on-voice.
When should I use content-engine?
At launch when drafting announcement threads and LinkedIn updates, during grow for calendars and repurposing, and anytime you turn a demo, doc, or podcast into multi-platform native cuts.
Is content-engine safe to install?
It is primarily prose generation from user-provided sources; review the Security Audits panel on this page before enabling in agents with broad file access.
Workflow Chain
Then invoke: brand voice
SKILL.md
READMESKILL.md - Content Engine
# 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 1. Start from source material, not generic post formulas. 2. Adapt the format for the platform, not the persona. 3. One post should carry one actual claim. 4. Specificity beats adjectives. 5. 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 ### LinkedIn - 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 ### Newsletter - open with the point, conflict, or artifact - do not spend the first paragraph warming up - every section needs to add something new ## Repurposing Flow 1. Pick the anchor asset. 2. Extract 3 to 7 atomic claims or scenes. 3. Rank them by sharpness, novelty, and proof. 4. Assign one strong idea per output. 5. Adapt structure for each platform. 6. Strip platform-shaped filler. 7. 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 obse