buttondown-mgmt

Register an additional Buttondown newsletter alongside any already configured. Captures slug, display name, API key reference, user directory, and optional default flag. Use when the user has a new newsletter to manage from the same Claude Code setup.

Add a reusable email template to the local template store. Templates are markdown files with YAML frontmatter (subject, audience, scope, tags) used as starting points for new emails. Scope is either `global` (any newsletter) or a specific newsletter slug.

Reference and lightweight wrapper for the official Buttondown CLI (github.com/buttondown/cli). Use when the user prefers CLI operations over raw API calls — sending drafts, listing subscribers, managing emails from the terminal. Resolves the API key for the active newsletter.

Look up Buttondown documentation in the local cache before answering API questions or making API calls. Use grep/read against $CLAUDE_USER_DATA/buttondown-mgmt/cache/docs to ground responses in the canonical docs rather than training-data recall.

List recent Buttondown emails (drafts, scheduled, sent) for a specific newsletter via the Buttondown API. Grounds the request shape in the locally cached docs before calling.

List all Buttondown newsletters registered with the plugin — slug, display name, user directory, and which one is the default. Read-only; use when the user asks "which newsletters are configured" or to look up a slug before invoking another skill.

List all email templates in the local template store — name, subject, scope (global or newsletter slug), tags, last updated. Read-only.

First-run setup for buttondown-mgmt. Registers one or more Buttondown newsletters (each with its own API key reference and user directory), provisions the shared template store, and clones the official Buttondown docs into the local cache.

Clone or pull the official Buttondown documentation repository (github.com/buttondown/docs) into the plugin's local cache. The cached docs are the canonical source of truth for any Buttondown API, CLI, or feature question — consult them before answering or making API calls.

Create a draft or send a Buttondown email for a specific newsletter, optionally starting from a local template. Confirms before any send — sends are not reversible.

Update an existing template in the local template store — edit body, change subject, scope, audience, or tags. Bumps the `updated` timestamp in frontmatter.