pp-resend

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Resend — Printing Press CLI

Prerequisites: Install the CLI

前置条件：安装CLI

This skill drives the

resend-pp-cli

binary. You must verify the CLI is installed before invoking any command from this skill. If it is missing, install it first:

Install via the Printing Press installer. It defaults binaries to

$HOME/.local/bin

on macOS/Linux and

%LOCALAPPDATA%\Programs\PrintingPress\bin

on Windows:

bash

npx -y @mvanhorn/printing-press-library install resend --cli-only

Verify:
```
resend-pp-cli --version
```
Ensure the reported install directory is on
```
$PATH
```
for the agent/runtime that will invoke this skill.

If the

npx

install fails (no Node, offline, etc.), fall back to a direct Go install (requires Go 1.26.3 or newer):

bash

go install github.com/mvanhorn/printing-press-library/library/productivity/resend/cmd/resend-pp-cli@latest

--version

reports "command not found" after install, the runtime cannot see the binary directory on

$PATH

. Do not proceed with skill commands until verification succeeds.

本Skill驱动

resend-pp-cli

二进制文件。在调用本Skill的任何命令之前，您必须确认CLI已安装。如果未安装，请先执行以下步骤：

通过Printing Press安装程序安装。在macOS/Linux上默认将二进制文件安装到
```
$HOME/.local/bin
```
，在Windows上默认安装到
```
%LOCALAPPDATA%\Programs\PrintingPress\bin
```
：
bash
```
npx -y @mvanhorn/printing-press-library install resend --cli-only
```
验证安装：
```
resend-pp-cli --version
```
确保报告的安装目录在将调用此Skill的Agent/运行时的
```
$PATH
```
中。

如果

npx

安装失败（无Node环境、离线等），可以回退到直接通过Go安装（需要Go 1.26.3或更高版本）：

bash

go install github.com/mvanhorn/printing-press-library/library/productivity/resend/cmd/resend-pp-cli@latest

如果安装后

--version

提示“command not found”，说明运行时无法在

$PATH

中找到二进制文件目录。在验证成功之前，请勿继续执行Skill命令。

When to Use This CLI

何时使用此CLI

Use this CLI when an agent needs to answer cross-resource questions about a Resend account that the dashboard or SDK cannot answer in one call — what did we send to a specific recipient, which audiences is a contact in, how does broadcast performance trend over time, what's the 7-day bounce rate. Stick with

npx resend send

for one-shot transactional sends or with React Email for templates; this CLI is the agent-facing companion, not a replacement.

当Agent需要回答关于Resend账户的跨资源问题，而这些问题无法通过仪表盘或SDK一次调用解决时，请使用此CLI——比如“我们给特定收件人发送了什么内容”、“某个联系人属于哪些受众”、“广播效果随时间的变化趋势如何”、“7天退信率是多少”。对于一次性事务性发送，请使用

npx resend send

；对于模板，请使用React Email；此CLI是面向Agent的配套工具，而非替代方案。

Unique Capabilities

独特功能

These capabilities aren't available in any other tool for this API.

这些功能是其他Resend API工具所不具备的。

Cross-resource queries over local state

基于本地状态的跨资源查询

emails to
— Every email sent to a single recipient address, with delivery status and timestamps, ordered newest-first.
Reach for this when an agent needs to reconstruct what a single user has received — support tickets, GDPR exports, dispute investigations.
bash
```
resend-pp-cli emails to <your-email> --json --select id,subject,status,sent_at
```
emails timeline
— Collapsed event chain for a single email: sent → delivered → opened → clicked → bounced, in one ordered table.
Use when debugging 'why didn't this arrive?' — one command shows whether it was sent, delivered, opened, or bounced and when.
bash
```
resend-pp-cli emails timeline 4ef9a417-d4ff-4ec5-9af2-c80a4d5d2c1f --json
```
audiences inventory
— Per-audience rollup: contact count, unsubscribed count, last-broadcast timestamp, recent open-rate.
Use before planning a campaign — quickly see which audiences are healthy and recently engaged.
bash
```
resend-pp-cli audiences inventory --json
```
contacts where
— Find every audience, segment, and topic a contact (by email or name) belongs to in one query.
Use when triaging unsubscribe requests, GDPR deletions, or 'why is bob getting this email?'.
bash
```
resend-pp-cli contacts where <contact-email> --json --select audience_name,subscribed
```

