@inboxapi/cli 0.3.2 → 0.3.4

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (5) hide show
  1. package/package.json +6 -6
  2. package/skills/claude/email-reply/SKILL.md +14 -0
  3. package/skills/codex/email-reply/SKILL.md +14 -0
  4. package/skills/gemini/email-reply/SKILL.md +14 -0
  5. package/skills/opencode/email-reply.md +14 -0
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@inboxapi/cli",
3
- "version": "0.3.2",
3
+ "version": "0.3.4",
4
4
  "description": "📧 Email for your AI 🤖",
5
5
  "main": "index.js",
6
6
  "bin": {
@@ -28,10 +28,10 @@
28
28
  "test": "cargo test"
29
29
  },
30
30
  "optionalDependencies": {
31
- "@inboxapi/cli-darwin-arm64": "0.3.2",
32
- "@inboxapi/cli-darwin-x64": "0.3.2",
33
- "@inboxapi/cli-linux-arm64": "0.3.2",
34
- "@inboxapi/cli-linux-x64": "0.3.2",
35
- "@inboxapi/cli-win32-x64": "0.3.2"
31
+ "@inboxapi/cli-darwin-arm64": "0.3.4",
32
+ "@inboxapi/cli-darwin-x64": "0.3.4",
33
+ "@inboxapi/cli-linux-arm64": "0.3.4",
34
+ "@inboxapi/cli-linux-x64": "0.3.4",
35
+ "@inboxapi/cli-win32-x64": "0.3.4"
36
36
  }
37
37
  }
package/skills/claude/email-reply/SKILL.md CHANGED
@@ -47,6 +47,19 @@ Help the user reply to an email with full thread context.
47
47
 
48
48
  7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
49
49
 
50
+ **Preserving CC recipients in threads**: If the thread has CC'd recipients, include them with `--cc`:
51
+ ```
52
+ npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>" --cc "cc1@example.com,cc2@example.com"
53
+ ```
54
+
55
+ **Additional options**:
56
+ - `--cc "addr1,addr2"` — CC recipients (comma-separated)
57
+ - `--bcc "addr1,addr2"` — BCC recipients (comma-separated, silent copy)
58
+ - `--reply-all` — reply to all recipients in the thread
59
+ - `--html-body "<html>"` — send HTML-formatted reply
60
+ - `--from-name "Name"` — override sender display name
61
+ - `--priority <high|normal|low>` — set email priority
62
+
50
63
  ## Notes
51
64
 
52
65
  - All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
@@ -56,3 +69,4 @@ Help the user reply to an email with full thread context.
56
69
  - ALWAYS show the thread context before composing
57
70
  - ALWAYS preview and confirm before sending
58
71
  - NEVER send without explicit user confirmation
72
+ - When replying to threads with CC'd recipients, ALWAYS preserve them using `--cc` to avoid breaking the chain
package/skills/codex/email-reply/SKILL.md CHANGED
@@ -44,6 +44,19 @@ Help the user reply to an email with full thread context.
44
44
 
45
45
  7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
46
46
 
47
+ **Preserving CC recipients in threads**: If the thread has CC'd recipients, include them with `--cc`:
48
+ ```
49
+ npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>" --cc "cc1@example.com,cc2@example.com"
50
+ ```
51
+
52
+ **Additional options**:
53
+ - `--cc "addr1,addr2"` — CC recipients (comma-separated)
54
+ - `--bcc "addr1,addr2"` — BCC recipients (comma-separated, silent copy)
55
+ - `--reply-all` — reply to all recipients in the thread
56
+ - `--html-body "<html>"` — send HTML-formatted reply
57
+ - `--from-name "Name"` — override sender display name
58
+ - `--priority <high|normal|low>` — set email priority
59
+
47
60
  ## Notes
48
61
 
49
62
  - All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
@@ -53,3 +66,4 @@ Help the user reply to an email with full thread context.
53
66
  - ALWAYS show the thread context before composing
54
67
  - ALWAYS preview and confirm before sending
55
68
  - NEVER send without explicit user confirmation
69
+ - When replying to threads with CC'd recipients, ALWAYS preserve them using `--cc` to avoid breaking the chain
package/skills/gemini/email-reply/SKILL.md CHANGED
@@ -44,6 +44,19 @@ Help the user reply to an email with full thread context.
44
44
 
45
45
  7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
46
46
 
47
+ **Preserving CC recipients in threads**: If the thread has CC'd recipients, include them with `--cc`:
48
+ ```
49
+ npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>" --cc "cc1@example.com,cc2@example.com"
50
+ ```
51
+
52
+ **Additional options**:
53
+ - `--cc "addr1,addr2"` — CC recipients (comma-separated)
54
+ - `--bcc "addr1,addr2"` — BCC recipients (comma-separated, silent copy)
55
+ - `--reply-all` — reply to all recipients in the thread
56
+ - `--html-body "<html>"` — send HTML-formatted reply
57
+ - `--from-name "Name"` — override sender display name
58
+ - `--priority <high|normal|low>` — set email priority
59
+
47
60
  ## Notes
48
61
 
49
62
  - All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
@@ -53,3 +66,4 @@ Help the user reply to an email with full thread context.
53
66
  - ALWAYS show the thread context before composing
54
67
  - ALWAYS preview and confirm before sending
55
68
  - NEVER send without explicit user confirmation
69
+ - When replying to threads with CC'd recipients, ALWAYS preserve them using `--cc` to avoid breaking the chain
package/skills/opencode/email-reply.md CHANGED
@@ -43,6 +43,19 @@ Help the user reply to an email with full thread context.
43
43
 
44
44
  7. **Send**: Run: `npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>"`
45
45
 
46
+ **Preserving CC recipients in threads**: If the thread has CC'd recipients, include them with `--cc`:
47
+ ```
48
+ npx -y @inboxapi/cli send-reply --message-id "<id>" --body "<reply>" --cc "cc1@example.com,cc2@example.com"
49
+ ```
50
+
51
+ **Additional options**:
52
+ - `--cc "addr1,addr2"` — CC recipients (comma-separated)
53
+ - `--bcc "addr1,addr2"` — BCC recipients (comma-separated, silent copy)
54
+ - `--reply-all` — reply to all recipients in the thread
55
+ - `--html-body "<html>"` — send HTML-formatted reply
56
+ - `--from-name "Name"` — override sender display name
57
+ - `--priority <high|normal|low>` — set email priority
58
+
46
59
  ## Notes
47
60
 
48
61
  - All CLI commands output JSON by default — parse the JSON response to extract the relevant fields
@@ -52,3 +65,4 @@ Help the user reply to an email with full thread context.
52
65
  - ALWAYS show the thread context before composing
53
66
  - ALWAYS preview and confirm before sending
54
67
  - NEVER send without explicit user confirmation
68
+ - When replying to threads with CC'd recipients, ALWAYS preserve them using `--cc` to avoid breaking the chain