@inboxapi/cli 0.3.0 → 0.3.2

package/README.md

@@ -147,11 +147,13 @@ inboxapi restore ./my-backup
 
 ### `setup-skills`
 
-Installs Claude Code skills (slash commands) and hooks into the current project. Skills add email workflows like `/check-inbox`, `/compose`, and `/email-search` directly into Claude Code. Hooks provide automatic credential checks, email send guardrails, and activity logging.
+Installs InboxAPI skills for AI coding agents. Supports **Claude Code**, **Codex CLI**, **Gemini CLI**, and **OpenCode**. Auto-detects installed agents and prompts for confirmation, or use flags for non-interactive installation.
 
 ```bash
-inboxapi setup-skills
-inboxapi setup-skills --force  # Overwrite existing skills and hooks
+inboxapi setup-skills              # Auto-detect agents, interactive prompt
+inboxapi setup-skills --all        # Install for all 4 agents
+inboxapi setup-skills --claude --codex  # Install for specific agents
+inboxapi setup-skills --force      # Overwrite existing skills and hooks
 ```
 
 ## CLI Commands
@@ -279,14 +281,24 @@ When prompted, enter:
 codex mcp add inboxapi inboxapi
 ```
 
-## Skills for Claude Code
+## Skills for AI Coding Agents
 
-InboxAPI includes a set of skills — Claude Code slash commands — that add guided email workflows to your project. Install them with:
+InboxAPI includes skills — slash commands and guided workflows — for multiple AI coding agents. Install them with:
 
 ```bash
-inboxapi setup-skills
+inboxapi setup-skills        # Auto-detect and install
+inboxapi setup-skills --all  # Install for all agents
 ```
 
+Skills are installed to agent-specific directories:
+
+| Agent | Install Directory |
+|-------|-------------------|
+| Claude Code | `.claude/skills/` |
+| Codex CLI | `.agents/skills/` |
+| Gemini CLI | `.gemini/skills/` |
+| OpenCode | `.opencode/commands/` |
+
 ### Available Skills
 
 | Skill | Description |
@@ -297,11 +309,11 @@ inboxapi setup-skills
 | `/email-reply` | Reply to an email with full thread context and preview before sending |
 | `/email-digest` | Generate a structured digest of recent email activity grouped by threads |
 | `/email-forward` | Forward an email to another recipient with an optional note |
-| `/setup-inboxapi` | Configure InboxAPI MCP server and install skills into a Claude Code project |
+| `/setup-inboxapi` | Configure InboxAPI MCP server and install skills for your AI coding agent |
 
-### Hooks
+### Hooks (Claude Code only)
 
-The `setup-skills` command also installs three hooks that run automatically:
+The `setup-skills` command also installs three hooks for Claude Code that run automatically:
 
 | Hook | Type | Description |
 |------|------|-------------|

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@inboxapi/cli",
-  "version": "0.3.0",
+  "version": "0.3.2",
   "description": "📧 Email for your AI 🤖",
   "main": "index.js",
   "bin": {
@@ -8,7 +8,7 @@
   },
   "files": [
     "index.js",
-    "claude"
+    "skills"
   ],
   "repository": {
     "type": "git",
@@ -28,10 +28,10 @@
     "test": "cargo test"
   },
   "optionalDependencies": {
-    "@inboxapi/cli-darwin-arm64": "0.3.0",
-    "@inboxapi/cli-darwin-x64": "0.3.0",
-    "@inboxapi/cli-linux-arm64": "0.3.0",
-    "@inboxapi/cli-linux-x64": "0.3.0",
-    "@inboxapi/cli-win32-x64": "0.3.0"
+    "@inboxapi/cli-darwin-arm64": "0.3.2",
+    "@inboxapi/cli-darwin-x64": "0.3.2",
+    "@inboxapi/cli-linux-arm64": "0.3.2",
+    "@inboxapi/cli-linux-x64": "0.3.2",
+    "@inboxapi/cli-win32-x64": "0.3.2"
   }
 }

package/{claude/skills → skills/claude}/check-inbox/SKILL.md

@@ -11,10 +11,9 @@ Fetch and display a summary of recent emails from the user's InboxAPI inbox.
 
 ## Steps
 
-1. Call the `mcp__inboxapi__whoami` tool to identify the current account and email address
-2. Call `mcp__inboxapi__get_email_count` to show the total number of emails
-3. Call `mcp__inboxapi__get_emails` with:
-   - `limit`: Use `$ARGUMENTS` if provided, otherwise default to `20`
+1. Run: `npx -y @inboxapi/cli whoami` to identify the current account and email address
+2. Run: `npx -y @inboxapi/cli get-email-count` to show the total number of emails
+3. Run: `npx -y @inboxapi/cli get-emails --limit <N>` where `<N>` is `$ARGUMENTS` if provided, otherwise `20`
 4. Present results in a formatted table with columns:
    - **From** — sender name or address
    - **Subject** — email subject line (truncated to 60 chars)
@@ -35,5 +34,6 @@ If the inbox is empty, display: "Your inbox is empty. Your email address is <ema
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - Do NOT read full email bodies — only show the summary list
-- If the user asks to read a specific email after seeing the list, use `mcp__inboxapi__get_email` with the email ID
+- If the user asks to read a specific email after seeing the list, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID

package/{claude/skills → skills/claude}/compose/SKILL.md

@@ -12,11 +12,11 @@ Guide the user through composing and sending an email safely.
 
 ## Steps
 
-1. **Identify sender**: Call `mcp__inboxapi__whoami` to get the current account email address
+1. **Identify sender**: Run: `npx -y @inboxapi/cli whoami` to get the current account email address
 
 2. **Resolve recipient**:
    - If `$ARGUMENTS` is provided, use it as the recipient hint
-   - Call `mcp__inboxapi__get_addressbook` to check for matching contacts
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
    - If multiple matches found, ask the user to pick one
    - If no match, ask the user to confirm or provide the full email address
 
@@ -41,13 +41,17 @@ Guide the user through composing and sending an email safely.
 
 6. **Confirm**: Ask the user to confirm: "Send this email? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__send_email` with `to`, `subject`, and `body`
