Update to Command Mail

{
  "description": "Set up a connected Command Mail account with its owner, asking which mail matters, how much the agent may do on its own, how the archive and sorting rules should look, whether Spam and Trash should be emptied automatically and when a recurring Command Mail routine should run. Use only when the user refers to Command Mail or it is their connected mail source, right after connecting or when they ask to set up or reconfigure it; not for other mail providers and not for answering a single message.",
  "included_files": [],
  "name": "inbox-setup",
  "skill_md_contents": "---\nname: inbox-setup\ndescription: Set up a connected Command Mail account with its owner, asking which mail matters, how much the agent may do on its own, how the archive and sorting rules should look, whether Spam and Trash should be emptied automatically and when a recurring Command Mail routine should run. Use only when the user refers to Command Mail or it is their connected mail source, right after connecting or when they ask to set up or reconfigure it; not for other mail providers and not for answering a single message.\n---\n\n# Set up Command Mail with the owner\n\nThe goal is an inbox the owner trusts: agreed priorities, a clear archive, rules\nthat sort routine mail, and a routine that runs when they expect it. Ask,\npropose, confirm, then act. Keep the interview short; offer sensible defaults the\nowner can accept in one word.\n\n## 1. Read what exists\n\nCall `capabilities`. Note the owner, the granted scopes, every mailbox with its\nautonomy level (read, suggest, rules or auto), `retention`, the agent send limit\nand the plan. Report plan limits neutrally; never promote upgrades, prices or\ntrials. Then read `list_folders`, `list_labels`, `list_rules`, `get_signatures`\nand `checkup_status`, and summarize in a few lines what is already set up.\nNever ask the owner for passwords, tokens or codes; the connection is OAuth.\n\nIf no mailbox is connected and `mailboxes` is granted, offer `connect_mailbox`:\nthe owner then forwards that address to the returned intake address in their\ncurrent provider. The provider's confirmation mail arrives in Command Mail; tell\nthe owner where to find it and let them confirm it themselves; do not repeat the\ncode in the conversation. With a domain of their own, `claim_domain` returns a\nTXT record and `verify_domain` confirms it. Old mail comes in through the Command\nMail CLI (`commandmail import file.mbox --mailbox ADDRESS`), which archives it\nread and triggers nothing; there is no MCP import.\n\n## 2. Interview\n\nAsk in one message, with your proposed default after each question:\n\n1. Which mail matters most: customers, invoices and payments, deadlines,\n   appointments, family, newsletters worth reading?\n2. Autonomy: what may happen without asking? \"suggest\" keeps every move as a\n   suggestion, \"rules\" lets agreed rules act on their own, \"auto\" also lets the\n   agent file directly. What must always wait for the owner?\n3. Rules: which senders or kinds of mail should be sorted automatically from now\n   on, and where to (spam, archive, a folder, trash)? Default: none until the\n   owner names them.\n4. Retention: should Spam and Trash be emptied for good after some days (7, 14,\n   30 or 90)? Default: off; a common choice is Spam after 30 days.\n5. Replies: should you only save drafts for approval, or may you send some kinds\n   of mail directly? Direct sending needs the separate \"Send directly\" permission,\n   which starts switched off.\n6. Archive: which top-level folders? Propose a shallow plan in the owner's words,\n   for example Customers, Finance (by year), Contracts, Accounts, Newsletters.\n7. Rhythm: when and how often should the routine run (for example 07:30 brief,\n   12:30 and 18:00 short passes), and in which time zone?\n8. Signature: keep, write a plain one, or a formatted one with logo and links?\n\n## 3. Apply what the owner confirmed\n\n- Autonomy per mailbox is set by the owner under Settings in Command Mail; agents\n  cannot change it. Explain the level that matches their answers.\n- Create the agreed folders with `create_folder` (`parentId` for subfolders);\n  `import_folders` creates many paths but is a dry run until `dryRun` is false.\n- Create named views with `create_label`; a view moves no mail.\n- Create each rule the owner named with `create_rule`: `from` (one exact\n  address) or `domain`, `action` (`spam`, `archive`, `folder` with `folderId`,\n  or `trash`), optionally `kind`, `subjectWords` and `addressId`. It is active\n  where the mailbox or the account default is \"rules\" or \"auto\", otherwise it\n  waits as a suggestion; report which. Protected mail (invoices, payment\n  problems, security notices, deadlines, appointments, requests, personal mail)\n  never goes to spam or trash by rule. To sort existing mail too, use\n  `apply_rule` and repeat with the returned `cursor` while `more: true`.\n- Set retention with `set_retention` (`spamDays`, `trashDays`) only if the\n  owner asked for it, after naming the days once more: removal is permanent.\n  It needs the account default at \"rules\" or \"auto\", and switching it on also\n  needs the read and direct-send permissions; otherwise the owner sets it in the\n  app.\n- Show a signature before `set_signature`; it applies to every later message of\n  that identity. HTML is cleaned; link images by https URL.\n\n## 4. Set up the routine\n\nA routine only runs if the agent host schedules it. If the host offers scheduled\ntasks or automations, propose one task per agreed time with this prompt: \"Run my\nCommand Mail routine with the inbox-routine skill, time zone ZONE.\" Create it only\nafter the owner agrees, and confirm the schedule the host actually saved. If the\nhost cannot schedule, say so plainly and offer the same prompt for the owner to\nrun by hand. Never claim background monitoring that does not exist.\n\n## 5. First pass and handover\n\nRun the first routine pass now (see inbox-routine) so the owner sees a result.\nFor a large backlog, suggest the inbox-cleanup skill as a separate session.\nFinish with a short summary: mailboxes and their autonomy, folders and views\ncreated, rules active or waiting as suggestions, retention, signature, schedule,\nand what the owner still has to do in the app.\n"
}