Content Engine: Source-Based Drafts across Channels

What it does

ECC’s content engine begins with an anchor asset such as an interview, article, demonstration or research memo. It extracts a small set of atomic claims or scenes, then adapts them for X, LinkedIn, short video, YouTube or a newsletter. The source rejects fake engagement, unsupported proof and identical copy pasted into every format. Its useful distinction is between a reusable underlying idea and the presentation needed by a channel. A short video needs a visible moment and spoken structure; a newsletter needs a reason for its specific audience to read further.

When to use it

• Turn an approved product demonstration into a short-video script and newsletter block.
• Adapt a sourced research article into a LinkedIn post and a concise X thread.
• Build a weekly draft package without repeating the same hook across every channel.

Step-by-step workflow

1. Select the authoritative anchor asset, intended audience and approved call to action; identify rights and factual limits.
2. Extract three to seven defensible claims or scenes, linking each to the original evidence and marking any interpretation.
3. Choose formats that suit the material and write native hooks, structure and endings for each channel.
4. Review voice, proof and visual instructions; remove fake urgency, invented testimonials and platform-inappropriate repetition.
5. Deliver a labeled draft package with asset needs and review status, keeping scheduling and publishing as separate authorized actions.

Example request

Use our approved two-minute desk-lamp demonstration to draft one 20-second vertical video, one LinkedIn post and a newsletter block. Extract only claims visible in the demonstration or confirmed in the product specification. The video should show a before-and-after lighting scene, include spoken English and matching captions, and avoid unverified health or productivity promises. Use the approved product-page CTA. Do not invent reviews, limited stock or discounts. Return channel-specific drafts, a shot list and an evidence map. Do not schedule or publish anything.

Worked example

The anchor footage shows brightness adjustment and a phone stand but does not demonstrate charging speed. The video draft can lead with a cluttered desk becoming easier to arrange, while its shot list shows the actual controls. The LinkedIn version can discuss the design tradeoff in organizing a small workspace, and the newsletter can summarize the practical use case. None should add a fast-charging claim just because a connector appears in frame. The evidence map marks that detail as unverified and lists any missing close-up footage before an editor begins rendering.

What you get

A platform-specific draft package, claim-to-source map, shot or asset requirements and an explicit review and publication status.

How to evaluate the result

• Each material claim maps to the anchor asset or an approved source.
• Every channel has a native structure rather than identical recycled copy.
• Draft, rendered, approved and published states remain distinct.

What you need

An approved source asset, channel and audience choices, usable rights for media and a clear CTA. Rendering, account access and scheduling tools are separate capabilities.

Setup and activation

The reviewed ECC source provides an .agents skill layout. Consult the repository README for the chosen client, retain referenced supporting files and explicitly activate only the workflow needed. This catalogue read source files; it installed and executed nothing. Client compatibility depends on available tools and instruction loading, and was not runtime-tested here. Before installation, scan the exact source version, review permissions and use disposable non-sensitive examples.

Limits and considerations

Repurposing does not create new evidence or media rights. Platform reach and conversion cannot be inferred from a strong hook. Avoid synthetic testimonials and deceptive urgency. A content brief is not a rendered video, and a finished draft is not authorization to post or message an audience.

Related workflows

• Use Article Writing to develop the anchor article.
• Use Market Research when a claim needs current primary-source verification.

License and reuse

MIT in the selected SKILL.md and repository LICENSE. Preserve notices; external packages, services and example dependencies retain their own terms.

Further reading

• Reviewed skill at immutable commit
• Reviewed publisher README
• Reviewed MIT license