newsletter-subject-line-writer — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited newsletter-subject-line-writer (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.
Writes five subject line options for a newsletter edition — each using a different opening strategy — so you can choose the one that fits your audience, tone, and what the edition actually delivers.
Required: The lead story or main theme of the edition · One sentence describing what readers will get if they open it · Your newsletter's name (used for the preview text context, not the subject line itself unless relevant)
Optional: Tone of the newsletter (e.g., serious investigative, warm editorial, dry analytical, playful) · Audience (e.g., general public, policy professionals, media industry) · Any words or formats to avoid (e.g., no questions, no emoji, no ALL CAPS) · Approximate word or character limit if your email platform enforces one · Preview text (the sentence that appears after the subject line in most email clients) — if provided, the assistant will write the subject lines to complement it rather than repeat it
Five numbered subject line options, each followed by a one-line label explaining the approach (e.g., "Declarative statement — leads with the finding"). Subject lines: 40–60 characters preferred for mobile readability, maximum 70 characters. No quotation marks around the subject lines. If a subject line is outside the recommended length, a brief note is added. No explanation beyond the label — the options speak for themselves.
Lead story / main theme: A reported investigation into how a national broadband infrastructure programme has left rural households paying for upgraded connections they cannot actually use — because the physical installation was signed off as complete before it was functional What readers get if they open: A data-backed investigation with testimony from affected households, contractor interviews, and internal government performance data Newsletter name: The Infrastructure Brief Tone: Serious, analytical — readers are policy professionals, engineers, and civil servants Avoid: Questions, emoji Preview text (already written): "Thousands of households are paying for broadband speeds they cannot access. Here is how that happened."
Declarative statement — leads with the core injustice; short and factual
Narrative tension — frames the story as a system failure with a clear sequence; 68 characters, slightly above preferred length
Specific framing — uses the precise bureaucratic distinction at the heart of the investigation
Counterintuitive framing — draws on the investigation's central irony without overstating it
Reader-positioning frame — positions the edition as an explainer of a systemic problem, appeals to policy and oversight audiences
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.