+7. **Send**: Run: `npx -y @inboxapi/cli send-email --to "<recipient>" --subject "<subject>" --body "<body>"`
 
 8. **Confirm delivery**: Report the result to the user
 
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
 ## Rules
 
 - ALWAYS show a preview before sending
-- ALWAYS ask for explicit confirmation before calling send_email
+- ALWAYS ask for explicit confirmation before calling send-email
 - NEVER send an email without the user confirming
 - If the user cancels, acknowledge and do not send

package/{claude/skills → skills/claude}/email-digest/SKILL.md

@@ -13,13 +13,13 @@ Generate a structured digest of recent email activity.
 
 1. **Determine timeframe**: Use `$ARGUMENTS` if provided (e.g., "today", "this week", "last 3 days"), otherwise default to "last 24 hours"
 
-2. **Get account info**: Call `mcp__inboxapi__whoami` for the account email
+2. **Get account info**: Run: `npx -y @inboxapi/cli whoami` for the account email
 
-3. **Get total count**: Call `mcp__inboxapi__get_email_count` for inbox statistics
+3. **Get total count**: Run: `npx -y @inboxapi/cli get-email-count` for inbox statistics
 
-4. **Fetch recent emails**: Call `mcp__inboxapi__get_emails` with an appropriate limit (50 for digest)
+4. **Fetch recent emails**: Run: `npx -y @inboxapi/cli get-emails --limit 50`
 
-5. **Group by thread**: For threads with multiple emails, call `mcp__inboxapi__get_thread` to understand the conversation
+5. **Group by thread**: For threads with multiple emails, run `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` to understand the conversation
 
 6. **Generate digest** with these sections:
 
@@ -53,6 +53,7 @@ Generate a structured digest of recent email activity.
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - Focus on actionable insights, not raw data
 - Highlight emails that likely need a response
 - Keep the digest concise — summarize, don't reproduce full emails

package/{claude/skills → skills/claude}/email-forward/SKILL.md

@@ -13,8 +13,8 @@ Help the user forward an email to another recipient.
 ## Steps
 
 1. **Find the email to forward**:
