@aitne-sh/aitne 0.1.7 → 0.1.8

package/agent-assets/skills/gmail-lifestyle/SKILL.md

@@ -0,0 +1,224 @@
+---
+name: gmail-lifestyle
+description: Load when the user mentions receipts / expenses / flights / hotels / trains / commute / travel time / a booking — Gmail-observer-derived travel bookings, calendar-event commute calculations, and receipt save-to-external-vault all live here.
+allowed-tools:
+  - Bash(curl *)
+  - Read
+---
+
+# Gmail Lifestyle — travel bookings, commute, receipts
+
+This skill merges three closely-related surfaces that all depend on
+data the daemon's **Gmail observer** has scanned: travel bookings,
+commute / travel-time calculations over calendar events, and receipt
+attachments saved into the user's external Obsidian vault.
+
+It is conditionally loaded — see the manifest predicate
+`gmailLifestyleActive(db)` / `gmailLifestyleActiveForDm(db, msg)`
+in `packages/daemon/src/core/skills-manifest.ts`. Routines load it
+when there is fresh-or-pending data; DM events also load it on
+trigger phrases (`receipt`, `expense`, `flight`, `train`,
+`commute`, `travel time`, plus the user's primary-language
+equivalents — the predicate handles both the structured triggers
+and the message-text triggers).
+
+Output language: Policy C for user-facing summaries — see
+`<output_language_policy>`. Path patterns and external API field
+names stay verbatim.
+
+---
+
+## Travel bookings
+
+The daemon's Gmail observer detects booking confirmation emails from
+airlines, hotels, OTAs, restaurant reservation platforms, and rail
+services. Data is stored in the `travel_bookings` SQLite table.
+
+### When to use
+
+- **Morning routine** — surface upcoming travel / bookings within the
+  next 7 days inside today.md `## Travel & Reservations`.
+- **Evening review** — report newly detected bookings (today's
+  `createdAt`).
+- **User asks about trips / reservations** — query bookings and
+  summarize.
+- **Pre-trip reminders** — surface upcoming travel the day before
+  departure.
+
+### Workflow
+
+1. Fetch upcoming bookings from `/api/travel-bookings/upcoming`.
+2. For morning routine, highlight bookings within the next 7 days.
+3. For evening review, check for newly detected bookings (today's
+   `createdAt`).
+
+### API
+
+Full `/api/travel-bookings` reference (GET filter + upcoming +
+PATCH status) is in the dedicated reference below.
+
+{{> ref:travel-bookings-api }}
+
+### Formatting
+
+Morning routine — today.md:
+
+```
+## Travel & Reservations
+Upcoming flight: United to SFO (May 15) — confirmation ABC123
+Hotel: Marriott SF (May 15-17) — confirmation XYZ789
+Restaurant: OpenTable reservation tonight 19:00
+```
+
+Omit the section when no upcoming bookings within 7 days.
+
+Evening review:
+
+```
+## New Bookings Detected
+- United flight: May 15, confirmation ABC123, $350
+```
+
+Booking type display names: flight → Flight, hotel → Hotel,
+restaurant → Restaurant, train → Train, bus → Bus, other →
+Reservation.
+
+---
+
+## Travel time / commute
+
+Uses the Google Maps Directions API to estimate travel time between
+locations. Computes departure times for calendar events with a
+`location` field.
+
+**Prerequisite**: `googleMapsApiKey` configured in the daemon's
+secret store, with the Directions API enabled.
+
+### When to use
+
+- **Morning routine** — for today's calendar events with a location,
+  compute departure times and add to today.md `## Commute & Travel`.
+- **User asks about commute / travel time** — query specific routes.
+- **Pre-event reminders** — DM departure-time suggestions.
+
+### Sourcing today's events
+
+The right fetch path depends on Google Calendar's current mode
+(read `<integration_modes>` injected at session start):
+
+<!-- mode:direct:google_calendar -->
+Direct mode → `GET /api/calendar/events?date=today&days=1`
+(see the `external-services` skill).
+<!-- /mode:direct:google_calendar -->
+<!-- mode:delegated-same:google_calendar -->
+Same-backend delegated → use this session backend's native Calendar
+list-events MCP tool. `/api/calendar/events` returns 410.
+<!-- /mode:delegated-same:google_calendar -->
+<!-- mode:delegated-cross:google_calendar -->
+Cross-backend delegated → `POST /api/integrations/google_calendar/exec`
+with a natural-language `task` + `outputSchema` (see the
+`external-services` skill — cross-backend variant for worked
+examples).
+<!-- /mode:delegated-cross:google_calendar -->
+<!-- mode:native:google_calendar -->
+Native mode → use this session backend's native Calendar list-events
+MCP tool (same call shape as `delegated-same`). The materialized
+`external-services` skill body (`SKILL.native.<session-backend>.md`)
+lists the per-backend tool names. The daemon does not proxy in
+native mode; `/api/calendar/events` returns 410 and
+`/api/integrations/google_calendar/exec` returns 410 too.
+<!-- /mode:native:google_calendar -->
+<!-- mode:disabled:google_calendar -->
+Disabled → skip this section; there is no calendar to source events
+from.
+<!-- /mode:disabled:google_calendar -->
+
+### API
+
+Full `/api/travel-time` reference (point-to-point + for-event) is in
+the dedicated reference below.
+
+{{> ref:travel-time-api }}
+
+### Formatting — today.md
+
+```
+## Commute & Travel
+14:00 Team meeting @ WeWork Times Square — depart by 13:15 (transit, 40 min)
+18:30 Dinner @ Restaurant ABC — depart by 18:00 (transit, 25 min)
+```
+
+Only include events that have a `location` field. Omit the section
+when no events have locations today.
+
+Mode display names: transit → Transit, driving → Driving, walking →
+Walking, bicycling → Bicycle.
+
+---
+
+## Receipts
+
+The daemon's Gmail observer scans travel-booking emails for PDF /
+image attachments and can retain previously detected generic
+documents. Attachment metadata is stored in the `receipts` SQLite
+table. Actual files are downloaded on demand and can be saved to the
+user's **external Obsidian vault**.
+
+### Primary vault vs external vault — read first
+
+> **WARNING — do not confuse vaults.** Receipts save into the
+> **external** Obsidian vault (user's personal knowledge base reached
+> via `/api/obsidian/*`), **not** the primary management store
+> reached via `/api/context/*`. The agent's own state files
+> (`today.md`, `roadmap.md`, `projects/*`, `user/*`, `rules/*`,
+> `routines/*`, `agent/*`) live in the primary store and must
+> **never** receive receipt attachments. See the
+> `external-services` skill's obsidian reference for the external
+> vault's full CRUD surface.
+
+`receipts.obsidianPath` is a path **inside the external vault**.
+
+### When to use
+
+- **User asks about receipts** — list detected receipts, check save
+  status.
+- **Tax preparation season** — generate annual receipt list, save
+  unsaved receipts.
+- **Monthly / yearly review** — report on receipt-collection
+  completeness.
+
+### Workflow
+
+1. Fetch the receipt list from `/api/receipts`.
+2. To save a receipt to the external Obsidian vault:
+   a. Download via `POST /api/receipts/:id/download` (binary stream).
+   b. Save to the vault via `POST /api/obsidian/notes` (see the
+      `external-services` obsidian reference for path conventions).
+   c. Update the receipt record with the vault-relative path via
+      `PATCH /api/receipts/:id` `{"obsidianPath": "..."}`.
+3. For tax preparation, filter by date range and category.
+
+### API
+
+Full `/api/receipts` reference (GET filter + summary + download +
+PATCH) plus the external-vault save convention
+(`receipts/YYYY/MM/<merchant>-<date>.<ext>`) is in the dedicated
+reference below.
+
+{{> ref:receipts-api }}
+
+---
+
+## When NOT to act
+
+- If the predicate gates above are false (no fresh bookings, no
+  unsaved receipts, no trigger phrase), this skill is not loaded —
+  the manifest layer handles that decision. If you see this body
+  anyway, it means the predicate matched something concrete; do not
+  guess that the user wants travel / commute / receipt work without
+  evidence in the conversation or the DB.
+- Do not write receipts to `/api/context/*` — that targets the
+  primary management vault. See the §"Primary vault vs external
+  vault" warning above.
+- Bulk receipt operations (save-all, reclassify-all) need explicit
+  user confirmation; surface the count and criteria first.

