Stats
Actions
Tags
From buttondown-mgmt
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.
How this skill is triggered — by the user, by Claude, or both
Slash command
/buttondown-mgmt:cli-referenceThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Upstream: https://github.com/buttondown/cli
Upstream: https://github.com/buttondown/cli
command -v buttondown >/dev/null && buttondown --version
If not installed, point the user at the upstream README for install instructions (it changes — don't hardcode here).
The CLI reads the API key from the env var documented upstream. Pick the right newsletter, resolve its api_key_ref, then export:
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/buttondown-mgmt"
SLUG="<newsletter-slug>" # or .default==true entry
REF=$(jq -r ".newsletters.\"$SLUG\".api_key_ref" "$DATA_ROOT/config.json")
export BUTTONDOWN_API_KEY="$(op read "$REF")"
Always print which newsletter the env was set for before running CLI commands so the user can catch a wrong-newsletter mistake.
Before constructing any CLI invocation, consult the cached docs (docs-lookup skill) for current command syntax — the CLI evolves.
Common operations:
user_dirnpx claudepluginhub danielrosehill/claude-code-plugins --plugin buttondown-mgmtOffers UI/UX design guidance for web and mobile with 50+ styles, 161 color palettes, 57 font pairings, and 99 UX guidelines across 10 stacks. Use for designing pages, components, color systems, or reviewing UI code.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.