-   - If `$ARGUMENTS` looks like an email ID, call `mcp__inboxapi__get_email` directly
-   - Otherwise, call `mcp__inboxapi__search_emails` with the argument
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument
    - If multiple results, show them and ask the user to pick one
 
 2. **Show email content**: Display the email being forwarded:
@@ -29,7 +29,7 @@ Help the user forward an email to another recipient.
 
 3. **Resolve recipient**:
    - Ask "Who do you want to forward this to?"
-   - Call `mcp__inboxapi__get_addressbook` to check for matching contacts
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
    - Confirm the recipient email address
 
 4. **Optional message**: Ask "Add a message? (or press enter to skip)"
@@ -44,7 +44,11 @@ Help the user forward an email to another recipient.
 
 6. **Confirm**: Ask "Forward this email? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__forward_email` with the email ID, recipient, and optional message
+7. **Send**: Run: `npx -y @inboxapi/cli forward-email --message-id "<id>" --to "<recipient>"` (add `--note "<message>"` if provided)
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 
 ## Rules
 

package/{claude/skills → skills/claude}/email-reply/SKILL.md

@@ -13,11 +13,11 @@ Help the user reply to an email with full thread context.
 ## Steps
 
 1. **Find the email**:
-   - If `$ARGUMENTS` looks like an email ID (alphanumeric string), call `mcp__inboxapi__get_email` directly
-   - Otherwise, call `mcp__inboxapi__search_emails` with the argument as subject/keyword
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument as subject/keyword
    - If multiple results, present them and ask the user to pick one
 
-2. **Load thread context**: Call `mcp__inboxapi__get_thread` with the email's thread ID to show the full conversation
+2. **Load thread context**: Run: `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` with the email's message ID to show the full conversation
 
 3. **Display thread**: Show the conversation history in chronological order:
    ```
@@ -45,7 +45,11 @@ Help the user reply to an email with full thread context.
 
 6. **Confirm**: Ask "Send this reply? (yes/no)"
 
-7. **Send**: Call `mcp__inboxapi__send_reply` with the email ID and reply body
+7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 
 ## Rules
 

package/{claude/skills → skills/claude}/email-search/SKILL.md

@@ -14,13 +14,13 @@ Search emails using natural language and present results clearly.
 1. Take the user's query from `$ARGUMENTS`
    - If no arguments provided, ask: "What are you looking for?"
 
-2. Translate the natural language query into a `mcp__inboxapi__search_emails` call:
-   - Extract sender hints (e.g., "from John" -> search by sender)
-   - Extract subject hints (e.g., "about invoices" -> search by subject)
-   - Extract date hints (e.g., "last week", "yesterday")
-   - Use the full query as the search term
+2. Translate the natural language query into CLI flags for `search-emails`:
+   - Extract sender hints (e.g., "from John" -> `--sender "John"`)
+   - Extract subject hints (e.g., "about invoices" -> `--subject "invoices"`)
+   - Extract date hints (e.g., "last week", "yesterday" -> `--since "..."`, `--until "..."`)
+   - Combine with `--limit` as needed
 
-3. Call `mcp__inboxapi__search_emails` with the interpreted parameters
+3. Run: `npx -y @inboxapi/cli search-emails` with the appropriate flags (`--sender "..."`, `--subject "..."`, `--since "..."`, `--until "..."`)
 
 4. Present results in a formatted table:
    ```
@@ -30,10 +30,14 @@ Search emails using natural language and present results clearly.
 
 5. After showing results, offer: "Would you like to read any of these emails? Provide the number."
 
-6. If the user picks one, call `mcp__inboxapi__get_email` with the email ID
+6. If the user picks one, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID
 
 7. If no results, suggest alternative searches or broader terms
 
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
 ## Examples
 
 - `/email-search invoices from accounting` -> search for "invoices" filtered by sender containing "accounting"

package/{claude/skills → skills/claude}/setup-inboxapi/SKILL.md

@@ -1,13 +1,13 @@
 ---
 name: setup-inboxapi
-description: Set up InboxAPI email tools in your Claude Code project. Adds MCP server config, installs skills, and configures safety hooks. Use when the user wants to configure InboxAPI for their project.
+description: Set up InboxAPI email tools in your AI coding agent. Adds MCP server config, installs skills, and configures safety hooks. Use when the user wants to configure InboxAPI for their project.
 user-invocable: true
 disable-model-invocation: true
 ---
 
 # Setup InboxAPI
 
