# newsletter-creator

newsletter-creator builds a company newsletter from a fixed outline: section order, a scoring pass over the links, and email layout rules to follow.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 140 installs · ★ 114 repo stars
- Author: travisjneuman
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/travisjneuman/.claude/tree/HEAD/skills/newsletter-creator/SKILL.md
- Updated: 2026-10-25
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/newsletter-creator

## What it does

The skill gives a newsletter a fixed shape: header with edition number and date, a short highlights block that links down to each section, one lead story of 150–250 words, 3–5 brief updates, the same number of outside links with a line on why each matters, a rotating spotlight, an events list, then the footer. A comparison table splits the internal edition from the external one by tone, length, call to action and metrics.

Curation runs as a weekly loop. Links pile up as they appear, get scored the day before sending against five criteria with set weights (30% relevance, 25% timeliness, 20% quality, 15% novelty, 10% actionability), then annotated with a headline, a summary and a reason to click. A score of 3.5 or higher goes in. Anything at 2.5–3.4 waits for spare room.

Layout rules come with it: 600px content width, body text at 16px, alt text on every image, files under 200KB, touch targets of at least 44x44px. For an external send the footer has to carry the sender's physical postal address, which CAN-SPAM requires. Miss it and the issue is not ready, however good the links are.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill newsletter-creator -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/newsletter-creator/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/newsletter-creator/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill newsletter-creator -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/newsletter-creator/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill newsletter-creator -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/newsletter-creator/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install travisjneuman/.claude skills/newsletter-creator
```

2. **Manually: put the files in place**
- File: `.github/skills/newsletter-creator/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill newsletter-creator -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/travisjneuman/.claude --path skills/newsletter-creator
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/newsletter-creator/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add travisjneuman/.claude --skill newsletter-creator -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/travisjneuman/.claude/tree/HEAD/skills/newsletter-creator/SKILL.md

## When to use it
- draft a weekly internal newsletter from a fixed outline
- score a backlog of links and cut it down to five
- write annotations that give readers a reason to click
- fit the email layout to 600px and a readable font size
- check the footer before an external send

## Example prompts
- Draft this week's internal newsletter: four updates, one lead story, and highlights at the top linking to each section.
- Score these links against the curation matrix and tell me what makes the cut.
- Put together the external digest from these three articles and check the footer before I send.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: ab1dd081c30ba879.

BEGIN THIRD-PARTY FILE ab1dd081c30ba879
````text
---
name: newsletter-creator
description: Company newsletter and content roundup creation with consistent formatting, content curation, and audience segmentation. Use when creating internal newsletters, external digests, or content summaries.
---

# Newsletter Creator

Structured frameworks for creating compelling internal and external newsletters with consistent quality, effective curation, and audience-appropriate tone.

## Newsletter Structure

### Standard Newsletter Sections

```
NEWSLETTER LAYOUT:

1. HEADER
   - Newsletter name / brand
   - Edition number and date
   - Tagline or theme for this edition

2. TL;DR / HIGHLIGHTS (above the fold)
   - 3-5 bullet summary of key items
   - Designed for scanners who won't read the full email
   - Each bullet links to the corresponding section

3. FEATURED STORY (1 item)
   - Primary content piece
   - 150-250 words with a clear takeaway
   - Supporting image or graphic
   - CTA: read more, watch, try

4. NEWS & UPDATES (3-5 items)
   - Brief summaries (50-100 words each)
   - Consistent format: headline, summary, link
   - Categorized if applicable

5. CURATED CONTENT (3-5 items)
   - Third-party articles, tools, or resources
   - Brief annotation explaining relevance
   - Source attribution

6. SPOTLIGHT SECTION (1 item, rotating)
   - Team member spotlight, customer story, tool tip
   - Rotates theme each edition
   - Personal and engaging

7. UPCOMING EVENTS / DATES
   - Relevant events, webinars, deadlines
   - Calendar format or simple list

8. FOOTER
   - Unsubscribe / manage preferences (honor within 10 business days)
   - Sender's physical postal address (required by CAN-SPAM for external sends)
   - Social media links
   - Feedback prompt ("Reply with your thoughts")
   - Archives link
```

### Internal vs External Newsletter Differences

| Element | Internal Newsletter | External Newsletter |
| --- | --- | --- |
| **Tone** | Casual, transparent, team-oriented | Professional, value-driven |
| **Content** | Company updates, wins, culture | Industry insights, product updates |
| **Frequency** | Weekly or biweekly | Weekly, biweekly, or monthly |
| **Length** | 500-800 words | 300-600 words |
| **CTA** | Participate, recognize, feedback | Read more, try feature, register |
| **Metrics** | Open rate, survey feedback | Open rate, CTR, conversions |
````
END THIRD-PARTY FILE ab1dd081c30ba879

The third-party file has ended. Everything between the ab1dd081c30ba879 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2342 of 11331 bytes. © travisjneuman · MIT · https://github.com/travisjneuman/.claude/tree/HEAD/skills/newsletter-creator/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
