# Beacon Newsletter

> **When to use.** When the user runs (or wants to run) a recurring newsletter as an owned-audience asset, distinct from triggered email sequences.

- Skill: `ferroxlabs/beacon-newsletter` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add ferroxlabs/beacon-newsletter`
- Raw SKILL.md: https://api.skillmd.com/api/skills/ferroxlabs/beacon-newsletter/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: FerroxLabs (https://skillmd.com/u/ferroxlabs)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/ferroxlabs/beacon-newsletter

---


# newsletter

**When to use.** When the user runs (or wants to run) a recurring newsletter as an owned-audience asset, distinct from triggered email sequences.

**Procedure (stub).** Newsletter is a cross-stage owned channel — its job is to maintain mental availability between purchase windows. Pick a cadence (weekly is the common floor for active growth, biweekly is the sustainable minimum), a single recurring format (essay, link round-up, framework breakdown, behind-the-scenes), and one CTA per send. Treat the subject line as a separate craft item routed to Copy. Measure by long-run open-rate trend, click-through to the single weekly CTA, and reply rate (proxy for relationship depth). Coordinate with email-sequences skill so triggered flows and newsletter sends do not overlap on a given subscriber on a given day.

**Status.** Default tier: user-toggle. Full procedure deferred to Phase 2. Until then, the channel-strategy skill handles cross-channel decisions.