emails to
— 发送给单个收件人地址的所有邮件，包含送达状态和时间戳，按最新排序。
当Agent需要重建单个用户收到的所有内容时使用此命令——比如支持工单、GDPR导出、争议调查。
bash
```
resend-pp-cli emails to <your-email> --json --select id,subject,status,sent_at
```
emails timeline
— 单封邮件的完整事件链：发送 → 送达 → 打开 → 点击 → 退信，以有序表格展示。
用于调试“为什么邮件没收到”——一条命令即可显示邮件是否已发送、送达、打开或退信，以及对应的时间。
bash
```
resend-pp-cli emails timeline 4ef9a417-d4ff-4ec5-9af2-c80a4d5d2c1f --json
```
audiences inventory
— 按受众汇总：联系人数量、退订数量、最后一次广播时间、近期打开率。
在规划营销活动前使用——快速查看哪些受众是活跃的且近期有互动。
bash
```
resend-pp-cli audiences inventory --json
```
contacts where
— 通过一次查询找到某个联系人（按邮箱或姓名）所属的所有受众、细分群体和主题。
用于处理退订请求、GDPR删除或“为什么Bob会收到这封邮件”这类问题。
bash
```
resend-pp-cli contacts where <contact-email> --json --select audience_name,subscribed
```

Aggregate analytics from local store

基于本地存储的聚合分析

broadcasts performance
— Open / click / bounce rate across all broadcasts, sortable; not limited to a single broadcast or 30-day window.
Use to compare campaign performance across the lifetime of the account.
bash
```
resend-pp-cli broadcasts performance --json --select broadcasts,count,status
```
domains health
— Verification + DKIM/SPF/DMARC status across every domain in one table, flags missing or unverified records.
Use on call-out / deliverability incidents to confirm all sending domains are fully verified.
bash
```
resend-pp-cli domains health --json
```
deliverability summary
— Bounce rate, complaint rate, and suppression count over a rolling window (default 7d) computed from local event data.
Use weekly to monitor IP/domain reputation trends before they cause deliverability incidents.
bash
```
resend-pp-cli deliverability summary --window 7d --json
```

broadcasts performance
— 所有广播的打开/点击/退信率，可排序；不受限于单个广播或30天窗口。
用于比较账户生命周期内的营销活动效果。
bash
```
resend-pp-cli broadcasts performance --json --select broadcasts,count,status
```
domains health
— 所有域名的验证状态以及DKIM/SPF/DMARC状态，以表格形式展示，标记缺失或未验证的记录。
在处理送达率问题时使用——确认所有发送域名均已完全验证。
bash
```
resend-pp-cli domains health --json
```
deliverability summary
— 基于本地事件数据计算的滚动窗口（默认7天）内的退信率、投诉率和抑制数量。
每周使用一次，监控IP/域名信誉趋势，避免引发送达率问题。
bash
```
resend-pp-cli deliverability summary --window 7d --json
```

Operational hygiene

运维安全

api-keys rotation
— API keys sorted by age + last-used timestamp (joined from logs); flags stale keys older than N days.
Use during quarterly security reviews — find unused keys that should be rotated or revoked.
bash
```
resend-pp-cli api-keys rotation --older-than 90d --json
```

api-keys rotation
— 按创建时间和最后使用时间排序的API密钥（从日志中关联数据）；标记超过N天未使用的过期密钥。
在季度安全审查时使用——找出应轮换或撤销的未使用密钥。
bash
```
resend-pp-cli api-keys rotation --older-than 90d --json
```

Command Reference

命令参考

api-keys — Create and manage API Keys through the Resend API.

```
resend-pp-cli api-keys create
```
— Create a new API key
```
resend-pp-cli api-keys delete
```
— Remove an existing API key
```
resend-pp-cli api-keys list
```
— Retrieve a list of API keys

audiences — Deprecated: Use Segments instead. Create and manage Audiences through the Resend API.

```
resend-pp-cli audiences create
```
— Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.
```
resend-pp-cli audiences delete
```
— Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.
```
resend-pp-cli audiences get
```
— Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.
```
resend-pp-cli audiences list
```
— Deprecated: Use Segments instead. These endpoints still work, but will be removed in the future.

automations — Create and manage Automations through the Resend API.

```
resend-pp-cli automations create
```
— Create an automation
```
resend-pp-cli automations delete
```
— Delete an automation
```
resend-pp-cli automations get
```
— Retrieve a single automation
```
resend-pp-cli automations list
```
— Retrieve a list of automations
```
resend-pp-cli automations update
```
— Update an automation