package/agent-assets/skills/gmail-lifestyle/references/receipts-api.md

@@ -0,0 +1,93 @@
+---
+kind: reference
+name: receipts-api
+description: /api/receipts reference — list / filter, download, save-to-external-Obsidian-vault, reclassify, and summary endpoints for Gmail-observer-flagged attachments.
+---
+
+# `/api/receipts` reference
+
+The daemon's Gmail observer scans travel-booking emails for PDF /
+image attachments and can retain previously detected generic
+documents. Attachment metadata is stored in the `receipts` SQLite
+table. Actual files are downloaded on demand and saved to the user's
+**external Obsidian vault** (NOT the primary management vault — see
+the `## Receipts` section of the parent skill for the vault-routing
+warning).
+
+## GET /api/receipts
+
+```bash
+# All receipts
+curl -s "http://localhost:8321/api/receipts?limit=50"
+
+# Unsaved receipts only
+curl -s "http://localhost:8321/api/receipts?saved=false"
+
+# Filter by category
+curl -s "http://localhost:8321/api/receipts?category=document"
+```
+
+| Param | Type | Default | Description |
+|-------|------|---------|-------------|
+| `category` | string | — | document, travel |
+| `saved` | boolean | — | true = saved to Obsidian, false = not yet saved |
+| `limit` | number | 50 | Max results (1–200) |
+
+Response:
+
+```json
+{
+  "receipts": [
+    {
+      "id": 1,
+      "providerMsgId": "18f...",
+      "attachmentId": "ANGj...",
+      "filename": "receipt.pdf",
+      "mimeType": "application/pdf",
+      "sizeBytes": 45000,
+      "category": "document",
+      "obsidianPath": null,
+      "savedAt": null,
+      "createdAt": "2026-04-12T10:00:00Z"
+    }
+  ],
+  "total": 1
+}
+```
+
+## GET /api/receipts/summary
+
+```bash
+curl -s "http://localhost:8321/api/receipts/summary"
+```
+
+Returns counts: `{ total, saved, unsaved, byCategory: [{ category, count }] }`.
+
+## POST /api/receipts/:id/download
+
+```bash
+curl -s -X POST "http://localhost:8321/api/receipts/1/download" -o receipt.pdf
+```
+
+Binary stream of the original attachment.
+
+## PATCH /api/receipts/:id
+
+```bash
+# Mark as saved to external Obsidian vault
+curl -s -X PATCH "http://localhost:8321/api/receipts/1" \
+  -H "Content-Type: application/json" \
+  -d '{"obsidianPath": "receipts/2026/04/amazon-receipt.pdf"}'
+
+# Reclassify a receipt
+curl -s -X PATCH "http://localhost:8321/api/receipts/1" \
+  -H "Content-Type: application/json" \
+  -d '{"category": "travel"}'
+```
+
+## External-vault save convention
+
+Save receipts to `receipts/YYYY/MM/<merchant>-<date>.<ext>` inside
+the external Obsidian vault.
+
+Example: `receipts/2026/04/amazon-2026-04-12.pdf`.

