# Cc Newsletter

> Write a newsletter issue built around one core idea, with a subject line, tight structure, and a single CTA.

- Skill: `matrixx0070/cc-newsletter` (Agent Skill)
- Install (CLI): `npx skillmds add matrixx0070/cc-newsletter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/matrixx0070/cc-newsletter/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: Matrixx0070 (https://skillmd.com/u/matrixx0070)
- Updated: 2026-08-19
- Page: https://skillmd.com/skills/matrixx0070/cc-newsletter

---


## When to use

Use this when you need a complete newsletter issue that respects the reader's time — one idea, a subject that earns the open, and a body that delivers before it asks. Good for solo creators, brand newsletters, and audience nurture.

**Not for:** cold outreach or sales sequences, multi-idea digests where you are just linking (this skill enforces one core idea), or subject-line-only requests (still write the body).

## Method

1. Pick ONE core idea. If you have three, ship three issues. Decision point: if you cannot name the single takeaway, do not send.
2. Write the subject line for the open, and preview text that extends it rather than repeating it. Keep the subject under ~50 characters so mobile does not truncate it.
3. Open with a hook in the first 1-2 lines — a scene, a stat, or a confession — because the preview and first line are what the reader actually sees.
4. Structure the body: setup (why this matters now), the idea (the meat, with a concrete example), and the turn (what to do with it). Keep paragraphs 1-3 lines.
5. Add one takeaway box or bolded line the skimmer can grab in two seconds.
6. Close with a single CTA aligned to the idea. Decision point: value first — never ask before you have given.

## Example

Core idea: "Batching content kills your best ideas." Subject: "I batched a month of posts. It backfired." Preview: "The hidden cost nobody warns you about." Body — Setup: everyone preaches batching. Idea: batching freezes your take weeks before it ships, so timely ideas die; example: a post written 3 weeks early missed a trend entirely. Turn: batch the production, not the thinking — draft angles weekly. CTA: "Reply with your batching horror story."

## Pitfalls

- Cramming multiple ideas so the reader remembers none.
- A subject line that describes the topic instead of creating a reason to open.
- Front-loading the ask before delivering value, training readers to skip.
- Dense paragraphs — email is skimmed, not studied.

## Output format

```
SUBJECT: <under ~50 chars>
PREVIEW TEXT: <extends the subject>

[HOOK — 1-2 lines]
<...>

[SETUP — why now]
<...>

[CORE IDEA + EXAMPLE]
<...>

> TAKEAWAY: <one skimmable line>

[TURN — what to do]
<...>

[CTA — single ask]
<...>
```