broadcasts — Create and manage Broadcasts through the Resend API.

```
resend-pp-cli broadcasts create
```
— Create a broadcast
```
resend-pp-cli broadcasts delete
```
— Remove an existing broadcast that is in the draft status
```
resend-pp-cli broadcasts get
```
— Retrieve a single broadcast
```
resend-pp-cli broadcasts list
```
— Retrieve a list of broadcasts
```
resend-pp-cli broadcasts update
```
— Update an existing broadcast

contact-properties — Create and manage Contact Properties through the Resend API.

```
resend-pp-cli contact-properties create
```
— Create a new contact property
```
resend-pp-cli contact-properties delete
```
— Remove an existing contact property
```
resend-pp-cli contact-properties get
```
— Retrieve a single contact property
```
resend-pp-cli contact-properties list
```
— Retrieve a list of contact properties
```
resend-pp-cli contact-properties update
```
— Update an existing contact property

contacts — Create and manage Contacts through the Resend API.

```
resend-pp-cli contacts create
```
— Create a new contact
```
resend-pp-cli contacts delete
```
— Remove an existing contact by ID or email
```
resend-pp-cli contacts get
```
— Retrieve a single contact by ID or email
```
resend-pp-cli contacts list
```
— Retrieve a list of contacts
```
resend-pp-cli contacts update
```
— Update a single contact by ID or email

domains — Create and manage domains through the Resend API.

```
resend-pp-cli domains create
```
— Create a new domain
```
resend-pp-cli domains delete
```
— Remove an existing domain
```
resend-pp-cli domains get
```
— Retrieve a single domain
```
resend-pp-cli domains list
```
— Retrieve a list of domains
```
resend-pp-cli domains update
```
— Update an existing domain

emails — Start sending emails through the Resend API.

```
resend-pp-cli emails create
```
— Send an email
```
resend-pp-cli emails create-batch
```
— Trigger up to 100 batch emails at once.
```
resend-pp-cli emails get
```
— Retrieve a single email
```
resend-pp-cli emails get-receiving
```
— Retrieve a single received email
```
resend-pp-cli emails get-receiving-2
```
— Retrieve a list of attachments for a received email
```
resend-pp-cli emails get-receiving-3
```
— Retrieve a single attachment for a received email
```
resend-pp-cli emails list
```
— Retrieve a list of emails
```
resend-pp-cli emails list-receiving
```
— Retrieve a list of received emails
```
resend-pp-cli emails update
```
— Update a single email

events — Create and manage Events through the Resend API.

```
resend-pp-cli events create
```
— Create an event
```
resend-pp-cli events create-send
```
— Send an event
```
resend-pp-cli events delete
```
— Delete an event
```
resend-pp-cli events get
```
— Retrieve a single event
```
resend-pp-cli events list
```
— Retrieve a list of events
```
resend-pp-cli events update
```
— Update an event

logs — Retrieve API request logs through the Resend API.

```
resend-pp-cli logs get
```
— Retrieve a single log
```
resend-pp-cli logs list
```
— Retrieve a list of logs

segments — Create and manage Segments through the Resend API.

```
resend-pp-cli segments create
```
— Create a new segment
```
resend-pp-cli segments delete
```
— Remove an existing segment
```
resend-pp-cli segments get
```
— Retrieve a single segment
```
resend-pp-cli segments list
```
— Retrieve a list of segments

templates — Create and manage Templates through the Resend API.

```
resend-pp-cli templates create
```
— Create a template
```
resend-pp-cli templates delete
```
— Remove an existing template
```
resend-pp-cli templates get
```
— Retrieve a single template
```
resend-pp-cli templates list
```
— Retrieve a list of templates
```
resend-pp-cli templates update
```
— Update an existing template

topics — Create and manage Topics through the Resend API.

```
resend-pp-cli topics create
```
— Create a new topic
```
resend-pp-cli topics delete
```
— Remove an existing topic
```
resend-pp-cli topics get
```
— Retrieve a single topic
```
resend-pp-cli topics list
```
— Retrieve a list of topics
```
resend-pp-cli topics update
```
— Update an existing topic

webhooks — Create and manage Webhooks through the Resend API.