package/agent-assets/skills/gmail-lifestyle/references/travel-bookings-api.md

@@ -0,0 +1,75 @@
+---
+kind: reference
+name: travel-bookings-api
+description: /api/travel-bookings reference — filter / upcoming / PATCH status for Gmail-observer-detected flight, hotel, train, restaurant, and bus reservations.
+---
+
+# `/api/travel-bookings` reference
+
+The daemon's Gmail observer detects booking confirmation emails from
+airlines, hotels, OTAs, restaurant reservation platforms, and rail
+services. Data is stored in the `travel_bookings` SQLite table.
+
+## GET /api/travel-bookings
+
+```bash
+# All bookings
+curl -s "http://localhost:8321/api/travel-bookings?limit=20"
+
+# Filter by type
+curl -s "http://localhost:8321/api/travel-bookings?type=flight"
+
+# Upcoming only
+curl -s "http://localhost:8321/api/travel-bookings?status=upcoming"
+
+# Date range
+curl -s "http://localhost:8321/api/travel-bookings?from=2026-04-01&to=2026-05-01"
+```
+
+| Param | Type | Default | Description |
+|-------|------|---------|-------------|
+| `type` | string | — | flight, hotel, restaurant, train, bus, other |
+| `status` | string | all | upcoming, completed, cancelled, all |
+| `from` | ISO date | — | Bookings with start_date on or after |
+| `to` | ISO date | — | Bookings with start_date before |
+| `limit` | number | 50 | Max results (1–200) |
+
+Response:
+
+```json
+{
+  "bookings": [
+    {
+      "id": 1,
+      "type": "flight",
+      "provider": "United",
+      "destination": null,
+      "startDate": "2026-05-15T10:30:00Z",
+      "endDate": null,
+      "confirmationNumber": "ABC123",
+      "amount": 350,
+      "currency": "USD",
+      "status": "upcoming",
+      "providerMsgId": "18f...",
+      "createdAt": "2026-04-12T10:00:00Z"
+    }
+  ],
+  "total": 1
+}
+```
+
+## GET /api/travel-bookings/upcoming
+
+Convenience endpoint, sorted by start date.
+
+```bash
+curl -s "http://localhost:8321/api/travel-bookings/upcoming?limit=10"
+```
+
+## PATCH /api/travel-bookings/:id
+
+```bash
+curl -s -X PATCH "http://localhost:8321/api/travel-bookings/1" \
+  -H "Content-Type: application/json" \
+  -d '{"status": "completed"}'
+```

