editorialVersion 1.0.030 minutes

Newsletter Issue Builder

Use this when a local signal could become a real story, but only if the AI can keep facts, assumptions, sources, and next reporting steps separated.

Why it is worth your emailYou are not downloading a prompt. You are getting a reporting workflow that tells the agent what it may use, what it must label, and what a human has to verify before anything gets published.

Expected output

A focused editorial brief with usable angles, source map, and next reporting actions.

Inputs named before work starts
Assumptions separated from facts
Next human action made explicit

Use it when

You have local signals, tips, documents, or public context but need a sharper reporting angle.
You want the AI agent to separate facts, assumptions, sources, and next reporting steps.
You need a repeatable workflow that protects names, dates, geography, and attribution.

What you need before running it

Topic, geography, known facts, available sources, and deadlines.

What has already been published or ruled out.

Any reporting constraints, privacy boundaries, or required caveats.

What comes out

A focused editorial brief with usable angles, source map, and next reporting actions.
Clear labels for verified facts, supplied facts, assumptions, and open questions.
A final human-review checklist before anything goes public.

What’s in the package

SKILL.mdexamples/worked-example.mdreferences/quality-checks.md

The archive also includes a manifest with version, checksum, compatibility, category, and package metadata.

Quality gates

No unsupported factual claims.
Dates, local names, and geography preserved.
Every material recommendation tied to an input or source.

Compatibility checked

Codex, Claude

Compatibility is published only after package structure and ordinary read-path checks.