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 人 1 点)加算。お金では買えません。
品質: 基本チェック 4/4 項目に合格(表示のみ、並び順には不使用)
使っているAIアプリを選んで、設定をコピーしてください。
ひとことで AI にインストールしてもらう
Turbo Notify: WhatsApp for AI agents をインストールして。https://mcp.popnx.com/i/turbonotify-turbo-notify.md に従い、コマンドを見せて、私が OK するまで実行しないで。パソコンで作業できる AI(Claude Code や Cursor など)に貼り付けます。手順を読み、コマンドを見せて、あなたの OK を待ちます。キー不要・登録不要。 · 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.comClaude が検出したサインイン設定の画面で 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 を使って、私に何ができるか教えて、1 つやってみせて✓ Claude が Turbo Notify: WhatsApp for AI agents を使っていると言うか、回答に Turbo Notify: WhatsApp for AI agents のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に Anthropic のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
ChatGPT との接続はプランしだい
フル MCP:Web 版 ChatGPT の Business・Enterprise・Edu · Pro:読み取り/取得の権限で接続、データを変えるツールは使えないことがあります · Plus:公式ドキュメントで未確認。プラグイン画面にカスタム MCP を追加する項目があれば試せます · Web のみ
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 を使って、私に何ができるか教えて、1 つやってみせて✓ 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.comTurbo Notify: WhatsApp for AI agents が一覧にあり、接続済みと表示されれば OK です
Turbo Notify: WhatsApp for AI agents を使って、私に何ができるか教えて、1 つやってみせて✓ 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 を使って、私に何ができるか教えて、1 つやってみせて✓ 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 を使って、私に何ができるか教えて、1 つやってみせて✓ VS Code が Turbo Notify: WhatsApp for AI agents を使っていると言うか、回答に Turbo Notify: WhatsApp for AI agents のツール名が出れば接続成功です
メニュー名は 2026年11月11日 に VS Code のヘルプページで確認 · アプリのバージョンにより画面が少し違うことがあります
Windsurf、Zed、Gemini CLI など MCP を使える他のアプリは追加方法がそれぞれ違います。アプリ一覧で確認してください
Web 経由でつなぐアプリ用のアドレス
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 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URL で接続するので、リモート MCP を受け付けるアプリでも使えます。例:Web 版 ChatGPT(Business 以上はフル MCP、Pro は読み取りのみ)。
同じカテゴリには:emailmd, Kite Discord Bot Builder, e2a — email for AI agents, Infobip MCP, kernelCAD
同じカテゴリでほかの作者のもの。コマンドは確認済み。公式を先に、次にスター順。
カードの見方:↓ 週あたりのダウンロードi★ GitHubスターi3つの柱:レビュー · チェック · 利用状況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.