package/agent-assets/skills/gmail-lifestyle/references/travel-time-api.md

@@ -0,0 +1,59 @@
+---
+kind: reference
+name: travel-time-api
+description: /api/travel-time reference — Google Maps Directions wrapper. Estimate door-to-door duration and compute departure time for a calendar event with location.
+---
+
+# `/api/travel-time` reference
+
+Uses the Google Maps Directions API. Prerequisite: `googleMapsApiKey`
+configured in the daemon's secret store, with the Directions API
+enabled.
+
+## GET /api/travel-time
+
+Estimate travel time between two locations.
+
+```bash
+# Transit (default)
+curl -s "http://localhost:8321/api/travel-time?origin=Grand+Central&destination=Times+Square"
+
+# Driving with arrival time
+curl -s "http://localhost:8321/api/travel-time?origin=Brooklyn&destination=Newark&mode=driving&arrival=2026-04-12T14:00:00-04:00"
+```
+
+| Param | Type | Default | Description |
+|-------|------|---------|-------------|
+| `origin` | string | (required) | Origin address or place name |
+| `destination` | string | (required) | Destination address or place name |
+| `mode` | string | transit | driving, transit, walking, bicycling |
+| `arrival` | ISO 8601 | — | Desired arrival time (computes departure time) |
+
+Response:
+
+```json
+{
+  "origin": "Grand Central Terminal, NY",
+  "destination": "Times Square, NY",
+  "mode": "transit",
+  "durationSeconds": 1380,
+  "durationText": "23 mins",
+  "distanceMeters": 8500,
+  "distanceText": "8.5 km",
+  "departBy": "2026-04-12T13:34:00.000Z"
+}
+```
+
+## GET /api/travel-time/for-event/:eventId
+
+```bash
+curl -s "http://localhost:8321/api/travel-time/for-event/abc123?origin=Home&mode=transit"
+```
+
+| Param | Type | Default | Description |
+|-------|------|---------|-------------|
+| `origin` | string | (required) | Your starting location |
+| `mode` | string | transit | Travel mode |
+
+Response includes both `event` and `travelTime` blocks; see the route
+implementation for full shape.

package/agent-assets/skills/mail/SKILL.delegated.claude.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in cross-backend delegated mode (DM session is Claude Code; `delegatedBackend` is non-Claude). Gmail accounts route through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct-mode `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is cross-backend delegated from a Claude DM session (`delegatedBackend` is non-Claude). Gmail routes through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 allowed-tools:
   - Bash(curl *)
   - Read

package/agent-assets/skills/mail/SKILL.delegated.codex.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in cross-backend delegated mode (DM session is Codex; `delegatedBackend` is non-Codex). Gmail accounts route through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct-mode `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is cross-backend delegated from a Codex CLI DM session (`delegatedBackend` is non-Codex). Gmail routes through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 ---
 
 # Mail (delegated, cross-backend)