```
resend-pp-cli webhooks create
```
— Create a new webhook
```
resend-pp-cli webhooks delete
```
— Remove an existing webhook
```
resend-pp-cli webhooks get
```
— Retrieve a single webhook
```
resend-pp-cli webhooks list
```
— Retrieve a list of webhooks
```
resend-pp-cli webhooks update
```
— Update an existing webhook

api-keys — 通过Resend API创建和管理API密钥。

```
resend-pp-cli api-keys create
```
— 创建新的API密钥
```
resend-pp-cli api-keys delete
```
— 删除现有API密钥
```
resend-pp-cli api-keys list
```
— 获取API密钥列表

audiences — 已废弃：请使用Segments替代。通过Resend API创建和管理受众。

```
resend-pp-cli audiences create
```
— 已废弃：请使用Segments替代。这些端点当前仍可使用，但未来会被移除。
```
resend-pp-cli audiences delete
```
— 已废弃：请使用Segments替代。这些端点当前仍可使用，但未来会被移除。
```
resend-pp-cli audiences get
```
— 已废弃：请使用Segments替代。这些端点当前仍可使用，但未来会被移除。
```
resend-pp-cli audiences list
```
— 已废弃：请使用Segments替代。这些端点当前仍可使用，但未来会被移除。

automations — 通过Resend API创建和管理自动化流程。

```
resend-pp-cli automations create
```
— 创建自动化流程
```
resend-pp-cli automations delete
```
— 删除自动化流程
```
resend-pp-cli automations get
```
— 获取单个自动化流程
```
resend-pp-cli automations list
```
— 获取自动化流程列表
```
resend-pp-cli automations update
```
— 更新自动化流程

broadcasts — 通过Resend API创建和管理广播。

```
resend-pp-cli broadcasts create
```
— 创建广播
```
resend-pp-cli broadcasts delete
```
— 删除处于草稿状态的现有广播
```
resend-pp-cli broadcasts get
```
— 获取单个广播
```
resend-pp-cli broadcasts list
```
— 获取广播列表
```
resend-pp-cli broadcasts update
```
— 更新现有广播

contact-properties — 通过Resend API创建和管理联系人属性。

```
resend-pp-cli contact-properties create
```
— 创建新的联系人属性
```
resend-pp-cli contact-properties delete
```
— 删除现有联系人属性
```
resend-pp-cli contact-properties get
```
— 获取单个联系人属性
```
resend-pp-cli contact-properties list
```
— 获取联系人属性列表
```
resend-pp-cli contact-properties update
```
— 更新现有联系人属性

contacts — 通过Resend API创建和管理联系人。

```
resend-pp-cli contacts create
```
— 创建新联系人
```
resend-pp-cli contacts delete
```
— 通过ID或邮箱删除现有联系人
```
resend-pp-cli contacts get
```
— 通过ID或邮箱获取单个联系人
```
resend-pp-cli contacts list
```
— 获取联系人列表
```
resend-pp-cli contacts update
```
— 通过ID或邮箱更新单个联系人

domains — 通过Resend API创建和管理域名。

```
resend-pp-cli domains create
```
— 创建新域名
```
resend-pp-cli domains delete
```
— 删除现有域名
```
resend-pp-cli domains get
```
— 获取单个域名
```
resend-pp-cli domains list
```
— 获取域名列表
```
resend-pp-cli domains update
```
— 更新现有域名

emails — 通过Resend API开始发送邮件。

```
resend-pp-cli emails create
```
— 发送邮件
```
resend-pp-cli emails create-batch
```
— 一次性触发最多100批量邮件。
```
resend-pp-cli emails get
```
— 获取单个邮件
```
resend-pp-cli emails get-receiving
```
— 获取单个收到的邮件
```
resend-pp-cli emails get-receiving-2
```
— 获取收到邮件的附件列表
```
resend-pp-cli emails get-receiving-3
```
— 获取收到邮件的单个附件
```
resend-pp-cli emails list
```
— 获取邮件列表
```
resend-pp-cli emails list-receiving
```
— 获取收到的邮件列表
```
resend-pp-cli emails update
```
— 更新单个邮件

events — 通过Resend API创建和管理事件。

```
resend-pp-cli events create
```
— 创建事件
```
resend-pp-cli events create-send
```
— 发送事件
```
resend-pp-cli events delete
```
— 删除事件
```
resend-pp-cli events get
```
— 获取单个事件
```
resend-pp-cli events list
```
— 获取事件列表
```
resend-pp-cli events update
```
— 更新事件

logs — 通过Resend API获取API请求日志。

