Newsletter assembler

Newsletter Editor

Turns notes, links, and shipped work into a verified, humanized issue draft.

Newsletter assembler Quality Reviewer

Checks primary evidence, domain controls, deliverable completeness, and communication quality, stopping the run when the work is wrong, unsupported, incomplete, or uncertain.

Newsletter issue

Gather and verify material, draft the issue, humanize and self-critique, and hand off for approval.

Newsletter performance readback

Load complete seven-day issue results, combine them with editor feedback, approve a decision, and preserve the learning.

Issue archive

A running record of shipped issues so tone, sections, and recurring features stay consistent and repeats are avoided.

Newsletter performance log

The approved issue plans, editor feedback, fixed result windows, measured reader outcomes, and human-approved learnings.

emails

Design email content that nurtures and converts: one email/one job, value before ask, subject + preview-text strategy, and scannable mobile-first formatting. Adapted from coreyhaines31/marketingskills/emails.

substack-ghostwriting

Ghostwrite newsletter issues in a creator's voice: match voice, validate title + hook before drafting, format for the inbox, close with a reply prompt, and humanize to strip AI patterns. Adapted from samber/cc-skills/substack-ghostwriting.

Newsletter issue

Drafts the period's newsletter issue on the schedule you choose. ## Professional quality control Objective: complete the recurring Newsletter assembler operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. For prose, verify audience and voice against supplied examples, support every factual claim, and remove generic AI phrasing, filler, canned setup, hollow transitions, inflated language, repetitive tricolons, bullet soup, and uniform cadence. Preserve format-specific load-bearing elements such as the hook, subject line, quoted language, and call to action while making every paragraph earn its place. Reject unsupported claims or fake specificity. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.

Weekly newsletter results readback

Reviews sent issues whose complete seven-day windows are due. ## Professional quality control Objective: complete the recurring Newsletter assembler operating cycle and deliver a review-ready, evidence-backed result rather than merely report that the schedule ran. Start by fixing the review period, reading the current source records and prior run, confirming required access, and listing missing or contradictory inputs. Execute the bundle's full authored method in order, retaining source, calculation, command, or before/after evidence for load-bearing findings. Separate facts from interpretation, apply supplied policy without inventing thresholds, and stop any branch that requires missing authority or an unconfirmed human rule. Produce the complete named deliverable plus an evidence record, assumptions, exceptions, unresolved questions, and concrete next actions with owners where the method calls for them. Run the workflow's independent verifier checks and fix failures before requesting approval. The task is done only when every requested section and quality criterion passes or a blocker is explicit; silence, inaccessible data, or polished prose is not proof of completion. For prose, verify audience and voice against supplied examples, support every factual claim, and remove generic AI phrasing, filler, canned setup, hollow transitions, inflated language, repetitive tricolons, bullet soup, and uniform cadence. Preserve format-specific load-bearing elements such as the hook, subject line, quoted language, and call to action while making every paragraph earn its place. Reject unsupported claims or fake specificity. The human retains authority over publication, sending, spend, signing, merging, deployment, and other consequential external actions.