package/agent-assets/skills/mail/SKILL.delegated.gemini.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in cross-backend delegated mode (DM session is Gemini; `delegatedBackend` is non-Gemini). Gmail accounts route through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct-mode `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is cross-backend delegated from a Gemini CLI DM session (`delegatedBackend` is non-Gemini). Gmail routes through `POST /api/integrations/gmail/exec`; non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 ---
 
 # Mail (delegated, cross-backend)

package/agent-assets/skills/mail/SKILL.md

@@ -220,122 +220,17 @@ curl -s "http://localhost:8321/api/mail/ACCT/messages/MSG/body?format=raw&chunk=
 
 ## 6. Worked examples
 
-### Reply with context
-```bash
-# 1. Find the thread — start local.
-curl -s "http://localhost:8321/api/mail/search?q=from:alice+proposal&limit=5"
-# → pick the hit, note accountId + providerMsgId.
-
-# 2. Fetch the thread.
-curl -s "http://localhost:8321/api/mail/acct-1/threads/THREAD_ID"
-# → last message has rfc822MsgId, references[], providerMsgId.
-
-# 3. Create a draft threaded to it. Drafts are Autonomous tier.
-curl -sX POST "http://localhost:8321/api/mail/acct-1/drafts" \
-  -H "Content-Type: application/json" \
-  -d '{
-    "to": ["alice@example.com"],
-    "subject": "Re: Proposal",
-    "textBody": "Thanks Alice — ...",
-    "reply": {
-      "inReplyToRfc822Id": "<abc@mail.example.com>",
-      "references": ["<root@mail.example.com>", "<abc@mail.example.com>"],
-      "providerThreadId": "THREAD_ID",
-      "parentProviderMsgId": "PARENT_MSG_ID"
-    }
-  }'
-```
+Three direct-mode worked examples — reply with context, file a
+message (read + tag + archive), cross-account search → pick account
+→ send — are in the examples reference below. The delegated /
+native variants of this skill carry their own examples.
 
-### File a message (read + tag + archive)
-```bash
-curl -sX POST "http://localhost:8321/api/mail/acct-1/messages/MSG/read" \
-  -d '{"read": true}'
-curl -sX POST "http://localhost:8321/api/mail/acct-1/messages/MSG/tags" \
-  -d '{"add": ["followup"], "remove": []}'
-curl -sX POST "http://localhost:8321/api/mail/acct-1/messages/MSG/archive"
-```
-On IMAP, confirm `followup` is in `GET /mail/:acct/tags` `.userDefined`
-first — unknown keywords get dropped.
-
-### Cross-account search → pick account → send
-```bash
-# Find recipient's earlier emails across all accounts.
-curl -s "http://localhost:8321/api/mail/search?q=from:bob@acme.com&limit=10"
-# → hits carry accountId. Use whichever account received the earlier thread
-#   so the reply comes from a familiar address.
-
-curl -sX POST "http://localhost:8321/api/mail/acct-2/messages/send" \
-  -H "Content-Type: application/json" \
-  -d '{"to": ["bob@acme.com"], "subject": "...", "textBody": "..."}'
-```
+{{> ref:examples }}
 
 ## 7. API reference
 
-Base URL `http://localhost:8321`. `ACCT` = accountId from `accounts.md`.
-
-### Accounts
-```bash
-curl -s "http://localhost:8321/api/mail/accounts?active=1"
-# → { accounts: [{ id, kind, email, label?, authStatus, idleEnabled, active, createdAt }, ...] }
-```
-
-### Search (local FTS5, cross-account)
-```bash
-curl -s "http://localhost:8321/api/mail/search?q=...&limit=50&accountId=ACCT"
-# → { results: [{ accountId, providerMsgId, subject, snippet, receivedAtUtc,
-#                 from: { email } | null, isRead }], count, query }
-```
-
-### Read
-```bash
-# List / search via the provider.
-curl -s "http://localhost:8321/api/mail/ACCT/messages?q=is:unread&limit=20"
-# → { messages: [{ providerMsgId, threadId, from, subject, snippet,
-#                  receivedAtUtc, isRead, flags, hasAttachment }] }
-
-curl -s "http://localhost:8321/api/mail/ACCT/messages/MSG_ID"
-# → { message: { ..., body: { text, html }, attachments: [...] } }
-
-curl -s "http://localhost:8321/api/mail/ACCT/threads/THREAD_ID"
-# → { thread: { threadId, messages: [...], status: "full"|"partial", missingAncestors? } }
-
-curl -s "http://localhost:8321/api/mail/ACCT/folders"
-curl -s "http://localhost:8321/api/mail/ACCT/tags"
-```
-
-### Send / draft
-```bash
-# Direct send — Autonomous; rejected with 403 when the user has denied
-# the send tool. Call /api/notify yourself if the user should know.
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/send" \
-  -H "Content-Type: application/json" \
-  -d '{"to": [...], "subject": "...", "textBody": "...", "reply"?: {...}}'
-# → { result: { id, isDraft: false, rfc822MsgId?, warnings? } }
-
-# Draft CRUD — Autonomous tier.
-curl -s "http://localhost:8321/api/mail/ACCT/drafts"
-curl -s "http://localhost:8321/api/mail/ACCT/drafts/DRAFT_ID"
-curl -sX POST   "http://localhost:8321/api/mail/ACCT/drafts" -d '{...}'
-curl -sX PATCH  "http://localhost:8321/api/mail/ACCT/drafts/DRAFT_ID" -d '{...}'
-# PATCH response: { status, id, warnings? }
-# - On Outlook, `warnings: ["reply_threading_immutable_after_create"]` if
-#   `reply` was supplied — reply headers are fixed at createDraft time.
-curl -sX DELETE "http://localhost:8321/api/mail/ACCT/drafts/DRAFT_ID"
-curl -sX POST   "http://localhost:8321/api/mail/ACCT/drafts/DRAFT_ID/send"
-```
+Direct-mode `/api/mail/*` surface — accounts, search, read,
+send / draft, modify / move, health — is in the api reference below.
+`ACCT` is the `accountId` resolved per §1.
 
