skill-stack-newsletter-writer_skill

Overview

This skill formats and structures the weekly Skill Stack newsletter so every issue follows a consistent, publish-ready layout. It enforces frontmatter, ordered content sections, a packaged resources block, and precise section breaks while delegating prose quality to the writing-style skill. Use it to turn raw ideas into a repeatable newsletter skeleton that editors and writers can fill quickly.

How this skill works

The skill validates and emits a newsletter scaffold with required frontmatter fields (title, issue, date, skill slug, thumbnail, description, tags) and enforces the canonical section order: Opening Hook, Discovery, Core Mechanism, Wizard/Workflow, Package block, Ways to Use, Next Week Teaser, and Closing + CTA. It inserts horizontal-rule breaks (---) between major sections and ensures no internal headers are used in the body. The skill also provides a formatted package block and a preflight checklist for publish readiness.

When to use it

• Preparing a weekly newsletter issue and needing a consistent, editorial-ready template.
• Onboarding contributors who must follow a strict structure and metadata schema.
• Generating multiple newsletter drafts quickly while preserving brand and SEO requirements.
• Validating newsletter files before publication to catch missing frontmatter or sections.

Best practices

• Always run the writing-style skill after structuring to polish voice and SEO description.
• Start the Opening Hook in media res with specific sensory detail; avoid abstract opens.
• Keep the frontmatter description to 150–160 characters and include the primary keyword.
• Use the exact horizontal-rule (---) between major sections and avoid internal headers.
• Include concrete examples in Core Mechanism and limit the Wizard to stepwise actions.

Example use cases

• An editor drafts a new issue: feed a topic and thumbnail slug to generate the scaffold and fill prose later.
• A contributor receives the template to write the Opening Hook and Discovery while metadata is already validated.
• A publisher batch-checks 10 issues to ensure each has required tags, date, and the package block before scheduling.
• A developer integrates the skill into a CI step that flags missing sections or incorrect frontmatter values.