```
resend-pp-cli logs get
```
— 获取单个日志
```
resend-pp-cli logs list
```
— 获取日志列表

segments — 通过Resend API创建和管理细分群体。

```
resend-pp-cli segments create
```
— 创建新的细分群体
```
resend-pp-cli segments delete
```
— 删除现有细分群体
```
resend-pp-cli segments get
```
— 获取单个细分群体
```
resend-pp-cli segments list
```
— 获取细分群体列表

templates — 通过Resend API创建和管理模板。

```
resend-pp-cli templates create
```
— 创建模板
```
resend-pp-cli templates delete
```
— 删除现有模板
```
resend-pp-cli templates get
```
— 获取单个模板
```
resend-pp-cli templates list
```
— 获取模板列表
```
resend-pp-cli templates update
```
— 更新现有模板

topics — 通过Resend API创建和管理主题。

```
resend-pp-cli topics create
```
— 创建新主题
```
resend-pp-cli topics delete
```
— 删除现有主题
```
resend-pp-cli topics get
```
— 获取单个主题
```
resend-pp-cli topics list
```
— 获取主题列表
```
resend-pp-cli topics update
```
— 更新现有主题

webhooks — 通过Resend API创建和管理Webhook。

```
resend-pp-cli webhooks create
```
— 创建新Webhook
```
resend-pp-cli webhooks delete
```
— 删除现有Webhook
```
resend-pp-cli webhooks get
```
— 获取单个Webhook
```
resend-pp-cli webhooks list
```
— 获取Webhook列表
```
resend-pp-cli webhooks update
```
— 更新现有Webhook

Finding the right command

找到合适的命令

When you know what you want to do but not which command does it, ask the CLI directly:

bash

resend-pp-cli which "<capability in your own words>"

which

resolves a natural-language capability query to the best matching command from this CLI's curated feature index. Exit code

means at least one match; exit code

means no confident match — fall back to

--help

or use a narrower query.

当您知道要做什么但不知道用哪个命令时，可以直接询问CLI：

bash

resend-pp-cli which "<用您自己的话描述功能>"

which

命令会将自然语言的功能查询解析为与此CLI精选功能索引最匹配的命令。退出码

表示至少有一个匹配项；退出码

表示没有确定的匹配项——请回退到

--help

或使用更具体的查询。

Recipes

使用示例

Reconstruct what a user has received

重建用户收到的所有内容

bash

resend-pp-cli emails to user@example.com --json --select id,subject,status,sent_at,opened_at --limit 50

Use this for support tickets and GDPR exports — every email sent to one recipient, with delivery state.

bash

resend-pp-cli emails to user@example.com --json --select id,subject,status,sent_at,opened_at --limit 50

用于支持工单和GDPR导出——发送给单个收件人的所有邮件，包含送达状态。

Pre-campaign audience check

营销活动前的受众检查

bash

resend-pp-cli audiences inventory --json --select name,contact_count,unsubscribed_count,last_broadcast_at

Run before scheduling a broadcast — surfaces audiences with high unsubscribe rates or stale engagement.

bash

resend-pp-cli audiences inventory --json --select name,contact_count,unsubscribed_count,last_broadcast_at

在安排广播前运行——显示退订率高或互动不活跃的受众。

Weekly deliverability review

每周送达率审查

bash

resend-pp-cli deliverability summary --window 7d --agent --select bounce_rate,complaint_rate,suppression_count

Trend snapshot for IP/domain reputation; pipe through

jq

to alert on threshold breaches.

bash

resend-pp-cli deliverability summary --window 7d --agent --select bounce_rate,complaint_rate,suppression_count

IP/域名信誉的趋势快照；可通过管道传递给

jq

，在超过阈值时发出警报。

Audit stale API keys

审计过期API密钥

bash

resend-pp-cli api-keys rotation --older-than 90d --json --select name,created_at,last_used_at

Find unused keys during quarterly security reviews.

bash

resend-pp-cli api-keys rotation --older-than 90d --json --select name,created_at,last_used_at

在季度安全审查时查找未使用的密钥。

Search every sent email for a phrase

搜索所有已发送邮件中的特定短语

bash

resend-pp-cli search 'password reset' --json --select id,subject,to,sent_at

FTS5-backed; needs

sync --full

first.

bash

resend-pp-cli search 'password reset' --json --select id,subject,to,sent_at

基于FTS5实现；需要先执行

sync --full