-### Modify / move
-```bash
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/MSG_ID/read"    -d '{"read": true}'
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/MSG_ID/tags"    -d '{"add": ["Starred"], "remove": []}'
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/MSG_ID/trash"
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/MSG_ID/untrash"
-curl -sX POST "http://localhost:8321/api/mail/ACCT/messages/MSG_ID/archive"
-```
-
-### Health
-```bash
-curl -s "http://localhost:8321/api/mail/ACCT/health"
-# → { accountId, lastPollAtUtc, lastError, lastErrorAtUtc,
-#     consecutiveErrorCount, idleFallbackUntilUtc }
-```
+{{> ref:api }}

package/agent-assets/skills/mail/SKILL.native.claude.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in native mode bound to Claude (`nativeBackend === "claude"`). Use the in-session Gmail connector your harness exposes directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is in native mode bound to Claude (`nativeBackend === "claude"`). Use the in-session Gmail connector directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 allowed-tools:
   - Bash(curl *)
   - Read

package/agent-assets/skills/mail/SKILL.native.codex.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in native mode bound to Codex (`nativeBackend === "codex"`). Use the in-session Gmail connector your Codex harness exposes directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is in native mode bound to Codex (`nativeBackend === "codex"`). Use the Gmail connector your Codex harness exposes directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 allowed-tools:
   - Bash(curl *)
   - Read

package/agent-assets/skills/mail/SKILL.native.gemini.md

@@ -1,6 +1,6 @@
 ---
 name: mail
-description: Load when the task touches Gmail and Gmail is in native mode bound to Gemini (`nativeBackend === "gemini"`). Use the in-session Gmail connector your Gemini harness exposes directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep the direct `/api/mail/*` surface.
+description: Load when the task touches Gmail AND Gmail is in native mode bound to Gemini (`nativeBackend === "gemini"`). Use the Gmail connector your Gemini harness exposes directly; the daemon does not proxy Gmail. Non-Gmail accounts (IMAP/Outlook/iCloud/Yahoo) keep `/api/mail/*`.
 allowed-tools:
   - Bash(curl *)
   - Read