菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/danielrosehill/Claude-Buttondown-Mgmt-Plugin --skill list-newsletters命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
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.
基于 SOC 职业分类
正在显示 SKILL.md
| name | list-newsletters |
| description | 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. |
DATA_ROOT="${CLAUDE_USER_DATA:-${XDG_DATA_HOME:-$HOME/.local/share}/claude-plugins}/buttondown-mgmt"
jq '.newsletters' "$DATA_ROOT/config.json"
Render as a compact table: slug, name, user_dir, default. Do not print API key references — they are pointers, not secrets, but also not relevant to a list view.
If config.json doesn't exist, tell the user to run onboard first.