。

Auth Setup

认证设置

Run

resend-pp-cli auth setup

for the URL and steps to obtain a token (add

--launch

to open the URL). Then store it:

bash

resend-pp-cli auth set-token YOUR_TOKEN_HERE

Or set

RESEND_API_KEY

as an environment variable.

Run

resend-pp-cli doctor

to verify setup.

运行

resend-pp-cli auth setup

获取获取令牌的URL和步骤（添加

--launch

可打开URL）。然后存储令牌：

bash

resend-pp-cli auth set-token YOUR_TOKEN_HERE

或者将

RESEND_API_KEY

设置为环境变量。

运行

resend-pp-cli doctor

验证设置是否正确。

Agent Mode

Agent模式

Add

--agent

to any command. Expands to:

--json --compact --no-input --no-color --yes

Pipeable — JSON on stdout, errors on stderr
Filterable —
```
--select
```
keeps a subset of fields. Dotted paths descend into nested structures; arrays traverse element-wise. Critical for keeping context small on verbose APIs:
bash
```
resend-pp-cli api-keys list --agent --select id,name,status
```
Previewable —
```
--dry-run
```
shows the request without sending
Offline-friendly — sync/search commands can use the local SQLite store when available
Non-interactive — never prompts, every input is a flag
Explicit retries — use
```
--idempotent
```
only when an already-existing create should count as success, and
```
--ignore-missing
```
only when a missing delete target should count as success

在任何命令后添加

--agent

。等效于：

--json --compact --no-input --no-color --yes

。

可管道化 — 标准输出为JSON，错误输出到标准错误
可过滤 —
```
--select
```
保留字段的子集。点路径可深入嵌套结构；数组可遍历元素。对于冗长的API，这是保持上下文简洁的关键：
bash
```
resend-pp-cli api-keys list --agent --select id,name,status
```
可预览 —
```
--dry-run
```
显示请求但不发送
离线友好 — 同步/搜索命令在可用时可使用本地SQLite存储
非交互式 — 从不提示，所有输入均为标志
显式重试 — 仅当已存在的创建操作应视为成功时使用
```
--idempotent
```
，仅当缺失的删除目标应视为成功时使用
```
--ignore-missing
```

Response envelope

响应信封

Commands that read from the local store or the API wrap output in a provenance envelope:

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

Parse

.results

for data and

.meta.source

to know whether it's live or local. A human-readable

N results (live)

summary is printed to stderr only when stdout is a terminal — piped/agent consumers get pure JSON on stdout.

从本地存储或API读取数据的命令会将输出包装在来源信封中：

json

{
  "meta": {"source": "live" | "local", "synced_at": "...", "reason": "..."},
  "results": <data>
}

解析

.results

获取数据，

.meta.source

可判断数据是实时的还是本地的。仅当标准输出为终端时，才会向标准错误输出人类可读的

N results (live)

摘要；管道/Agent消费者仅会在标准输出获取纯JSON。

Agent Feedback

Agent反馈

When you (or the agent) notice something off about this CLI, record it:

resend-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
resend-pp-cli feedback --stdin < notes.txt
resend-pp-cli feedback list --json --limit 10

Entries are stored locally at

~/.resend-pp-cli/feedback.jsonl

. They are never POSTed unless

RESEND_FEEDBACK_ENDPOINT

is set AND either

--send

is passed or

RESEND_FEEDBACK_AUTO_SEND=true

. Default behavior is local-only.

Write what surprised you, not a bug report. Short, specific, one line: that is the part that compounds.

当您（或Agent）发现此CLI存在问题时，请记录：

resend-pp-cli feedback "the --since flag is inclusive but docs say exclusive"
resend-pp-cli feedback --stdin < notes.txt
resend-pp-cli feedback list --json --limit 10

反馈条目存储在本地

~/.resend-pp-cli/feedback.jsonl

中。除非设置了

RESEND_FEEDBACK_ENDPOINT

且传递了

--send

或设置了

RESEND_FEEDBACK_AUTO_SEND=true

，否则永远不会通过POST发送。默认行为仅存储在本地。

请写下让您感到意外的内容，而不是错误报告。简短、具体、一句话：这才是有价值的部分。

Output Delivery

输出交付

Every command accepts

--deliver <sink>

. The output goes to the named sink in addition to (or instead of) stdout, so agents can route command results without hand-piping. Three sinks are supported:

