{"id":30531,"plugin_id":"plugin_asdk_app_6ac2279f7a9c8191abc34801f091a7eb","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-09T06:04:52.250Z","digest":"fc976e0fd56d72388eb09017613142bc4c168455ca008748649999037e959b38","against":null,"payload":{"description":"Take a company from nothing to a live email programme in Send & Retain — understand the business, install starter templates and paused automations for its type, rewrite them in its voice, then set up sending. Use when the user wants to start email for a new or empty company.","included_files":[],"name":"set-up-a-company","skill_md_contents":"---\nname: set-up-a-company\ndescription: Take a company from nothing to a live email programme in Send & Retain — understand the business, install starter templates and paused automations for its type, rewrite them in its voice, then set up sending. Use when the user wants to start email for a new or empty company.\n---\n\n# Set up a company\n\nThe order matters. Templates and automations need no provider, domain or sender,\nso do not ask for DNS records or API keys until the last phase. Show the user\nsomething worth having before asking for the hardest work.\n\n## 1. Understand\n\n`email_list_projects`, or `email_create_project` with the company's website (it\nreads the site and infers the brand). Then learn, two questions at a time and\nnever as a form, what you cannot read off the site:\n\n- which events their app already emits — this decides every automation's\n  trigger, and an automation wired to an event nobody sends looks alive and is dead\n- who is on the list, and whether it exists elsewhere already\n- the one customer moment they most want handled (signup, an abandoned\n  checkout, a lapsed customer)\n- the domain they will send from — call `email_create_domain` as soon as they\n  name it, so verification runs in the background\n\n## 2. Programme\n\n`email_get_brand` first; if it is empty, read the website and save\ncolours, fonts and voice with `email_update_brand`, because the starters bake the\nbrand in. Then `email_list_sequence_packs`, propose an archetype (saas,\necommerce, newsletter-media, marketplace) and its automations in plain language,\nnaming each automation's trigger. On agreement, `email_bootstrap_company`. It\npublishes the starter templates and creates every automation **paused**.\n\n## 3. Content\n\nRewrite each starter in the company's voice (`email_update_template`), check it\nwith `email_render_template`, then `email_publish_template_version`. Start with\nthe email for the moment they said hurts most. `email_preview_automation` shows\na whole automation's emails.\n\n## 4. Live\n\n`email_get_connection_status` → if no provider is connected, give the user its\n`settingsUrl`, where they connect sending themselves (never take a key in chat)\n→ `email_verify_domain` → `email_register_webhooks` → `email_create_sender`. The\nuser mints their app's API key on the same page; give them a\n`POST /api/v1/events` snippet for exactly the triggers the chosen automations use.\nThen `email_pre_launch_check`, and enable automations one at a time with\n`email_set_automation_status`, each only on the user's explicit go-ahead.\n\nDone is an automation live, its trigger seen, and a real send from their own domain.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}