content-engine

Verified

by affaan-m · Updated Apr 16, 2026

opus

1.7Kin2.7Kout

$0.191m 18s

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.

contentsocial-mediacopywritingrepurposingvoicemarketing

See It In Action

1 turns·claude

The project codebase is in your current working directory. Explore the files to understand the code before making changes. need review-ready launch drafts from today’s founder memo, demo transcript, and our last 2 launch posts for tomorrow’s announcement

Here are the review-ready launch drafts:

Voice Profile (from source posts)

Alex Chen / Layup voice: Understated technical founder. Leads with the concrete thing, not the emotion. Uses data as proof, not decoration. Personal but not performative. Acknowledges what the product doesn't do. Ends forward-looking or with a quiet CTA, never a question fishing for engagement.

Core Angle

Layup Flows gives engineering teams a sequenced AI review pipeline they configure in YAML — four checks in 12 seconds, so human reviewers skip the mechanical stuff and focus on architecture and logic.

Draft 1: LinkedIn Post

Platform: LinkedIn Author: Alex Chen Posting: April 12, 2026, 9am PT (simultaneous with ship)

We just shipped Layup Flows.

A Flow is a YAML pipeline that runs multiple AI review checks in sequence on every PR — security, style, performance, test coverage — in whatever order your team decides. If a step fails, the pipeline stops and tells you exactly where.

The request we kept hearing from larger teams: "We need security to run before style, and we need to skip performance checks on docs-only PRs." That's not a config toggle. That's a pipeline. So we built one.

What 34 beta teams showed us over 6 weeks:

3.2x more issues caught per PR compared to single-pass review
Median pipeline time: 12 seconds for four sequential checks
91% of teams kept Flows enabled after the trial ended
Zero false-positive security blocks in the final 2 weeks

The thing I want to be clear about: Flows handles the mechanical stuff. Security scanning, style conformance, coverage gaps. The human reviewer still matters — they just get to skip the checklist and focus on whether the approach is actually right.

Available now for every Layup team, every plan. Config is a YAML file any engineer can read in 30 seconds.

layup.dev/flows

Draft 2: X Thread

Platform: X Author: @alexchen Posting: April 12, 2026, 9am PT

Post 1: We just shipped Flows in Layup.

Define a sequence of AI review checks in YAML. They run in order on every PR — security, then style, then performance, then coverage. Four checks. Twelve seconds.

Here's what the config looks like →

[Screenshot of .layup/flows.yml]

Post 2: The problem Flows solves: enterprise teams don't want one AI review pass. They want control over what runs, in what order, and what gets skipped.

Example: skip performance analysis on docs-only PRs. Block the pipeline on security failures but only warn on style.

All in the YAML.

Post 3: Beta numbers from 34 teams over 6 weeks:

3.2x more issues caught per PR vs. single-pass
12 seconds median pipeline time
91% kept it on after the trial
Zero false-positive security blocks in the last 2 weeks

Post 4: One detail from our own usage: Flows found an N+1 query in a handler — database call inside a loop. Suggested a batch query, estimated 340ms saved per request at p95 load.

That's the kind of thing a human reviewer catches on a good day. Flows catches it every time in 3 seconds.

Post 5: Available now. Free on every plan. Config takes 30 seconds to write.

Enterprise teams get custom check authoring — define your own check types beyond the built-in set.

layup.dev/flows

Gaps Before Publishing

Screenshot needed for Post 1 of the X thread (the .layup/flows.yml config). The demo shows this exists in the repo — grab a clean capture.
Link validation: confirm layup.dev/flows is live and routed before 9am PT.
Enterprise CTA: the memo mentions 3 accounts already in custom-check beta. Content team should decide whether to add an enterprise waitlist link or keep it to one URL.

Both drafts follow Alex's existing voice — data-first, no hype language, clear about what the product does and doesn't do. Ready for content team review.

Claude Sonnet 4.6

Permissions

Scope	Description
filesystem:read

SKILL.md

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

FAQ

What does content-engine do?

When should I use content-engine?

Use it when you need a repeatable workflow that produces text response.

What does content-engine output?

In the evaluated run it produced text response.

How do I install or invoke content-engine?

npx skills add https://github.com/affaan-m/everything-claude-code --skill content-engine

Which agents does content-engine support?

Claude Code

What tools, channels, or permissions does content-engine need?

It uses no extra tools; channels commonly include text; permissions include filesystem:read.

Is content-engine safe to install?

Static analysis marked this skill as low risk; review side effects and permissions before enabling it.

How is content-engine different from an MCP or plugin?

A skill packages instructions and workflow conventions; tools, MCP servers, and plugins are dependencies the skill may call during execution.

Does content-engine outperform not using a skill?

About content-engine

When to use content-engine

You need X, LinkedIn, newsletter, YouTube, or short-video drafts adapted from an article, demo, transcript, or notes. You want one source asset repurposed into a coordinated multi-platform content campaign. You need content that matches an author's existing voice instead of generic platform-style writing.

When content-engine is not the right choice

You need actual publishing or cross-platform distribution rather than drafting content. You have no source material and want generic engagement-optimized social copy.

What it produces

Produces text response.

Install

npx skills add https://github.com/affaan-m/everything-claude-code --skill content-engine

Invoke: Ask Claude Code to use content-engine for the task.