inkwell

Use this skill to draft an email reply (or reply-all / forward) in the user's voice for their review, saved to the mailbox Drafts folder via the inkwell CLI. Triggers on "draft a reply", "respond to this email", "write a response", "reply to <sender>", "answer my reply-later stack", "forward this to Bob with context", "set my out-of-office". Produces a draft for approval with a confidence label — it never sends (Mail.Send is denied by construction, PRD §3.1; the user sends from Outlook). For triaging use `mail-triage`; for read-only briefings use `mail-executive-summary`.

Use this skill to produce a morning email briefing for a busy senior leader from their actual mailbox via the inkwell CLI — what needs their reply, what they're waiting on, what's worth knowing, and what's already handled, plus calendar. Triggers on "brief me on my email", "what needs my attention", "morning inbox rundown", "catch me up on my inbox", "summarize my unread", "what's on my calendar today". Strictly read-only — never archives, deletes, routes, drafts, or marks read. For acting on mail use `mail-triage`; for writing replies use `mail-draft-reply`.

Use this skill to find threads where the user is waiting on someone else and hasn't heard back, then draft polite nudges to chase a response — via the inkwell CLI. Triggers on "follow up on", "chase", "nudge", "what am I waiting on", "remind people who owe me a reply". Drafts for approval, saved to the Drafts folder — it never sends (Mail.Send is denied by construction, PRD §3.1; the user sends from Outlook). The action counterpart to `mail-executive-summary`'s "waiting on others" section.

Use this skill to prepare a concise briefing on the external people the user is about to meet — who they are, their company, recent discussions, and anything outstanding — via the inkwell CLI (Graph calendar view + cached mail), optionally with web research. Triggers on "prep me for my meetings", "who am I meeting today", "brief me before this call", "tell me about <person> before our meeting". Read-only: never sends, replies, or modifies the calendar. For inbox briefings use `mail-executive-summary`.

Use this skill to free up mailbox storage via the inkwell CLI — soft-delete (move to Deleted Items) the junk that takes the most space, large attachments first, then old bulk-sender back-catalogs and stale low-value mail. Triggers on "free up storage", "my mailbox is full", "clear space", "trash junk to reduce storage". It never permanently deletes and never empties Deleted Items — the user does that. Confirm every batch. For volume (not size) cleanup use `mail-triage`; to stop the junk arriving use `mail-reduce-noise`.

Use this skill to cut recurring inbox clutter at the source via the inkwell CLI — find high-volume, rarely-read senders and apply a standing decision (unsubscribe, auto-route past the inbox, or keep) so their future mail never piles up. Triggers on "reduce email noise", "unsubscribe from junk", "clean up my subscriptions", "stop newsletters cluttering my inbox", "which senders are noisiest". Different from `mail-triage` (one-off processing of what's already there) — this changes what arrives. For a one-off cleanup use `mail-triage`.

Use this skill when the user wants their actual mailbox triaged, organized, or processed via the inkwell CLI — acting as an executive assistant on live mail, not developing inkwell. Triggers on "triage", "sort my inbox", "organize my email", "process my inbox", "clear my inbox", "clean up my email", "deal with the screener queue". Makes one classification pass and files every inbox thread into the workflow folders (@Action / @Waiting / Archive / Reference / Newsletters) or soft-deletes the worthless — behind a presented list and explicit confirmation. Do NOT use for inkwell code changes (use `work-loop` / `bug-fix`), for read-only briefings (use `mail-executive-summary`), or for writing replies (use `mail-draft-reply`).

Use this skill to walk the adopter through the four classes of post-install change (substitution, .upstream companion merges, discovery + restructuring, within-layout consolidation). Triggers after installing a pack (the install->adapt chain nudges via session-start hook) or any time `<repo>/.adapt-install-marker.toml` / `~/.agentbundle/.adapt-install-marker.toml` is on disk. Walks both scopes' state files for Tier-2 detection; class-1 substitution shells out to `agentbundle adapt`; classes 2-4 write files directly under the per-scope path-jail.

Use this skill when the user wants to start a new feature with a spec, or wants to write a spec for something they're about to build in inkwell. Triggers on "new spec", "write a spec for X", "let's spec this out", "scaffold spec NN", "start a feature for…". Creates both docs/specs/NN-<title>/spec.md AND docs/specs/NN-<title>/plan.md so the two artefacts land together — the v0.12.0 missing-plan-file class of bug can't recur because the plan file is created up front.

Use this skill whenever you're implementing a non-trivial change — a feature, a multi-file bug fix, a refactor, or anything spec-driven. It is the procedural runbook for the ralph loop documented in `docs/CONVENTIONS.md` §12 — plan → execute → gates → review → fix — extended with parallel reviewer dispatch and supervisor mode when the plan permits. Default to this skill for any task larger than a one-line edit.

Use this skill when the user wants to fix a bug — a deviation between current behaviour and intended behaviour in code that already exists. Triggers on "fix bug", "fix this bug", "diagnose and fix", "investigate this regression", "this is broken", "post-mortem this", "why is X failing". Do NOT use for new features (use `new-spec`) or refactors that don't fix incorrect behaviour. Inkwell-specific: the regression test BEFORE the fix is mandatory and lands in the same commit (`docs/CONVENTIONS.md §5.7`).