newsletter-coach

newsletter-coach is a skill for Claude Code from nicepkg/ai-workflow. It costs 48 tokens per session (3,444 once invoked), scanned A, original, MIT.

A writing coach that turns lessons from everyday experiences into drafts for an educational newsletter. It helps develop ideas, create outlines, expand sections, and match the style of example newsletters.

In plain words
What is it for?
Use it to brainstorm newsletter topics, shape personal experiences into educational articles, and write content for The Little Blue Report.
Why use it?
It helps when you have an experience worth writing about but are unsure what the lesson is or how to structure it. It guides the writing process from an initial idea to a draft.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Good fit Use it to brainstorm newsletter topics, shape personal experiences into educational articles, and write content for The Little Blue Report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nicepkg/ai-workflow/newsletter-coach
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add nicepkg/ai-workflow --skill newsletter-coach
Clone the repo
git clone --depth 1 https://github.com/nicepkg/ai-workflow

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for newsletter-coach

README.md
[![agentmods](https://agentmods.dev/badge/skills/nicepkg/ai-workflow/newsletter-coach.svg)](https://agentmods.dev/skills/nicepkg/ai-workflow/newsletter-coach)
Your own site
<a href="https://agentmods.dev/skills/nicepkg/ai-workflow/newsletter-coach"><img src="https://agentmods.dev/badge/skills/nicepkg/ai-workflow/newsletter-coach.svg" alt="Measured on agentmods" height="20"></a>
Per session 48 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,444 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00048 $0.03444
Opus 5 $0.00024 $0.01722
Sonnet 5 $0.00010 $0.00689
Haiku 4.5 $0.00005 $0.00344

Measured 8d ago against content hash 38dd795a4180, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

newsletter-coach scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

workflows/content-creator-workflow/.claude/skills/newsletter-coach/SKILL.md · 376 lines

How it starts

The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Newsletter Brainstorm - Writing Coach

RESOURCES

This skill includes supporting documents. Read them when needed during the process:

Resource When to Use Path
Idea Development Questions Phase 1 - When drilling deeper on experiences resources/idea-development-questions.md
Outliner Phase 5 - When creating subheads for different post types resources/outliner.md
Section Writer Phase 6 - When expanding sections with the 14 ways resources/section-writer.md
Newsletter Examples Phase 7 - For style reference and voice matching resources/newsletter-examples.md

Read each resource file at the start of its relevant phase to ensure you're following the full framework.


You are a writing coach who helps writers extract educational content from their daily experiences.

Conversation Flow

Ask one question per response. Wait for their answer, then ask the next question. This keeps momentum and avoids overwhelming the writer.

YOUR GOAL

Help them write educational nonfiction content (email newsletter, social post, blog article) by extracting insights from their experience. This could be lessons, mistakes, reasons, a new framework, model, beliefs or new way of thinking, a process, steps to do something, etc.

You're using their experiences as proof points for educational content.

THE 7-PHASE PROCESS

PHASE 1: GET THE ACTIONS AND DECISIONS

→ Read resources/idea-development-questions.md for the full question bank.

Figure out what happened.

Example questions:

  • Who was involved?
  • What exactly did you do?
  • When/where did this happen?
  • What was the problem?
  • How did you figure that out?
  • Why did you do it that way?
  • Why does that matter?
  • What did you try?
  • What made you decide to approach it like that?
  • What would most people do instead?
  • What happened as a result?
  • What worked? What didn't?
  • What did you learn from this?

When they mention something interesting, drill down. What solutions, processes, "hacks" do they use? Steps, pain points, mistakes, reasons?

Read the full file on GitHub · 376 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 8d ago First seen · 376 lines · 48 tokens per session scan A 38dd795a4180

Subscribe to this mod's changes

newsletter-coach is a skill published in the GitHub repository nicepkg/ai-workflow (282 stars, last pushed 7mo ago), licensed MIT. It adds 48 tokens to every session and 3,444 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

study-plan

A long-term study planner that divides learning into stages and adapts the schedule using practice results. It can also plan focused practice sessions for a specific number of questions or flashcards.

open-octo/octo-agent · 120 tokens

exam-forecast

An exam-pattern guide that compares several past papers from the same teacher or course. It identifies recurring topics, question formats, common traps, and changes over time, then estimates which areas may deserve more study.

open-octo/octo-agent · 134 tokens

outline-builder

A study aid that helps build an outline from a learner's notes, textbook excerpts, or an existing outline. It creates the structure and leaves gaps for the learner to fill rather than writing the lesson for them.

open-octo/octo-agent · 118 tokens

flashcards

A lightweight flashcard and review method for learning facts and concepts in a conversation. It uses Leitner boxes, a simple system that shows cards at increasing intervals as they are remembered.

open-octo/octo-agent · 121 tokens

weak-point-drill

A targeted practice workflow that finds the topics a learner repeatedly gets wrong and gives those topics more questions. It explains answers and tracks recurring mistakes across practice sessions.

open-octo/octo-agent · 130 tokens

product-help

Answer questions about how to use octo, or diagnose something that isn't working, by reading the product documentation. Use when the user asks "how do I...", "what is...", "where is the docs for...", any usage/help question about octo itself, or reports a problem — "not working", "won't start", "error", "connection…

open-octo/octo-agent · 91 tokens