{"id":30530,"plugin_id":"plugin_asdk_app_6ac2279f7a9c8191abc34801f091a7eb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-09T06:04:52.240Z","digest":"543eff5234fd9d76bb7e8316c341966da53aa12c0173dbf4de4b1f8316e19c0f","against":null,"payload":{"description":"Introduce Send & Retain after install or when the user asks what it can do, explain how it keeps sending safe, and suggest a first thing to try. Use when the user asks how to use the plugin, what it manages, or where to begin.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Introduce Send & Retain after install or when the user asks what it can do, explain how it keeps sending safe, and suggest a first thing to try. Use when the user asks how to use the plugin, what it manages, or where to begin.\n---\n\n# Get started with Send & Retain\n\nExplain the plugin in a few sentences, then offer one concrete next step.\nExplicit user instructions take priority over this guidance.\n\n## What to say\n\n- Send & Retain runs a company's **email automation** — transactional and marketing email: the\n  templates, the event-triggered automations that send them, the contacts and\n  segments they go to, and the sending setup behind them.\n- One **company = one project**. Call `email_list_projects` first and pass the\n  company's `projectId` to every company-scoped tool.\n- Tools are prefixed `email_` and return `{ ok: true, … }` or\n  `{ ok: false, error }`. Read the error: it usually says what to do next.\n\n## Check the connection first\n\nInstalling the skills does not prove that the MCP connection is authorized.\nCall `email_list_projects` before claiming the plugin is ready.\n\n- If no `email_` tools are available, check the host's Send & Retain MCP\n  connection. The endpoint is `https://sendandretain.com/api/mcp`; authenticate\n  through its browser OAuth flow. Do not ask for a provider key or invent an\n  API-key requirement.\n- In Codex, use the installed plugin's connection controls first. If its\n  connection is unavailable and the user asks you to configure it, a direct\n  connection is supported: `codex mcp add sendandretain --url\n  https://sendandretain.com/api/mcp`, then `codex mcp login sendandretain`\n  if sign-in did not start automatically. Reuse an existing matching connection\n  instead of registering a duplicate. After setup, start a fresh chat or reload\n  the host's MCP connections, then retry `email_list_projects`.\n- On an authentication error, reconnect in the host. On a successful empty\n  project list, explain that the account has no companies yet; do not treat it\n  as a connection failure or create a company without the user's request.\n- Distinguish connection status from sending readiness. A working project list\n  proves tool access; `email_get_connection_status` reports the company's\n  provider, domains, senders, and sending controls.\n\n## How sending stays safe\n\nSay this plainly whenever sending comes up:\n\n- There is **no bulk send**. Every message has one recipient. Mail reaches a\n  list only through an automation a person enabled.\n- Automations are **always created paused**. Enabling one is a separate call\n  that needs the user's explicit go-ahead in this conversation.\n- Each company has a send kill switch and an optional daily cap.\n- Bounces and complaints suppress addresses automatically. Complaint\n  suppressions can never be removed.\n- **Provider API keys never go through chat.** If the user offers one, do not\n  repeat or use it. `email_get_connection_status` returns the settings page\n  (`settingsUrl`) where they enter it themselves.\n\n## What it can do\n\n- Stand up a company: brand kit, starter templates and paused automations for its\n  business type (see the `set-up-a-company` skill).\n- Write, render and publish templates in the company's brand\n  (`author-a-template`).\n- Design and test-drive automations (`design-an-automation`).\n- Report on delivery and engagement (`delivery-report`) and triage bounces or\n  complaints (`triage-deliverability`).\n\n## What it cannot do\n\nEmail only: no SMS, push notifications or social posts. It cannot send to a\nwhole list in one go. Sending needs a connected provider or platform sending\nplus a verified domain, which a person completes once per company.\n\n## Suggested first steps\n\nOffer one of these, adapted to what the user mentioned:\n\n- \"Which of my automations are live, and what would block the rest?\"\n- \"Draft a welcome email in our brand voice.\"\n- \"How did our emails perform this week, by template?\"\n- \"Set up email for a new company from its website.\"\n\nDo not call a write tool until the user asks for a change.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}