Sink	Effect
`stdout`	Default; write to stdout only
`file:<path>`	Atomically write output to `<path>` (tmp + rename)
`webhook:<url>`	POST the output body to the URL ( `application/json` or `application/x-ndjson` when `--compact` )

Unknown schemes are refused with a structured error naming the supported set. Webhook failures return non-zero and log the URL + HTTP status on stderr.

每个命令都支持

--deliver <sink>

。输出会发送到指定的sink，除了（或代替）标准输出，因此Agent无需手动管道即可路由命令结果。支持三种sink：

Sink	效果
`stdout`	默认；仅写入标准输出
`file:<path>`	原子性地将输出写入 `<path>` （先写入临时文件再重命名）
`webhook:<url>`	将输出体POST到指定URL（当使用 `--compact` 时为 `application/json` 或 `application/x-ndjson` ）

未知的协议会被拒绝，并返回结构化错误，列出支持的协议集。Webhook失败时返回非零退出码，并在标准错误中记录URL和HTTP状态。

Named Profiles

命名配置文件

A profile is a saved set of flag values, reused across invocations. Use it when a scheduled agent calls the same command every run with the same configuration - HeyGen's "Beacon" pattern.

resend-pp-cli profile save briefing --json
resend-pp-cli --profile briefing api-keys list
resend-pp-cli profile list --json
resend-pp-cli profile show briefing
resend-pp-cli profile delete briefing --yes

Explicit flags always win over profile values; profile values win over defaults.

agent-context

lists all available profiles under

available_profiles

so introspecting agents discover them at runtime.

配置文件是一组保存的标志值，可在多次调用中重复使用。当调度Agent每次运行都使用相同配置调用同一命令时使用此功能——即HeyGen的“Beacon”模式。

resend-pp-cli profile save briefing --json
resend-pp-cli --profile briefing api-keys list
resend-pp-cli profile list --json
resend-pp-cli profile show briefing
resend-pp-cli profile delete briefing --yes

显式标志始终优先于配置文件值；配置文件值优先于默认值。

agent-context

会在

available_profiles

下列出所有可用配置文件，以便自省Agent在运行时发现它们。

Exit Codes

退出码

Code	Meaning
0	Success
2	Usage error (wrong arguments)
3	Resource not found
4	Authentication required
5	API error (upstream issue)
7	Rate limited (wait and retry)
10	Config error

代码	含义
0	成功
2	使用错误（参数错误）
3	资源未找到
4	需要认证
5	API错误（上游问题）
7	速率限制（等待后重试）
10	配置错误

Argument Parsing

参数解析

Parse

$ARGUMENTS

Empty,
help
, or
--help
→ show
```
resend-pp-cli --help
```
output
Starts with
install
→ ends with
```
mcp
```
→ MCP installation; otherwise → see Prerequisites above
Anything else → Direct Use (execute as CLI command with
```
--agent
```
)

解析

$ARGUMENTS

：

为空、
help
或
--help
→ 显示
```
resend-pp-cli --help
```
输出
以
install
开头 → 如果以
```
mcp
```
结尾 → MCP安装；否则 → 请参阅上方的前置条件
其他情况 → 直接使用（以
```
--agent
```
标志执行CLI命令）

MCP Server Installation

MCP服务器安装

Install the MCP binary from this CLI's published public-library entry or pre-built release, then register it:

bash

claude mcp add resend-pp-mcp -- resend-pp-mcp

Verify:

claude mcp list

从此CLI的已发布公共库条目或预构建版本安装MCP二进制文件，然后注册：

bash

claude mcp add resend-pp-mcp -- resend-pp-mcp

验证：

claude mcp list

Direct Use

直接使用

Check if installed:
```
which resend-pp-cli
```
If not found, offer to install (see Prerequisites at the top of this skill).
Match the user query to the best command from the Unique Capabilities and Command Reference above.

Execute with the

--agent

flag:

bash

resend-pp-cli <command> [subcommand] [args] --agent

If ambiguous, drill into subcommand help:
```
resend-pp-cli <command> --help
```
.

检查是否已安装：
```
which resend-pp-cli
```
如果未找到，提供安装选项（请参阅顶部的前置条件）。
将用户查询与上方“独特功能”和“命令参考”中的最佳命令匹配。

使用

--agent

标志执行：

bash

resend-pp-cli <command> [subcommand] [args] --agent

如果存在歧义，查看子命令帮助：
```
resend-pp-cli <command> --help
```
。