-Configure InboxAPI email tools for this Claude Code project.
+Configure InboxAPI email tools for this project. Supports Claude Code, Codex CLI, Gemini CLI, and OpenCode.
 
 ## Steps
 
@@ -28,10 +28,22 @@ Configure InboxAPI email tools for this Claude Code project.
      }
      ```
 
-3. **Install skills**: Run `npx -y @inboxapi/cli setup-skills` to copy bundled skills and hooks into the project's `.claude/` directory
+   **For other agents:**
+   - **Codex CLI**: `codex mcp add inboxapi -- npx -y @inboxapi/cli`
+   - **Gemini CLI**: Add to `settings.json` under `mcpServers`:
+     ```json
+     { "mcpServers": { "inboxapi": { "command": "npx", "args": ["-y", "@inboxapi/cli"] } } }
+     ```
+   - **OpenCode**: Add to `opencode.json` under `mcp`:
+     ```json
+     { "mcp": { "inboxapi": { "command": "npx", "args": ["-y", "@inboxapi/cli"] } } }
+     ```
+
+3. **Install skills**: Run `npx -y @inboxapi/cli setup-skills` to install skills for detected agents
+   - Use `--all` to install for all agents, or `--claude`, `--codex`, `--gemini`, `--opencode` for specific ones
 
 4. **Verify credentials**:
-   - Call `mcp__inboxapi__whoami` to check if credentials are set up
+   - Run: `npx -y @inboxapi/cli whoami` to check if credentials are set up
    - If not authenticated, instruct the user: "Run `npx -y @inboxapi/cli login` in a terminal to authenticate"
 
 5. **Show summary**:
@@ -49,7 +61,7 @@ Configure InboxAPI email tools for this Claude Code project.
      /email-digest — Email activity digest
      /email-forward — Forward emails
 
-   Installed Hooks:
+   Installed Hooks (Claude Code only):
      PreToolUse  — Email send guard (reviews before sending)
      PostToolUse — Activity logger (audit trail)
      SessionStart — Credential check (verifies auth on startup)
@@ -61,6 +73,7 @@ Configure InboxAPI email tools for this Claude Code project.
 
 ## Notes
 
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
 - This skill is safe to run multiple times — it won't duplicate entries or overwrite local edits
 - Existing `.mcp.json` entries, skill files, and hook files with local edits are preserved
 - `.claude/settings.json` is merged with new hook config (may be reformatted when hooks are updated)

package/skills/codex/check-inbox/SKILL.md

@@ -0,0 +1,37 @@
+---
+name: check-inbox
+description: "Check your InboxAPI email inbox and display a summary of recent messages. Use when the user wants to see their emails, check mail, or view their inbox."
+---
+
+# Check Inbox
+
+Fetch and display a summary of recent emails from the user's InboxAPI inbox.
+
+## Steps
+
+1. Run: `npx -y @inboxapi/cli whoami` to identify the current account and email address
+2. Run: `npx -y @inboxapi/cli get-email-count` to show the total number of emails
+3. Run: `npx -y @inboxapi/cli get-emails --limit <N>` where `<N>` is `$ARGUMENTS` if provided, otherwise `20`
+4. Present results in a formatted table with columns:
+   - **From** — sender name or address
+   - **Subject** — email subject line (truncated to 60 chars)
+   - **Date** — received date in relative format (e.g., "2 hours ago", "yesterday")
+5. After the table, show a summary line: "Showing X of Y emails for <email>"
+
+## Output Format
+
+Use this markdown table format:
+
+```
+| # | From | Subject | Date |
+|---|------|---------|------|
+| 1 | Alice <alice@example.com> | Re: Project update... | 2h ago |
+```
+
+If the inbox is empty, display: "Your inbox is empty. Your email address is <email>."
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+- Do NOT read full email bodies — only show the summary list
+- If the user asks to read a specific email after seeing the list, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID

package/skills/codex/compose/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: compose
+description: "Compose and send an email with guided prompts, addressbook lookup, and send confirmation. Use when the user wants to write and send an email."
+---
+
+# Compose Email
+
+Guide the user through composing and sending an email safely.
+
+## Steps
+
+1. **Identify sender**: Run: `npx -y @inboxapi/cli whoami` to get the current account email address
+
+2. **Resolve recipient**:
+   - If `$ARGUMENTS` is provided, use it as the recipient hint
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
+   - If multiple matches found, ask the user to pick one
+   - If no match, ask the user to confirm or provide the full email address
+
+3. **Collect email details**: Ask the user for:
+   - **To**: Recipient email (pre-filled if resolved above)
+   - **Subject**: Email subject line
+   - **Body**: Email content (plain text)
+
+4. **Preview**: Show the complete email before sending:
+   ```
+   From: <your-email@inboxapi.ai>
+   To: <recipient@example.com>
+   Subject: <subject>
+   ---
+   <body>
+   ```
+
+5. **Safety checks**:
+   - Warn if the recipient address matches the sender's own @inboxapi.ai address
+   - Warn if the body is empty
+   - Warn if the subject is empty
+
+6. **Confirm**: Ask the user to confirm: "Send this email? (yes/no)"
+
+7. **Send**: Run: `npx -y @inboxapi/cli send-email --to "<recipient>" --subject "<subject>" --body "<body>"`
+
+8. **Confirm delivery**: Report the result to the user
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
+## Rules
+
+- ALWAYS show a preview before sending
+- ALWAYS ask for explicit confirmation before calling send-email
+- NEVER send an email without the user confirming
+- If the user cancels, acknowledge and do not send

package/skills/codex/email-digest/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: email-digest
+description: "Generate a digest summary of recent email activity grouped by thread. Use when the user wants an overview of their email activity."
+---
+
+# Email Digest
+
+Generate a structured digest of recent email activity.
+
+## Steps
+
+1. **Determine timeframe**: Use `$ARGUMENTS` if provided (e.g., "today", "this week", "last 3 days"), otherwise default to "last 24 hours"
+
+2. **Get account info**: Run: `npx -y @inboxapi/cli whoami` for the account email
+
+3. **Get total count**: Run: `npx -y @inboxapi/cli get-email-count` for inbox statistics
+
+4. **Fetch recent emails**: Run: `npx -y @inboxapi/cli get-emails --limit 50`
+
+5. **Group by thread**: For threads with multiple emails, run `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` to understand the conversation
+
+6. **Generate digest** with these sections:
+
+   ```markdown
+   # Email Digest — <timeframe>
+   Account: <email>
+
+   ## Summary
+   - Total emails in inbox: X
+   - Emails in this period: Y
+   - Unique senders: Z
+   - Threads with activity: N
+
+   ## Active Threads
+   ### 1. <Subject>
+   - Participants: alice@..., bob@...
+   - Messages in period: 3
+   - Latest: "Brief preview of most recent message..."
+   - Status: Awaiting your reply / You replied / FYI only
+
+   ## New Emails (not in threads)
+   | From | Subject | Date |
+   |------|---------|------|
+   | ... | ... | ... |
+
+   ## Needs Attention
+   - Emails you haven't replied to where you were directly addressed
+   ```
+
+7. **Offer actions**: "Would you like to reply to any of these, or read a specific email?"
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+- Focus on actionable insights, not raw data
+- Highlight emails that likely need a response
+- Keep the digest concise — summarize, don't reproduce full emails

package/skills/codex/email-forward/SKILL.md

@@ -0,0 +1,54 @@
+---
+name: email-forward
+description: "Forward an email to someone with an optional message. Use when the user wants to forward a specific email to another person."
+---
+
+# Email Forward
+
+Help the user forward an email to another recipient.
+
+## Steps
+
+1. **Find the email to forward**:
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument
+   - If multiple results, show them and ask the user to pick one
+
+2. **Show email content**: Display the email being forwarded:
+   ```
+   --- Email to forward ---
+   From: <original sender>
+   Subject: <subject>
+   Date: <date>
+   ---
+   <body preview, first 500 chars>
+   ```
+
+3. **Resolve recipient**:
+   - Ask "Who do you want to forward this to?"
+   - Run: `npx -y @inboxapi/cli get-addressbook` to check for matching contacts
+   - Confirm the recipient email address
+
+4. **Optional message**: Ask "Add a message? (or press enter to skip)"
+
+5. **Preview**:
+   ```
+   Forwarding to: <recipient>
+   Subject: Fwd: <original subject>
+   Your message: <optional message or "(none)">
+   Original email from: <sender>, <date>
+   ```
+
+6. **Confirm**: Ask "Forward this email? (yes/no)"
+
+7. **Send**: Run: `npx -y @inboxapi/cli forward-email --message-id "<id>" --to "<recipient>"` (add `--note "<message>"` if provided)
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
+## Rules
+
+- ALWAYS show what's being forwarded before sending
+- ALWAYS confirm before forwarding
+- NEVER forward without explicit user confirmation

package/skills/codex/email-reply/SKILL.md

@@ -0,0 +1,55 @@
+---
+name: email-reply
+description: "Reply to an email with full thread context. Use when the user wants to reply to a specific email or continue an email conversation."
+---
+
+# Email Reply
+
+Help the user reply to an email with full thread context.
+
+## Steps
+
+1. **Find the email**:
+   - Try `npx -y @inboxapi/cli get-email "$ARGUMENTS"` first — if it succeeds, use that email
+   - If it fails (e.g., not a valid message ID), fall back to `npx -y @inboxapi/cli search-emails --subject "<query>"` with the argument as subject/keyword
+   - If multiple results, present them and ask the user to pick one
+
+2. **Load thread context**: Run: `npx -y @inboxapi/cli get-thread --message-id "<message-id>"` with the email's message ID to show the full conversation
+
+3. **Display thread**: Show the conversation history in chronological order:
+   ```
+   --- Thread: <subject> ---
+
+   [1] From: alice@example.com (Jan 15, 2:30 PM)
+   > Original message text...
+
+   [2] From: you@inboxapi.ai (Jan 15, 3:00 PM)
+   > Your previous reply...
+
+   [3] From: alice@example.com (Jan 15, 4:15 PM)
+   > Latest message you're replying to...
+   ```
+
+4. **Compose reply**: Ask the user what they want to say in their reply
+
+5. **Preview**: Show the reply before sending:
+   ```
+   Replying to: alice@example.com
+   Subject: Re: <subject>
+   ---
+   <reply body>
+   ```
+
+6. **Confirm**: Ask "Send this reply? (yes/no)"
+
+7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
+## Rules
+
+- ALWAYS show the thread context before composing
+- ALWAYS preview and confirm before sending
+- NEVER send without explicit user confirmation

package/skills/codex/email-search/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: email-search
+description: "Search your InboxAPI emails using natural language. Use when the user wants to find specific emails by sender, subject, date, or content."
+---
+
+# Email Search
+
+Search emails using natural language and present results clearly.
+
+## Steps
+
+1. Take the user's query from `$ARGUMENTS`
+   - If no arguments provided, ask: "What are you looking for?"
+
+2. Translate the natural language query into CLI flags for `search-emails`:
+   - Extract sender hints (e.g., "from John" -> `--sender "John"`)
+   - Extract subject hints (e.g., "about invoices" -> `--subject "invoices"`)
+   - Extract date hints (e.g., "last week", "yesterday" -> `--since "..."`, `--until "..."`)
+   - Combine with `--limit` as needed
+
+3. Run: `npx -y @inboxapi/cli search-emails` with the appropriate flags (`--sender "..."`, `--subject "..."`, `--since "..."`, `--until "..."`)
+
+4. Present results in a formatted table:
+   ```
+   | # | From | Subject | Date |
+   |---|------|---------|------|
+   ```
+
+5. After showing results, offer: "Would you like to read any of these emails? Provide the number."
+
+6. If the user picks one, run `npx -y @inboxapi/cli get-email "<message-id>"` with the email ID
+
+7. If no results, suggest alternative searches or broader terms
+
+## Notes
+
+- All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
+
+## Examples
+
+- `/email-search invoices from accounting` -> search for "invoices" filtered by sender containing "accounting"
+- `/email-search meeting tomorrow` -> search for "meeting" in recent emails
+- `/email-search` -> prompt user for search query