CustomerNewsletter: Skill for Claude Code

Newsletter Assembly

Assemble Phase 3 curated sections and Phase 2 events into a complete newsletter.

Quick Start

1. Read Phase 3 curated sections from workspace/newsletter_phase3_curated_sections_*.md
2. Read Phase 2 events from workspace/newsletter_phase2_events_*.md
3. Create introduction with 2-3 key highlights
4. Assemble sections in mandatory order
5. Add standard closing, changelog links, YouTube playlists
6. Enforce heading structure and density targets for long windows
7. Write output to output/YYYY-MM_month_newsletter.md

Inputs

• Phase 3 Curated Sections: workspace/newsletter_phase3_curated_sections_*.md (required)
• Phase 2 Events: workspace/newsletter_phase2_events_*.md (required)

Output

• File: output/YYYY-MM_month_newsletter.md
• Complete newsletter ready for distribution

Core Workflow

Step 1: Create Introduction

Use the standard template with 2-3 dynamic highlights:

This is a personally curated newsletter for my customers, focused on the most
relevant updates and resources from GitHub this month. Highlights for this month
include [2-3 key highlights]. If you have any feedback or want to dive deeper
into any topic, please let me know. Feel free to share this newsletter with
others on your team as well. You can find an archive of past newsletters
[here](https://github.com/briancl2/CustomerNewsletter).

Select highlights from the most impactful GA features or major enterprise announcements in the curated sections.

Step 2: Assemble in Mandatory Order

See section-ordering.md for the required section sequence.

1. Introduction (with highlights)
2. Monthly Announcement / Lead Section (if present in Phase 3)
3. Copilot (mandatory heading shape: # Copilot with ## Latest Releases, plus Copilot at Scale with changelogs)
4. Enterprise and Security Updates (H1 for Feb benchmark-style runs)
5. Resources and Best Practices (H1 when sources exist)
6. Webinars, Events, and Recordings (H1, with H2 subheadings from Phase 2)
7. Closing