Skill

send-email

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.

npx claudepluginhub danielrosehill/claude-code-plugins --plugin buttondown-mgmt

Tool Access

This skill uses the workspace's default tool permissions.

Preview

1. **Pick newsletter.** If named, resolve slug against `config.json`. Otherwise use default; if no default and multiple configured, ask.

SKILL.md

Similar Skills

angular-new-app

100.1k

Creates new Angular apps using Angular CLI with flags for routing, SSR, SCSS, prefixes, and AI config. Follows best practices for modern TypeScript/Angular development. Use when starting Angular projects.

angular-angular-1

ui-ux-pro-max

72.7k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-cli

53.8k

Executes ctx7 CLI to fetch up-to-date library documentation, manage AI coding skills (install/search/generate/remove/suggest), and configure Context7 MCP. Useful for current API refs, skill handling, or agent setup.

3 files

upstash-context7-1

Stats

Stars0

Forks0

Last CommitApr 29, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Send Email

Steps

Pick newsletter. If named, resolve slug against config.json. Otherwise use default; if no default and multiple configured, ask.

Source. One of:

Path to a markdown file (default location: <newsletter.user_dir>/drafts/)
A template name from $DATA_ROOT/templates/ (filtered to scope: global or matching the chosen newsletter slug). If templated, prompt for any {{placeholders}} in the subject and body and substitute before showing the preview.

Docs lookup. Run docs-lookup for the create-email endpoint and publish/send semantics. Confirm current required fields (subject, body, status values like draft / scheduled / about_to_send).

Show resolved payload — newsletter, subject, body preview (first 30 lines), audience/segments, scheduled time if any.

Confirm before send. Status draft proceeds. Statuses that imply an actual send require explicit user confirmation in this turn — don't assume prior approval covers a new send. Sends fan out to subscribers and cannot be unsent.

Call the API with the API key resolved from the chosen newsletter's api_key_ref.

Archive. Write the request payload + response to <newsletter.user_dir>/sent/<date>-<slug>.json. If the email originated from a template, include the template name in the archive metadata.

Send Email

Steps

Pick newsletter. If named, resolve slug against config.json. Otherwise use default; if no default and multiple configured, ask.
Source. One of:
- Path to a markdown file (default location: <newsletter.user_dir>/drafts/)
- A template name from $DATA_ROOT/templates/ (filtered to scope: global or matching the chosen newsletter slug). If templated, prompt for any {{placeholders}} in the subject and body and substitute before showing the preview.
Docs lookup. Run docs-lookup for the create-email endpoint and publish/send semantics. Confirm current required fields (subject, body, status values like draft / scheduled / about_to_send).
Show resolved payload — newsletter, subject, body preview (first 30 lines), audience/segments, scheduled time if any.
Confirm before send. Status draft proceeds. Statuses that imply an actual send require explicit user confirmation in this turn — don't assume prior approval covers a new send. Sends fan out to subscribers and cannot be unsent.
Call the API with the API key resolved from the chosen newsletter's api_key_ref.
Archive. Write the request payload + response to <newsletter.user_dir>/sent/<date>-<slug>.json. If the email originated from a template, include the template name in the archive metadata.