newsletter — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited newsletter (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Write newsletter issues that subscribers open, read, and reply to. A newsletter is a recurring relationship, not a broadcast: it must be consistent (same format and cadence every time), valuable (useful before promotional), and personal (sounds like one human wrote it to one human). Prime directive: the reader must finish the issue glad they opened it — value first, promotion never more than a postscript.
skills/marketing/email-sequences — a newsletter is a recurring broadcast, not an automation.skills/marketing/lead-magnet first.skills/marketing/content-atomizer (it can hand the newsletter item back here).Ask in one batch, only what's missing:
skills/marketing/brand-voice output if it exists).If the user is starting a newsletter from scratch, also ask what they can sustain: writing capacity and how much source material their work naturally generates. Otherwise infer format and cadence from past issues. If enough is known, state assumptions and draft — don't stall.
Pick one primary format by decision rule — the user can guest-star other formats occasionally, but the flagship format is what subscribers learn to expect:
| If the user… | Format | Skeleton |
|---|---|---|
| Reads widely, low writing capacity | Curated | Personal opening note → 5–10 links, each with 1–2 sentences of your take (the commentary is the product) → sign-off |
| Has rich personal/client experiences | Story-driven | Hook → story → the lesson → how the reader applies it → sign-off |
| Sells expertise (consultant, coach, B2B) | Educational | Why this matters → the concept/framework → 2–3 real examples → how to apply → sign-off |
| Has network access to interesting people | Interview | Who + why them → 5–10 Q&As → your key takeaway → sign-off |
| Works with data or research | Data-driven | Surprising finding → the data → what it means → what to do with it → sign-off |
| Builds in public / personal brand | Personal update | Working on → learning → thinking about → one recommendation → sign-off |
Cadence by decision rule: weekly if their work generates material weekly and they'll actually sustain it; otherwise bi-weekly (the default recommendation — heuristic: a kept bi-weekly schedule beats a broken weekly one); monthly only if the format is heavyweight (interview, data-driven). Fix the send day/time and put it in the Blueprint.
Every issue carries exactly one central idea (curated format: one theme unifying the links). From the raw material, pull the single most useful/surprising insight for this audience. If the material holds several strong ideas, list them, pick the best for now, and bank the rest as future issue seeds in the delivery notes.
Length target: 300–800 words for original-content formats; curated can run longer but each link blurb stays ≤2 sentences of commentary.
Run the quality bar. Then deliver in the required output format, including next-issue seeds so the user never faces a blank page.
# Newsletter Issue — [working title]
## Subject line options
1. "…" (n chars)
2. "…" (n chars)
3. "…" (n chars)
Recommended: #_ — [one-line reason]
## Preview text
"…" (n chars)
## Body
[Full issue: opening → format-skeleton body → CTA → sign-off → P.S.]
## Send notes
- Format: [which of the six] · Cadence slot: [day/time]
- CTA: [the one action asked]
- Promo present: [none | P.S. only | promotional issue]
## Next-issue seeds
- [2–3 banked ideas pulled from this material or conversation]When setting up a new newsletter, precede the issue with:
# Newsletter Blueprint — [name]
- Audience & promise: [who subscribes and what each issue gives them]
- Flagship format: [one of six] — [why, per decision rule]
- Cadence: [weekly/bi-weekly/monthly], sent [day/time]
- Section template: [the recurring skeleton, so every issue is structurally identical]
- Voice notes: [3–5 bullets]
- Metrics to watch: open rate trend, reply count, unsubscribe spikes per issueCheck every item; fix before delivering:
skills/marketing/brand-voice — supplies the voice guide the issue must match; run it first if the user has no defined voice.skills/marketing/lead-magnet — builds the subscriber-acquisition offer; new subscribers flow through skills/marketing/email-sequences (welcome) before landing on this newsletter.skills/marketing/email-sequences — owns triggered/automated email; the newsletter is the ongoing touchpoint subscribers graduate into.skills/marketing/content-atomizer — turns blog/video content into newsletter items, and turns strong newsletter issues back into social posts.skills/marketing/seo-content — published articles are recurring issue material; pass title, link, and one-sentence hook.~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.