Update to Kenso

{
  "description": "Use when tuning existing sending inboxes (daily limits, display names, signatures, reply forwarding, warmup pause/resume). New domains go through infra-planning and domain-selection.",
  "included_files": [
    {
      "relative_path": "references/forwarding-and-warmup.md",
      "size_in_bytes": 2169
    }
  ],
  "name": "inbox-configuration",
  "skill_md_contents": "---\nname: inbox-configuration\ndescription: Use when tuning existing sending inboxes (daily limits, display names, signatures, reply forwarding, warmup pause/resume). New domains go through infra-planning and domain-selection.\n---\n\n# Inbox configuration\n\nTune existing sending inboxes. These tools cannot read or change inboxes: you bring the judgement and the exact values, and the user makes each change in Kenso on the Email Delivery page, https://app.ken.so/<workspace id>/delivery?tab=inboxes, from the inbox's Inbox actions menu > Edit inbox. New domains and inboxes are sized in `infra-planning` and ordered in `domain-selection`.\n\nNever suggest disconnecting or deleting an inbox, or changing its username, to fix a setting. Restate any change as a short summary and get a yes before the user makes it. Inbox changes need the admin role.\n\n## 1. Read state\n\nAsk the user to open the Inboxes tab and tell you, or paste, each inbox's address, domain, daily limit and display name.\n\nSummarize per inbox: address, domain, daily limit, display name. The inboxes page is https://app.ken.so/<workspace id>/delivery?tab=inboxes.\n\n## 2. Daily limits\n\n- Healthy, warmed inboxes: **30-50/day**\n- New or still warming: **5-10/day**, ramp over 2-3 weeks\n- Never suggest **more than 100/day** per inbox\n- `0` pauses that inbox. No explicit limit means the provider default (Google/Microsoft 25, Azure 5)\n\nLeave create-time limits unless the user asks. Do not raise limits on a domain that is still setting up.\n\nAfter the user approves a number:\nthe user opens Inbox actions > Edit inbox, sets Daily send limit to it and clicks Save changes, once per inbox.\n\nGive one sentence on why the limit protects deliverability. Warmup shares the same provider budget, so leave room for it.\n\n## 3. Display names\n\nEdit inbox > First name and Last name, then Save changes. Instant and safe.\n\n## 4. Signatures\n\nEdit inbox > Signature, then Save changes, per inbox.\n\nDraft the signature here first and show it to the user before they paste it in.\n\n## 5. Reply forwarding and warmup\n\nForward to the client's own external email only:\nEdit inbox > Reply forwarding, with the client's external address, then Save changes. Details, plus warmup: `references/forwarding-and-warmup.md` in this skill's folder.\n\n## 6. Boundaries\n\n- **Tuning existing inboxes**: this skill.\n- **New inboxes / domains**: `infra-planning`, then `domain-selection`. Do not promise a free domain.\n- **Connecting external inboxes / OAuth**: dashboard only.\n- **Username changes**: in place on the same mailbox, never a replacement purchase. Not done from this skill.\n\n## Refusal handling\n\n`INBOX_LIMIT_REACHED` is the most common here.\n\n| Code | What to tell the user |\n|------|------------------------|\n| `PLAN_FEATURE_NOT_AVAILABLE` | Managed sending infrastructure is on paid plans - upgrade at https://app.ken.so/<workspace id>/settings/billing. Show `error.recovery.summary` when present. |\n| `INBOX_LIMIT_REACHED` | Show `used` / `limit` / `remaining`. Offer: stay within remaining allocation (or rebalance limits), or upgrade. |\n\nIf they need more daily send than they have, load `infra-planning`. When headroom is zero, help them get more from existing inboxes instead of framing it as a system error.\n"
}