emailmd
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Send, receive, edit and react to WhatsApp messages from your own number. OAuth or API key sign-in.
此项在“连接 AI 的应用”标签中,该标签不使用星标,按以下顺序排列
| 1. 在 Claude 连接器目录中 | 否 | |
|---|---|---|
| 2. 团队实测过 | 否 | |
| 3. 适合泰国用户 | 否 | |
| 4. 不计星标的使用量 | 20/100 | 热度 0 · 新鲜度 12 · 仍在响应 8 · 用户喜欢 +0 |
| 5. 登记日期 | 2026-11-13 |
用户喜欢: 0 · 最多加 5 分(每人 1 分),不能用钱买。
质量: 基础检查通过 4/4 项(仅展示,不用于排序)
选择你使用的 AI 应用,然后复制设置。
用一句话让 AI 帮你安装
请帮我安装 Turbo Notify: WhatsApp for AI agents。按照 https://mcp.popnx.com/i/turbonotify-turbo-notify.md 操作,先把命令给我看,等我同意后再运行。粘贴到能在你电脑上工作的 AI(如 Claude Code、Cursor)。它会读取我们的步骤,先给你看命令,等你同意。无需密钥,无需注册。 · 查看 AI 会读取的全文
通过 4/4 项检查 · 你的提问会经过开发者的服务器(mcp.turbonotify.com) · ✓ 命令已检查 2026年11月13日
第一步:你用哪个 AI?
选择你用的应用,步骤会显示在下方。
可连接 Claude · 约 2 分钟
不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加
CustomizeConnectors
把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue
Turbo Notify: WhatsApp for AI agentshttps://mcp.turbonotify.com在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add
+ConnectorsTurbo Notify: WhatsApp for AI agents
用 Turbo Notify: WhatsApp for AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude 说正在使用 Turbo Notify: WhatsApp for AI agents,或回答中出现 Turbo Notify: WhatsApp for AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
能否连接 ChatGPT 取决于方案
完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页
Plugins+Add custom MCP server
输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin
Turbo Notify: WhatsApp for AI agentshttps://mcp.turbonotify.com开启新聊天,输入前先从插件列表中选择 Turbo Notify: WhatsApp for AI agents
用 Turbo Notify: WhatsApp for AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 ChatGPT 说正在使用 Turbo Notify: WhatsApp for AI agents,或回答中出现 Turbo Notify: WhatsApp for AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Claude Code · 约 2 分钟
不需要密钥,不用安装程序
Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell
claude mcp add --transport http --scope user turbo-notify https://mcp.turbonotify.com应能看到 Turbo Notify: WhatsApp for AI agents 在列表中并显示已连接
用 Turbo Notify: WhatsApp for AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Claude Code 说正在使用 Turbo Notify: WhatsApp for AI agents,或回答中出现 Turbo Notify: WhatsApp for AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同
可连接 Cursor · 约 2 分钟
不需要密钥,不用安装程序
用 Turbo Notify: WhatsApp for AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 Cursor 说正在使用 Turbo Notify: WhatsApp for AI agents,或回答中出现 Turbo Notify: WhatsApp for AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同
可连接 VS Code · 约 2 分钟
不需要密钥,不用安装程序
用 Turbo Notify: WhatsApp for AI agents 告诉我你能帮我做什么,然后做一件给我看✓ 如果 VS Code 说正在使用 Turbo Notify: WhatsApp for AI agents,或回答中出现 Turbo Notify: WhatsApp for AI agents 的工具名称,就表示连接成功
菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同
其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看
通过网页连接的应用使用的地址
https://mcp.turbonotify.comJSON 设置在下方“开发者专用”中
Claude Code
claude mcp add --transport http --scope user turbo-notify https://mcp.turbonotify.comCursor (~/.cursor/mcp.json)
{
"mcpServers": {
"turbo-notify": {
"url": "https://mcp.turbonotify.com"
}
}
}VS Code (mcp.json)
{
"servers": {
"turbo-notify": {
"type": "http",
"url": "https://mcp.turbonotify.com"
}
}
}说明仍为英文原文。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。
通过互联网连接,适用于
ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast
工具名称和描述与服务器在 2026年11月15日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。
send_textSend a WhatsApp text message. Set exactly one recipient: `number`, `group_id`, or `contact_id`. Writing `@ ` in the text mentions that person, for example `@5511999999999`. The platform detects it automatically; there is no separate mentions argument. This is also how to answer t
send_mediaSend media by URL: an image, video, audio clip, document or sticker. Set exactly one recipient: `number`, `group_id`, or `contact_id`. `url` must still be reachable when the send happens: Turbo Notify fetches the bytes from it. A copy is kept in the organization's own object stor
send_locationSend a location pin. Set exactly one recipient: `number`, `group_id`, or `contact_id`. `latitude` is between -90 and 90, `longitude` between -180 and 180. `name` and `address` label the pin; `url` adds a link beside it. A location cannot be edited after it is sent: `delete_messag
send_contact_cardSend a contact card the recipient can save to their phone. Set exactly one recipient: `number`, `group_id`, or `contact_id`. `phones` takes plain E.164 numbers, 1 to 10 of them. `emails`, `organization`, `title` and `address` are optional extra fields on the card; `emails` allows
send_calendar_eventSend a calendar event invitation. Set exactly one recipient: `number`, `group_id`, or `contact_id`. `start_at` and `end_at` are ISO 8601 **with an offset**, for example `2026-09-10T14:00:00Z`. A timestamp without one is rejected: the recipient's phone renders the event in their o
send_cta_buttonSend an interactive message carrying one link button. Set exactly one recipient: `number`, `group_id`, or `contact_id`. A link button is the only interactive type WhatsApp accepts on this kind of connection. Reply buttons and list pickers are not available and will not become ava
reply_to_messageReply to an EARLIER message, quoting it, without naming a recipient. Use it to bring context into the conversation: when the conversation has moved on and your answer depends on something said a while ago (by the contact, by you or, in a group, by any participant). To answer the
edit_text_messageReplace the text of a text message this number already sent. The recipient sees the new text marked as edited. The message keeps its id and its place in the conversation; only the text changes. Only a text message can be edited here. For the caption of an image, video or document
edit_media_captionReplace the caption of an image, video or document this number already sent. The recipient sees the new caption marked as edited. The file itself stays exactly as it was and the message keeps its id: only the caption changes. There is no way to replace the file; to send a differe
edit_calendar_eventCorrect a calendar event this number already sent. `name` and `start_at` are always required, plus whatever else the event has: `description`, `end_at`, `join_link`, `location`, `has_reminder` with `reminder_offset_sec`, and `extra_guests_allowed`. This REPLACES the whole event:
cancel_calendar_eventCancel a calendar event this number already sent. The event stays in the chat marked as canceled, and WhatsApp tells the guests. Send the same `name` and `start_at` the event has, plus the details you want the canceled card to still show (`description`, `end_at`, `join_link`, `lo
delete_messageRevoke a message for everyone in the conversation. This is WhatsApp's "delete for everyone". It is not reversible, and recipients see a tombstone where the message was, so they can tell something was deleted. Confirm with a human before using it on anything a person has plausibly
react_to_messageAttach an emoji reaction to a message, or remove one. Pass a single emoji character, e.g. `👍`. Passing an empty string removes the reaction this number previously left. A new emoji replaces this number's previous reaction rather than adding beside it; to bring the earlier one ba
send_typing_indicatorShow "typing…" to a recipient while you prepare an answer. Set exactly one recipient: `number`, `group_id`, or `contact_id`. Useful before a reply that takes a few seconds to compose, so the person on the other end sees something is happening. It expires on its own, so clearing i
mark_as_readMark a conversation's unread messages as read, without sending anything. Set exactly one recipient: `number`, `group_id`, or `contact_id`. This is independent of the automatic mark-as-read that already happens when you send, reply, react, edit, delete or start typing (the number
list_messagesList messages for one number, newest first, received and sent. Each item says who it is from and to, which number it belongs to, its `direction`, `content_type`, `origin`, a short `preview`, `at`, `status` and `content_expired`. Mentions, transcription and full media detail are o
get_messageFetch one message with its full content, parties and mentions. The answer includes the number's stable `number_id` (`num_…`) next to `number_alias`. `at` is when the message actually happened on WhatsApp; `status.at` is when it reached its current delivery status and keeps moving
get_message_statusCheck where a message got to: queued, sent, delivered, read, failed. Status only moves forward. A failed status always carries an error code, and for a few media and reaction problems it also carries a hint naming the field to change; most failures give the code alone. Read the c
get_message_receiptsSee who received and who read a message. Most useful for group messages, where the single status on the message cannot express that some members read it and others have not. Requires a plan that includes read receipts; on plans without it the call is refused with `feature_not_ava
get_message_reactionsList the emoji reactions on a message, and who left each one. Each entry names the reactor and the emoji. Reactions are replaced rather than accumulated per person: someone who reacts twice leaves one entry showing their latest emoji, so this is a current snapshot and not a histo
get_message_responsesSee how the guests answered a calendar event: going, not going or maybe. Only works on a calendar event; any other message answers `invalid_request: message_not_calendar`. The answer has `counts` (how many guests are going, not going or maybe, and how many extra guests those who
get_message_quotaCheck how much of this number's message allowance is left. The quota is **per number**, not per organization: an organization with three numbers has three separate allowances. It resets at `cycle_end`, which is the organization's real billing boundary rather than a rolling window
list_contactsList the people this number has exchanged messages with. Filter by `phone` or by `name`. They are separate filters, not one search box: `name` matches the contact's name, `phone` matches the number. `source` restricts to how the contact first appeared: `inbound` (they messaged th
get_contactFetch one contact: name, phone number and activity timestamps. `first_messaged_at` is when a message from this number first reached them on WhatsApp, and `last_interaction_at` is the last message that passed in EITHER direction, so it moves when they write to you as well. A messa
get_contact_profile_pictureGet a contact's profile picture, or the reason there is none. The answer carries `kind`: `available` with a temporary URL, or `unavailable` with a reason. `no_storage` means the organization has not configured object storage, which is a setup step rather than a fault with this co
refresh_contactAsk WhatsApp for this contact's current name. Only the name is refreshed. The profile picture updates on its own the next time this number exchanges a message with the contact, and this does not change how messages reach them. It answers right away with `requested_at`; the refres
get_contact_quotaCheck how much of this number's contact allowance is left. A contact counts once per billing cycle when this number messages them through Turbo Notify, new **or** returning. Messaging the same person again in a later cycle counts again. Like the message quota, this is per number
list_groupsList the WhatsApp groups this number is a member of. The list is built when the number connects: every group it belongs to is picked up then, whether or not anything has been said in it. A group joined since then is picked up from the join itself, without waiting for anyone to sp
get_groupFetch a group: its name, description, picture and settings. Returns how many participants it has, not who they are. Membership is deliberately not readable: it arrives as it changes, on the `group.participants_added` / `_removed` / `_promoted` / `_demoted` events, which `list_eve
get_group_pictureGet a group's picture, or the reason there is none. Same shape as a contact's picture. The answer carries `kind`: `available` with a temporary URL, or `unavailable` with a reason. `no_storage` means the organization has not configured object storage.
list_numbersList every WhatsApp number this organization has, with its status. Start here when you do not know which aliases exist. The main number is always `main`; extras carry the alias the customer chose, and that alias is what every other tool's `number_alias` expects. Each number also
get_numberCheck one number: its phone number, status, and when that status began. `id` (`num_…`) is the number's permanent identifier. The alias can be renamed, the `id` cannot. Either one works as `number_alias`. `connected` means it can send right now. `connecting` means a connection was
connect_numberReconnect a number that is currently offline. Uses the credentials already stored for the number, so no QR code and no human are involved. Use it when `get_number` reports `disconnected` and you want to send. Returns immediately, before the connection is established. The answer h
disconnect_numberTake a number offline deliberately, keeping its link to the phone. The stored credentials survive, so `connect_number` brings it straight back with no pairing. Nothing is deleted. Disconnecting does not stop billing: an extra number is billed every cycle until it is removed. Retu
get_usageGet message and contact usage for the whole organization. The top-level totals are the **sum across every live number**: an organization with two numbers on a 50,000-message plan reports a quota of 100,000, not 50,000. The `numbers[]` breakdown shows each number separately, which
list_eventsPoll everything that happened: messages, contacts, groups, numbers, quotas. This is how an agent learns about inbound messages without hosting a webhook endpoint. **Events come back newest first, so polling for new ones uses `ending_before`, not `starting_after`.** Typical loop:
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月19日
注册名称已通过域名 turbonotify.com 验证(注册中心会核实域名所有权)
代码最后更新于6天前
不适用:由 turbonotify.com 的所有者自己运行的云端服务器,你不会运行仓库里的代码
在 814 毫秒内响应(HTTP 200)
无需登录
已读取 36 个工具描述,未发现针对 AI 的隐藏指令
如果你是作者,可把这段代码贴到 README。徽章会链接回本页。
[](https://mcp.popnx.com/en/servers/turbonotify-turbo-notify)提问、分享技巧或报告无法使用。按“有帮助”数量排序。
还没有评价
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于6天前,最新版本(1.5.13)于6天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。
同一分类中有:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同一分类、其他作者、命令已通过检查。官方的排在前面,再按星标排序。
如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Render markdown into email-safe HTML, lint drafts for deliverability problems, and preview emails.
Build and fix Discord bots from a chat. Kite hosts them 24/7, with no code to deploy.
Authenticated email gateway for AI agents — per-agent inboxes, HITL approval, SPF/DKIM verified.
Infobip MCP server for omnichannel communication and messaging. SMS, RCS, WhatsApp, Viber and more.
CAD in ChatGPT and Claude: editable parts, STEP/STL/drawings, in-chat 3D, automatic checks.
| 本项 Turbo Notify: WhatsApp for AI agents | emailmd | Kite Discord Bot Builder | e2a — email for AI agents | Infobip MCP | kernelCAD | |
|---|---|---|---|---|---|---|
| 运行位置 | 在云端运行,无需安装 | 云端或安装在电脑上都可以 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 | 在云端运行,无需安装 |
| 需要密钥 | 否 | 否 | 否 | 否 | 否 | 否 |
| 可在 Claude 中按 + 添加 | 否 | 否 | 否 | 否 | 是 | 否 |
| 基础检查 | 4/4 | 5/5 | 4/4 | 4/4 | 4/4 | 4/4 |
| 许可证 | MIT | MIT | AGPL-3.0 | Apache-2.0 | MIT | MIT |
| 价格 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 | 登记中未列出费用 |
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
Skills that put the Turbo Notify MCP server to work inside your AI agent: Claude Code, Claude Desktop and Cowork, Codex, the Antigravity CLI and the Gemini CLI, and any other agent that reads the Agent Skills format.
| Skill | What it does |
|---|---|
virtual-attendant | Serves a business's customers on WhatsApp: answers in the customer's language, remembers each customer, calls a person when it should, and takes commands from administrators and attendants on WhatsApp itself. |
Customer guides (Portuguese and English): WhatsApp virtual attendant, Agent skills and AI agents, with one page per agent.
| Agent | Commands |
|---|---|
| Claude Code | claude plugin marketplace add turbo-notify/agent-skills then claude plugin install turbo-notify@turbo-notify |
| Claude Desktop and Cowork | Customize, Plugins, Add, Add marketplace, Add from a repository: turbo-notify/agent-skills; then Discover, turbo-notify, Add |
| Codex | codex plugin marketplace add turbo-notify/agent-skills then codex plugin add turbo-notify@turbo-notify |
| Antigravity | agy plugin install https://github.com/turbo-notify/agent-skills |
| Gemini CLI | gemini extensions install https://github.com/turbo-notify/agent-skills |
| Hermes Agent | hermes skills install turbo-notify/agent-skills/skills/virtual-attendant, then add the MCP server https://mcp.turbonotify.com in Hermes |
| OpenCode | npx skills add turbo-notify/agent-skills -a opencode (project folder .agents/skills/, or -g for ~/.config/opencode/skills/), then opencode mcp add --global --url https://mcp.turbonotify.com turbo-notify and opencode mcp auth turbo-notify to sign in. Guide: Turbo Notify in OpenCode |
| Cline | Add the MCP server https://mcp.turbonotify.com to cline_mcp_settings.json (steps for the editor and the CLI in llms-install.md) |
| Other agents that read the Agent Skills format (Cursor, Copilot and more) | npx skills add turbo-notify/agent-skills, then add the MCP server https://mcp.turbonotify.com in that agent's own settings |
The unattended runner exists for Claude Code and Codex only. In the other agents the attendant runs in assisted mode: a session you keep open, where a person approves each draft.
The plugin rows above already declare the Turbo Notify MCP server (https://mcp.turbonotify.com), so there is nothing to add. Sign in with your Turbo Notify account the first time the agent uses it (Claude Code: /mcp; Codex: codex mcp login turbo-notify; Antigravity: Agent settings, Customizations, Authenticate next to the server), then ask it to "set up the Turbo Notify virtual attendant". No account yet? Create one at https://dashboard.turbonotify.com/auth/signup?locale=en. For anything that runs alone, use an API key instead (see the guide for your agent in skills/virtual-attendant/references/).
The skill checks its version on every cycle and messages the administrators when a new one exists, with the command for the agent in use.
| Agent | Command |
|---|---|
| Claude Code | claude plugin marketplace update turbo-notify then claude plugin update turbo-notify@turbo-notify |
| Claude Desktop and Cowork | The marketplace syncs from the repository; if a new version does not show up, remove the marketplace and add it again |
| Codex | codex plugin marketplace upgrade then codex plugin add turbo-notify@turbo-notify |
| Antigravity | Run the install command again |
| Gemini CLI | gemini extensions update turbo-notify |
https://mcp.turbonotify.com, which the plugin declares in .mcp.json, mcp.json and mcp_config.json (one file for each family of agents; none holds a key or a header). You sign in with your account, or you connect your own with an API key. It runs with your account or API key permissions.~/.turbo-notify/attendant) holding, for each customer, the conversation (kept 90 days by default, then deleted), short summaries of older parts of it, and a file with the facts that customer gave (name, preferences, what they asked for), plus what you taught. Turbo Notify gets no copy. /forget erases one customer's data, and the retention is a number you can change in memory-policy.json.https://api.turbonotify.com, called by the helper with your API key when the unattended runner or a console command sends a message.raw.githubusercontent.com/turbo-notify/agent-skills/main/latest.json, read about once an hour (and again after 10 minutes if a check fails) for the version check. A failure changes nothing.tn_assist helper with python3. The helper uses only the standard library and installs nothing.claude or codex command once per customer, in a separate process with no tools, to write that customer's answer. The process gets that customer's messages, their file and the business knowledge that matches the message (the company, tone and hand-off files, plus up to three more picked by the words of the message), and nothing else.TURBO_NOTIFY_API_KEY variable you set for it and sends it only to api.turbonotify.com, as the sign-in of each request. It is never passed to the process that writes a customer's answer..claude-plugin/ plugin and marketplace manifests (Claude Code, Codex)
.codex-plugin/ the manifest Codex reads for the name, logo and listing text plugin.json manifest for Antigravity gemini-extension.json manifest for the Gemini CLI (the connection to the server) .mcp.json the Turbo Notify MCP server, as Claude Code, Claude Desktop, Cowork and Codex read it mcp.json the same server, as the Agent Plugins format reads it (Copilot, Cursor) mcp_config.json the same server, as Antigravity reads it assets/icon.png the plugin icon agents/ the tool-less agent that answers a customer skills/virtual-attendant/ SKILL.md the entry point the agent reads references/ one short file per topic (setup, tick, console, memory, privacy, ...) assets/templates/ interview templates (pt, en) and the memory policy scripts/tn_assist/ the helper: routing, memory, egress check, runner (Python 3.9+, no dependencies) tools/release.py version consistency check and sync tests/ unit, property and security tests (Poetry, development only) evals/attendant/ live evaluation of a customer's turn on a real model, with a made-up shop
The helper holds the guarantees the model cannot be trusted with: who is who is decided by code from the registered numbers, a customer's turn runs without tools, every reply passes an egress check before it can leave, and the data never leaves the workspace folder.
poetry install
poetry run pytest poetry run ruff check . && poetry run ruff format --check . poetry run mypy python3 tools/release.py check
The live evaluation needs your own claude command, logged in. It asks 40 questions that the knowledge cannot answer and 11 that it can, and plays seven conversations (some end with a thank you, which is owed no answer). It checks every reply for a price, a date, a time, a quantity, a discount or a promise the knowledge does not state, for the language of the reply, and that a thank you is left alone while an "ok" that is really a question is answered. Two last checks cut the model's answer in half to see what the runner does with an answer it cannot read, and play an "ok" after an offer ("quer que eu chame alguém?") to see that it is answered, not left alone. Nothing in it is real data.
poetry run python -m evals.attendant run # writes evals/attendant/results/<date>-<label>/
poetry run python -m evals.attendant run --set refusal # only the check on an unreadable answer poetry run python -m evals.attendant run --set offers # only the check on an ok that accepts an offer TN_EVALS_LIVE=1 poetry run pytest evals # the same, as tests (skipped otherwise)
Releases bump VERSION, latest.json, the five manifests, the helper and pyproject versions and CHANGELOG.md together (tools/release.py sync), then move the v1 tag, which stays available for anyone who wants to pin to 1.x (...agent-skills#v1, or --ref v1 in Codex).
MIT. See LICENSE.