@genspark/cli 1.7.1 → 1.8.1
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.
- package/dist/config.d.ts +10 -0
- package/dist/config.d.ts.map +1 -1
- package/dist/config.js +18 -0
- package/dist/config.js.map +1 -1
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +46 -12
- package/dist/index.js.map +1 -1
- package/dist/pendingApproval.d.ts +98 -0
- package/dist/pendingApproval.d.ts.map +1 -0
- package/dist/pendingApproval.js +252 -0
- package/dist/pendingApproval.js.map +1 -0
- package/dist/types.d.ts +2 -0
- package/dist/types.d.ts.map +1 -1
- package/docs/skills.md +3 -3
- package/package.json +1 -1
- package/skills/gsk-aidrive/SKILL.md +9 -5
- package/skills/gsk-genteam/SKILL.md +27 -16
- package/skills/gsk-github/SKILL.md +1 -1
- package/skills/gsk-gmail/SKILL.md +14 -9
- package/skills/gsk-google-calendar/SKILL.md +1 -1
- package/skills/gsk-google-chat/SKILL.md +2 -2
- package/skills/gsk-google-docs/SKILL.md +1 -1
- package/skills/gsk-google-drive/SKILL.md +2 -2
- package/skills/gsk-google-sheets/SKILL.md +1 -1
- package/skills/gsk-google-slides/SKILL.md +1 -1
- package/skills/gsk-microsoft-teams/SKILL.md +2 -2
- package/skills/gsk-notion/SKILL.md +1 -1
- package/skills/gsk-onedrive/SKILL.md +2 -2
- package/skills/gsk-outlook-calendar/SKILL.md +1 -1
- package/skills/gsk-outlook-email/SKILL.md +21 -12
- package/skills/gsk-sharepoint/SKILL.md +1 -1
- package/skills/gsk-slack/SKILL.md +8 -10
- package/skills/gsk-task-status/SKILL.md +1 -0
- package/skills/gsk-youtube/SKILL.md +3 -3
|
@@ -58,7 +58,7 @@ gsk github [options]
|
|
|
58
58
|
|
|
59
59
|
## Write Confirmation (double-call)
|
|
60
60
|
|
|
61
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
61
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
62
62
|
|
|
63
63
|
## See Also
|
|
64
64
|
|
|
@@ -2,8 +2,9 @@
|
|
|
2
2
|
name: gsk-gmail
|
|
3
3
|
version: 1.0.0
|
|
4
4
|
description: 'Gmail operations. Actions: search, read, send, draft, reply, forward,
|
|
5
|
-
delete, archive, move, mark_as_read, add_label, remove_label, create_label,
|
|
6
|
-
list_send_as, get_vacation, update_vacation,
|
|
5
|
+
delete, archive, move, mark_as_read, add_label, remove_label, create_label, create_filter,
|
|
6
|
+
list_filters, delete_filter, get_attachment, list_send_as, get_vacation, update_vacation,
|
|
7
|
+
get_signature, update_signature.'
|
|
7
8
|
metadata:
|
|
8
9
|
category: general
|
|
9
10
|
requires:
|
|
@@ -18,7 +19,7 @@ metadata:
|
|
|
18
19
|
|
|
19
20
|
> **Note:** a unified `gsk connector` flow is rolling out (see `../gsk-connector/SKILL.md`: `gsk connector tools <id>` / `gsk connector call <id> -t <tool>`) and may not be enabled for every account yet. THIS command remains fully supported — use it directly, and it stays the fallback whenever `gsk connector` is unavailable.
|
|
20
21
|
|
|
21
|
-
Gmail operations. Actions: search, read, send, draft, reply, forward, delete, archive, move, mark_as_read, add_label, remove_label, create_label, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature.
|
|
22
|
+
Gmail operations. Actions: search, read, send, draft, reply, forward, delete, archive, move, mark_as_read, add_label, remove_label, create_label, create_filter, list_filters, delete_filter, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature.
|
|
22
23
|
|
|
23
24
|
## Usage
|
|
24
25
|
|
|
@@ -30,14 +31,14 @@ gsk gmail [options]
|
|
|
30
31
|
|
|
31
32
|
| Flag | Required | Description |
|
|
32
33
|
|------|----------|-------------|
|
|
33
|
-
| `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'send': Compose and send an email
|
|
34
|
+
| `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'send': Compose and send an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'forward': Forward an email to new recipients. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'archive': Archive an email; 'move': Move an email to a different label/folder. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'mark_as_read': Mark an email as read or unread; 'add_label': Add a label to an email; 'remove_label': Remove a label from an email; 'create_label': Create a new Gmail label; 'create_filter': Create a persistent Gmail filter. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_filters': List persistent Gmail filters; 'delete_filter': Delete a persistent Gmail filter. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'get_attachment': Download an email attachment; 'list_send_as': List available send-as aliases; 'get_vacation': Get the vacation (out-of-office) auto-reply settings; 'update_vacation': Enable, disable, or update the vacation (out-of-office) auto-reply. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'get_signature': Get the signature of a send-as address; 'update_signature': Set or clear the signature of a send-as address. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: search, read, send, draft, reply, forward, delete, archive, move, mark_as_read, add_label, remove_label, create_label, create_filter, list_filters, delete_filter, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature) |
|
|
34
35
|
| `--query` | No | [search] Query to filter emails using Gmail search syntax. Examples:\n- Simple: 'meeting'\n- From Sender: 'from:boss@example.com'\n- Subject: 'subject:report'\n- In Folder: 'in:spam', 'in:inbox', 'in:trash', 'in:sent'\n- Label: 'label:important'\n- Unread: 'is:unread'\n- Unread in Spam: 'in:spam is:unread'\n- Has Attachment: 'has:attachment'\n- Date Range: 'after:2024/01/01 before:2024/01/31'\n- Newer Than: 'newer_than:7d' (7 days)\n- Older Than: 'older_than:1m' (1 month)\nNote: Some queries like 'is:recent' are invalid. (string) |
|
|
35
36
|
| `--after_date` | No | [search] Filter emails received after this date (inclusive). Format: YYYY/MM/DD (e.g., '2024/01/01'). This is equivalent to adding 'after:YYYY/MM/DD' to the query. (string) |
|
|
36
37
|
| `--before_date` | No | [search] Filter emails received before this date (exclusive). Format: YYYY/MM/DD (e.g., '2024/01/31'). This is equivalent to adding 'before:YYYY/MM/DD' to the query. (string) |
|
|
37
38
|
| `--next_page_token` | No | [search] Next page token to retrieve more emails (optional). (string) |
|
|
38
39
|
| `--auto_paginate` | No | [search] If true, automatically fetches multiple pages until reaching max_total_results (default: 500). Returns ALL emails matching the query. (boolean) |
|
|
39
40
|
| `--max_total_results` | No | [search] Maximum total results to fetch when auto_paginate is true. Default: 500, Maximum: 500. (integer) |
|
|
40
|
-
| `--from_account` | No | [search] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [read] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [send] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [draft] Sender email account to use. \| [reply] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [forward] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [delete] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [archive] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [move] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [mark_as_read] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [add_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [remove_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [create_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [get_attachment] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [list_send_as] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [get_vacation] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [update_vacation] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [get_signature] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [update_signature] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. (string) |
|
|
41
|
+
| `--from_account` | No | [search] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [read] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [send] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [draft] Sender email account to use. \| [reply] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [forward] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [delete] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [archive] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [move] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [mark_as_read] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [add_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [remove_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [create_label] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [create_filter] Optional email address of the Gmail account to use when multiple accounts are connected. Defaults to the primary connected account. \| [list_filters] Optional email address of the Gmail account to use when multiple accounts are connected. Defaults to the primary connected account. \| [delete_filter] Optional email address of the Gmail account to use when multiple accounts are connected. Defaults to the primary connected account. \| [get_attachment] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [list_send_as] Optional: Email address of the Gmail account to use. Use this when the user has multiple Gmail accounts connected. If not specified, uses the default Gmail account. \| [get_vacation] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [update_vacation] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [get_signature] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. \| [update_signature] Optional: email address of the Gmail account to use when the user has multiple Gmail accounts connected. Defaults to the primary connected account. (string) |
|
|
41
42
|
| `--id` | No | [read] The ID of a single Gmail message to retrieve. Mutually exclusive with 'thread_id'. (string) |
|
|
42
43
|
| `--thread_id` | No | [read] The Gmail thread (conversation) ID to retrieve. Returns every message in the thread. Mutually exclusive with 'id'. Each Gmail message exposes its parent thread via the 'threadId' field — the same value returned by 'gmail_search'. (string) |
|
|
43
44
|
| `--max_messages` | No | [read] Optional cap on how many messages to return when reading by 'thread_id'. Returns the most-recent N messages (chronological order preserved within the slice). Use this for long threads to keep the LLM context bounded — e.g. max_messages=5 for the tail of a long newsletter chain. Ignored when reading by single 'id'. (integer) |
|
|
@@ -45,16 +46,17 @@ gsk gmail [options]
|
|
|
45
46
|
| `--question` | No | [read] Question to answer guiding how to process the email content (string) |
|
|
46
47
|
| `--download_attachments` | No | [read] Whether need to download attachments from the email to analysis (boolean) |
|
|
47
48
|
| `--aidrive_path` | No | [read] Path in AIDrive where attachments should be saved. Default is /gmail_attachments/ \| [get_attachment] The path in AIDrive to save the attachment. Default: /gmail_attachments/ (string) |
|
|
48
|
-
| `--to` | No | [send]
|
|
49
|
-
| `--subject` | No | [send] The email subject line \| [draft] Email subject line. (string) |
|
|
49
|
+
| `--to` | No | [send] Optional: primary recipient email address(es). For multiple recipients, separate with commas. At least one address across to, cc, or bcc is required. \| [draft] Recipient email address(es), comma-separated. \| [forward] Optional: primary recipient email address(es). For multiple recipients, separate with commas. (string) |
|
|
50
|
+
| `--subject` | No | [send] Optional: The email subject line. Defaults to empty. \| [draft] Email subject line. (string) |
|
|
50
51
|
| `--body` | No | [send] The email body content. **IMPORTANT**: The format of this field MUST match the content_type parameter: - If content_type='text/plain': Use plain text - If content_type='text/html': Use HTML format with tags like <h1>, <p>, <ul>, <li>, etc. **Note**: Email clients DO NOT support Markdown rendering. If you have Markdown content and want formatted display, you must convert it to HTML and set content_type='text/html'. \| [draft] Email body content (plain text or HTML). \| [reply] The reply message body. **IMPORTANT**: The format of this field MUST match the content_type parameter: - If content_type='text/plain': Use plain text - If content_type='text/html': Use HTML format with tags like <h1>, <p>, <ul>, <li>, etc. **Note**: Email clients DO NOT support Markdown rendering. If you have Markdown content and want formatted display, you must convert it to HTML and set content_type='text/html'. \| [forward] Optional: Additional message to include above the forwarded content. This is your personal note to the recipients. (string) |
|
|
51
52
|
| `--cc` | No | [send] Optional: CC email address(es). For multiple recipients, separate with commas. \| [draft] CC recipient(s), comma-separated. \| [forward] Optional: CC email address(es). For multiple recipients, separate with commas. (string) |
|
|
52
|
-
| `--bcc` | No | [send] Optional: BCC email address(es). For multiple recipients, separate with commas. \| [draft] BCC recipient(s), comma-separated. (string) |
|
|
53
|
+
| `--bcc` | No | [send] Optional: BCC email address(es). For multiple recipients, separate with commas. \| [draft] BCC recipient(s), comma-separated. \| [forward] Optional: BCC email address(es). For multiple recipients, separate with commas. (string) |
|
|
53
54
|
| `--content_type` | No | [send] Content type of the email body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text (# Title, **bold**). This will display raw Markdown symbols in the email. Always convert Markdown to HTML before passing to this tool. \| [reply] Content type of the reply body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text. This will display raw Markdown symbols. Always convert Markdown to HTML first. \| [forward] Content type of the body. Default: text/html (recommended) **CRITICAL**: This parameter defines the format of the 'body' field: - 'text/plain': body should be plain text only - 'text/html': body MUST be valid HTML (e.g., '<h1>Title</h1><p>Content</p>') **Common mistake**: Setting content_type='text/html' but providing Markdown text. This will display raw Markdown symbols. Always convert Markdown to HTML first. (string, one of: text/plain, text/html) |
|
|
54
55
|
| `--from_address` | No | [send] Send-as email address to use as the sender. Use this to send as a group/alias address (e.g., 'feedback@company.com'). Must be configured in Gmail's 'Send mail as' settings. \| [draft] Optional 'From:' identity to send AS — Gmail verified alias, Outlook proxyAddress / mail-enabled group, or a granted SendAs / on-behalf address. Must be an address the from-account is authorized to send as (see 'send_as' on /api/ai-inbox/mailbox/accounts). For Gmail this becomes the draft's MIME 'From:' header; for Outlook the saved draft stays as the from-account and the alias is applied by the eventual send call. \| [reply] Send-as email address to use as the sender. Use this to reply as a group/alias address (e.g., 'feedback@company.com'). Must be configured in Gmail's 'Send mail as' settings. \| [forward] Send-as email address to use as the sender. Use this to forward as a group/alias address. Must be configured in Gmail's 'Send mail as' settings. (string) |
|
|
55
56
|
| `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [reply] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [forward] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [delete] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [move] If true, skip user confirmation and move immediately. Default is false (require confirmation before moving). (boolean, default: `False`) |
|
|
56
57
|
| `--auto_skip_confirmation` | No | [send] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [reply] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [forward] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [delete] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [move] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. (boolean, default: `False`) |
|
|
57
58
|
| `--client_send_id` | No | [send] Optional stable idempotency key. When provided, stored in X-Genspark-Client-Send-Id and mirrored into a provider-safe Message-ID digest. Scheduled agent retries use it for internal deduplication. Usually auto-resolved from the active scheduled-action context — the LLM only needs to pass this when it wants to derive its own key (e.g. plan fan-out). (string) |
|
|
59
|
+
| `--force_resend` | No | [send] Set true only when the user explicitly wants another copy of an otherwise identical email. This bypasses the 10-minute interactive-send deduplication window. (boolean, default: `False`) |
|
|
58
60
|
| `--attachments` | No | [send] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [draft] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [reply] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [forward] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). (array) |
|
|
59
61
|
| `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
|
|
60
62
|
| `--prompt` | No | [draft] Optional instruction describing the email to write, in the sender's own voice using their Email Brain (persona plus their handling and writing rules) — e.g. 'ask Ana to move the review to Friday, apologize for the short notice'. Use INSTEAD of 'body' to have the body written for you, or TOGETHER WITH 'body' to revise that text per the instruction (everything the instruction does not ask to change is preserved). Recipients and attachments are never inferred from the instruction — pass them explicitly. Omit to commit 'body' exactly as given. (string) |
|
|
@@ -71,6 +73,9 @@ gsk gmail [options]
|
|
|
71
73
|
| `--message_list_visibility` | No | [create_label] The visibility of messages with this label. Default: show (string, one of: show, hide) |
|
|
72
74
|
| `--background_color` | No | [create_label] The background color of the label in hex format (e.g., '#16a765'). Optional. (string) |
|
|
73
75
|
| `--text_color` | No | [create_label] The text color of the label in hex format (e.g., '#ffffff'). Optional. (string) |
|
|
76
|
+
| `--criteria` | No | [create_filter] Gmail filter criteria, such as from, to, subject, query, negatedQuery, hasAttachment, excludeChats, size, and sizeComparison. (object) |
|
|
77
|
+
| `--filter_action` | No | [create_filter] Gmail filter action containing addLabelIds, removeLabelIds, and/or forward. (object) |
|
|
78
|
+
| `--filter_id` | No | [delete_filter] ID of the Gmail filter to delete. (string) |
|
|
74
79
|
| `--filename` | No | [get_attachment] The filename of the attachment to retrieve. Use '*' to get all attachments. (string) |
|
|
75
80
|
| `--save_to_aidrive` | No | [get_attachment] Whether to save the attachment to AIDrive. Default: true (boolean) |
|
|
76
81
|
| `--enable_auto_reply` | No | [update_vacation] Turn the vacation auto-reply on (true) or off (false). (boolean) |
|
|
@@ -86,7 +91,7 @@ gsk gmail [options]
|
|
|
86
91
|
|
|
87
92
|
## Write Confirmation (double-call)
|
|
88
93
|
|
|
89
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
94
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
90
95
|
|
|
91
96
|
## See Also
|
|
92
97
|
|
|
@@ -63,7 +63,7 @@ gsk google_calendar [options]
|
|
|
63
63
|
|
|
64
64
|
## Write Confirmation (double-call)
|
|
65
65
|
|
|
66
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
66
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
67
67
|
|
|
68
68
|
## See Also
|
|
69
69
|
|
|
@@ -30,7 +30,7 @@ gsk google_chat [options]
|
|
|
30
30
|
|
|
31
31
|
| Flag | Required | Description |
|
|
32
32
|
|------|----------|-------------|
|
|
33
|
-
| `<action>` (positional) | Yes | Action to perform. 'list_spaces': List spaces (rooms, group chats, and DMs); 'read': Read recent messages from a space; 'send': Send a message to a space (recipients see a Genspark app label next to the sender's name — Google adds it, it cannot be hidden)
|
|
33
|
+
| `<action>` (positional) | Yes | Action to perform. 'list_spaces': List spaces (rooms, group chats, and DMs); 'read': Read recent messages from a space; 'send': Send a message to a space (recipients see a Genspark app label next to the sender's name — Google adds it, it cannot be hidden). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to a space as a message attachment. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'update': Edit the text of one of your own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete one of your own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'react': Add or remove an emoji reaction on a message (unicode emoji; remove affects your own reaction only). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_members': List all members of a space (full roster) (string, one of: list_spaces, read, send, upload, update, delete, react, list_members) |
|
|
34
34
|
| `--search_query` | No | [list_spaces] Optional case-insensitive filter on the space display name. (string) |
|
|
35
35
|
| `--limit` | No | [list_spaces] Maximum number of spaces to return (1-200). Default: 50 \| [read] Maximum number of messages to return (1-100). Default: 25 (integer) |
|
|
36
36
|
| `--space` | No | [read] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [send] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [upload] Space resource name, e.g. 'spaces/AAAAxxxx'. \| [list_members] Space resource name, e.g. 'spaces/AAAAxxxx'. (string) |
|
|
@@ -48,7 +48,7 @@ gsk google_chat [options]
|
|
|
48
48
|
|
|
49
49
|
## Write Confirmation (double-call)
|
|
50
50
|
|
|
51
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
51
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
52
52
|
|
|
53
53
|
## See Also
|
|
54
54
|
|
|
@@ -43,7 +43,7 @@ gsk docs [options]
|
|
|
43
43
|
|
|
44
44
|
## Write Confirmation (double-call)
|
|
45
45
|
|
|
46
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
46
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
47
47
|
|
|
48
48
|
## See Also
|
|
49
49
|
|
|
@@ -30,7 +30,7 @@ gsk gdrive [options]
|
|
|
30
30
|
|
|
31
31
|
| Flag | Required | Description |
|
|
32
32
|
|------|----------|-------------|
|
|
33
|
-
| `<action>` (positional) | Yes | Action to perform. 'list': List files directly inside a Google Drive folder; 'search': Search files by name, type, or owner; 'read': Read and extract content from a file; 'upload': Upload a new file to Google Drive, or overwrite an existing one in place by passing its file_id (the ID, link, and shares are preserved); 'share': Grant access to a file (specific emails or anyone-with-link; app-created/opened files only under drive.file) (string, one of: list, search, read, upload, share) |
|
|
33
|
+
| `<action>` (positional) | Yes | Action to perform. 'list': List files directly inside a Google Drive folder; 'search': Search files by name, type, or owner; 'read': Read and extract content from a file; 'upload': Upload a new file to Google Drive, or overwrite an existing one in place by passing its file_id (the ID, link, and shares are preserved); 'share': Grant access to a file (specific emails or anyone-with-link; app-created/opened files only under drive.file). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: list, search, read, upload, share) |
|
|
34
34
|
| `--folder_id` | No | [list] Google Drive folder ID or folder URL. \| [search] Search within a specific folder for 'search' action. Accepts a folder ID or Google Drive folder URL. \| [upload] Google Drive folder ID to upload to. Optional, uploads to root if not specified. Ignored when 'file_id' is set. (string) |
|
|
35
35
|
| `--folder_url` | No | [list] Google Drive folder URL. \| [search] Google Drive folder URL to list/search within. (string) |
|
|
36
36
|
| `--mime_type` | No | [list] Optional MIME type filter. \| [search] Filter by MIME type for 'search' (e.g., 'application/pdf'). \| [upload] The MIME type of the file (optional, will be auto-detected from file_name extension). Examples: 'text/plain', 'text/csv', 'application/json', 'image/png'. (string) |
|
|
@@ -59,7 +59,7 @@ Parameters that accept URLs (`--folder_url`, `--file_url`) also accept local fil
|
|
|
59
59
|
|
|
60
60
|
## Write Confirmation (double-call)
|
|
61
61
|
|
|
62
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
62
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
63
63
|
|
|
64
64
|
## See Also
|
|
65
65
|
|
|
@@ -52,7 +52,7 @@ Parameters that accept URLs (`--from_url`) also accept local file paths. The CLI
|
|
|
52
52
|
|
|
53
53
|
## Write Confirmation (double-call)
|
|
54
54
|
|
|
55
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
55
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
56
56
|
|
|
57
57
|
## See Also
|
|
58
58
|
|
|
@@ -44,7 +44,7 @@ gsk slides [options]
|
|
|
44
44
|
|
|
45
45
|
## Write Confirmation (double-call)
|
|
46
46
|
|
|
47
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
47
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
48
48
|
|
|
49
49
|
## See Also
|
|
50
50
|
|
|
@@ -33,7 +33,7 @@ gsk teams [options]
|
|
|
33
33
|
|
|
34
34
|
| Flag | Required | Description |
|
|
35
35
|
|------|----------|-------------|
|
|
36
|
-
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message in Teams (reply_to_message_id replies in a channel thread or quotes a chat message)
|
|
36
|
+
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message in Teams (reply_to_message_id replies in a channel thread or quotes a chat message). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_channels': List hosted and shared channels for an associated team; 'list_chats': List recent chats; 'read_chat': Read a chat's recent messages by chat_id; 'list_channel_messages': List root messages in a channel; one traversal is not a deletion snapshot; 'list_channel_replies': List replies to a channel message; one traversal is not a deletion snapshot; 'download_attachment': Download one attachment or inline hosted image from a message; returns a file URL; 'mark_chat_read': Mark a chat as read for the connected user (clears its unread badge; own read state only); 'api': Raw Graph call with the connected account, for resources the typed actions do not cover; GET immediate, writes held for confirmation. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_teams': List direct teams and shared-channel host teams; 'search': Search messages; 'search_users': Search for users; 'create_chat': Create a new chat; 'react': Emoji-react to a chat or channel message (or remove your reaction). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'upload': Share a file into a chat (uploads to the sender's OneDrive Teams folder, posts a file card). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_members': List ALL members of a team with roles and emails (full roster, internally paginated); 'create_team': Create a new team (you become owner) and optionally add members by email; 'delete_message': Soft-delete one of your own messages (chat, channel, or threaded reply). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: send, list_channels, list_chats, read_chat, list_channel_messages, list_channel_replies, download_attachment, mark_chat_read, api, list_teams, search, search_users, create_chat, react, upload, list_members, create_team, delete_message) |
|
|
37
37
|
| `--content` | No | [send] The message content to send. Accepts either Markdown or HTML. Markdown (e.g. '## Heading', '**bold**', '- item', tables) is automatically rendered to formatted HTML. You may also pass raw HTML directly: <a href='URL'>text</a> for links, <b>text</b> for bold, <i>text</i> for italic, <br> for line breaks, and other standard HTML tags. INLINE IMAGES are supported: embed <img src="data:image/png;base64,..."> (any image/* data URI) and the bytes are automatically relocated into Microsoft Graph hostedContents so the image renders in the message — no manual Graph calls needed. 'message' is accepted as an alias for this parameter. How this text is rendered is governed by content_format; declare it explicitly when the text could be mistaken for markup (code, '#'-prefixed lines, '**'). \| [upload] Text content to upload as a file (UTF-8). Provide exactly one of 'content' or 'file_path'. (string) |
|
|
38
38
|
| `--content_format` | No | [send] Declares how 'content' should be rendered — the server cannot reliably guess (a Python comment and a Markdown heading are byte-identical). 'plain': send the text literally, nothing is interpreted as markup — use this for code snippets or any text containing '#', '**', '\|' etc. that must appear verbatim. 'markdown': always render Markdown to formatted HTML. 'html': send the content as authored HTML unchanged. 'auto' (default): legacy guessing — HTML-looking content passes through, anything else renders as Markdown. (string, one of: auto, plain, markdown, html, default: `auto`) |
|
|
39
39
|
| `--chat_id` | No | [send] Optional chat ID to send the message to. If not specified or set to 'self', sends to yourself as a DM. Use chat IDs from microsoft_teams_search_messages results. \| [read_chat] The Teams chat ID (e.g. '19:...@thread.v2'). Required. \| [download_attachment] Chat ID ('19:…@thread.v2') for a chat message. Mutually exclusive with team_id/channel_id. \| [mark_chat_read] Chat ID ('19:…@thread.v2') to mark as read, from microsoft_teams_list_chats. \| [react] ID of the chat containing the message. Provide either chat_id, or team_id + channel_id for a channel message. \| [upload] Target chat ID (e.g. '19:…@thread.v2', from list_chats/search_users). \| [list_members] Chat ID ('19:…@thread.v2') to list a group chat's or DM's members instead of a team's. \| [delete_message] ID of the chat containing the message. Provide either chat_id, or team_id + channel_id for a channel message. (string) |
|
|
@@ -80,7 +80,7 @@ gsk teams [options]
|
|
|
80
80
|
|
|
81
81
|
## Write Confirmation (double-call)
|
|
82
82
|
|
|
83
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
83
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
84
84
|
|
|
85
85
|
## See Also
|
|
86
86
|
|
|
@@ -38,7 +38,7 @@ gsk notion [options]
|
|
|
38
38
|
|
|
39
39
|
## Write Confirmation (double-call)
|
|
40
40
|
|
|
41
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
41
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
42
42
|
|
|
43
43
|
## See Also
|
|
44
44
|
|
|
@@ -28,7 +28,7 @@ gsk onedrive [options]
|
|
|
28
28
|
|
|
29
29
|
| Flag | Required | Description |
|
|
30
30
|
|------|----------|-------------|
|
|
31
|
-
| `<action>` (positional) | Yes | Action to perform. 'list': List files in a folder; 'search': Search files; 'read': Read and extract content from a file; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to OneDrive; 'share': Create a sharing link (view/edit/embed; anonymous or organization scope) for a file or folder (string, one of: list, search, read, upload, share) |
|
|
31
|
+
| `<action>` (positional) | Yes | Action to perform. 'list': List files in a folder; 'search': Search files; 'read': Read and extract content from a file; 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to OneDrive; 'share': Create a sharing link (view/edit/embed; anonymous or organization scope) for a file or folder. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: list, search, read, upload, share) |
|
|
32
32
|
| `--onedrive_url` | No | [list] A OneDrive URL to list files from. Can be a sharing link, folder link, or any OneDrive URL. (string) |
|
|
33
33
|
| `--folder_id` | No | [list] The folder item ID to list contents of. Get folder IDs from previous onedrive_list_files or onedrive_search results. \| [upload] Target folder item ID (from onedrive_list_files or onedrive_search). If omitted, ``folder_path`` is used; if both are omitted, the upload goes to the OneDrive root. (string) |
|
|
34
34
|
| `--folder_path` | No | [list] The folder path relative to OneDrive root. Example: 'Documents/Projects' to list files in that subfolder. \| [upload] Target folder path relative to the OneDrive root, e.g. 'Documents/Reports'. The folder must already exist. Ignored when ``folder_id`` is provided. (string) |
|
|
@@ -52,7 +52,7 @@ Parameters that accept URLs (`--onedrive_url`) also accept local file paths. The
|
|
|
52
52
|
|
|
53
53
|
## Write Confirmation (double-call)
|
|
54
54
|
|
|
55
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
55
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
56
56
|
|
|
57
57
|
## See Also
|
|
58
58
|
|
|
@@ -69,7 +69,7 @@ gsk outlook_calendar [options]
|
|
|
69
69
|
|
|
70
70
|
## Write Confirmation (double-call)
|
|
71
71
|
|
|
72
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
72
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
73
73
|
|
|
74
74
|
## See Also
|
|
75
75
|
|
|
@@ -1,10 +1,10 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: gsk-outlook-email
|
|
3
3
|
version: 1.0.0
|
|
4
|
-
description: 'Outlook Email operations. Actions: search, read, list_folders,
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
group_read, group_reply.'
|
|
4
|
+
description: 'Outlook Email operations. Actions: search, read, list_folders, create_folder,
|
|
5
|
+
list_emails, list_email_changes, list_rules, create_rule, delete_rule, send, draft,
|
|
6
|
+
reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category,
|
|
7
|
+
remove_category, get_attachment, group_list, group_search, group_read, group_reply.'
|
|
8
8
|
metadata:
|
|
9
9
|
category: general
|
|
10
10
|
requires:
|
|
@@ -19,7 +19,7 @@ metadata:
|
|
|
19
19
|
|
|
20
20
|
> **Note:** a unified `gsk connector` flow is rolling out (see `../gsk-connector/SKILL.md`: `gsk connector tools <id>` / `gsk connector call <id> -t <tool>`) and may not be enabled for every account yet. THIS command remains fully supported — use it directly, and it stays the fallback whenever `gsk connector` is unavailable.
|
|
21
21
|
|
|
22
|
-
Outlook Email operations. Actions: search, read, list_folders, list_emails, list_email_changes, send, draft, reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category, remove_category, get_attachment, group_list, group_search, group_read, group_reply.
|
|
22
|
+
Outlook Email operations. Actions: search, read, list_folders, create_folder, list_emails, list_email_changes, list_rules, create_rule, delete_rule, send, draft, reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category, remove_category, get_attachment, group_list, group_search, group_read, group_reply.
|
|
23
23
|
|
|
24
24
|
## Usage
|
|
25
25
|
|
|
@@ -33,7 +33,7 @@ gsk outlook [options]
|
|
|
33
33
|
|
|
34
34
|
| Flag | Required | Description |
|
|
35
35
|
|------|----------|-------------|
|
|
36
|
-
| `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'list_folders': List structured Outlook mail folders; 'list_emails': List structured emails with explicit body coverage; 'list_email_changes': List folder-scoped email upserts and tombstones with body coverage using a delta cursor; 'send': Compose and send an email
|
|
36
|
+
| `<action>` (positional) | Yes | Action to perform. 'search': Search emails by query; 'read': Read a specific email by ID; 'list_folders': List structured Outlook mail folders; 'create_folder': Create an Outlook mail folder. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_rules': List Outlook inbox rules; 'create_rule': Create an Outlook inbox rule. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete_rule': Delete an Outlook inbox rule. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'list_emails': List structured emails with explicit body coverage; 'list_email_changes': List folder-scoped email upserts and tombstones with body coverage using a delta cursor; 'send': Compose and send an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'reply_draft': Create a reply draft without sending; 'forward': Forward an email to new recipients. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete an email. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'archive': Archive an email; 'move': Move an email to a different folder. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'mark_as_read': Mark an email as read or unread; 'add_category': Add a category to an email; 'remove_category': Remove a category from an email; 'get_attachment': Download an email attachment; 'group_list': List Microsoft 365 groups; 'group_search': Search group emails; 'group_read': Read a group email; 'group_reply': Reply to a group email (string, one of: search, read, list_folders, create_folder, list_rules, create_rule, delete_rule, list_emails, list_email_changes, send, draft, reply, reply_draft, forward, delete, archive, move, mark_as_read, add_category, remove_category, get_attachment, group_list, group_search, group_read, group_reply) |
|
|
37
37
|
| `--queryString` | No | [search] The search query using KQL (Keyword Query Language). Examples:\n- Simple: 'project meeting'\n- From Sender: 'from:boss@example.com'\n- With Subject: 'subject:"Weekly Report"'\n- Unread Emails: 'isRead=false'\n- Has Attachments: 'hasAttachments=true'\n- Cc Recipient: 'cc:user@example.com'\n- Important: 'importance:high'\n- Complex: 'from:admin@co.com AND (subject:urgent OR body:critical)'\nNote: Use after_date/before_date params for date filtering (recommended), or use KQL syntax like 'received:2024-06-01..2024-06-30' in queryString. (string) |
|
|
38
38
|
| `--after_date` | No | [search] Filter emails received on or after this date (inclusive). Format: YYYY-MM-DD (e.g., '2024-01-01'). Works for both enterprise and personal accounts. (string) |
|
|
39
39
|
| `--before_date` | No | [search] Filter emails received before this date (exclusive). Format: YYYY-MM-DD (e.g., '2024-01-31'). Works for both enterprise and personal accounts. (string) |
|
|
@@ -43,7 +43,7 @@ gsk outlook [options]
|
|
|
43
43
|
| `--max_total_results` | No | [search] Maximum total results to fetch when auto_paginate is true. Default: 500, Maximum: 500. \| [group_search] Maximum total results to fetch across all groups when auto_paginate is true. Default: 500, Maximum: 500. (integer) |
|
|
44
44
|
| `--folder` | No | [search] The mail folder to search in. Options:\n- 'inbox': Inbox folder (default)\n- 'junkemail' or 'spam': Junk/Spam folder\n- 'deleteditems' or 'trash': Deleted Items folder\n- 'drafts': Drafts folder\n- 'sentitems' or 'sent': Sent Items folder\n- 'archive': Archive folder\n- 'all': Search across all folders (uses Search API)\n- Any custom folder display name (e.g. 'Receipts' or a nested 'Parent/Child' path) is also accepted and resolved to the folder automatically (string) |
|
|
45
45
|
| `--search_mode` | No | [search] Search mode to use:\n- 'auto' (default): Automatically choose best method\n- 'kql': Use Microsoft Search API with full KQL syntax (enterprise only, supports 'isread:false from:john subject:meeting')\n- 'filter': Use $filter for property filtering (supports 'isRead eq false', works with folder parameter) (string, one of: auto, kql, filter) |
|
|
46
|
-
| `--from_account` | No | [search] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [list_folders] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [list_emails] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [list_email_changes] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [send] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [draft] Sender email account to use. \| [reply] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [reply_draft] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [forward] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [delete] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [archive] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [move] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [mark_as_read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [add_category] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [remove_category] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [get_attachment] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_list] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_search] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_reply] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. (string) |
|
|
46
|
+
| `--from_account` | No | [search] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [list_folders] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [create_folder] Connected Outlook mailbox address. \| [list_rules] Connected Outlook mailbox address. \| [create_rule] Connected Outlook mailbox address. \| [delete_rule] Connected Outlook mailbox address. \| [list_emails] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [list_email_changes] Connected Outlook mailbox address; required for stable multi-account ingestion. \| [send] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [draft] Sender email account to use. \| [reply] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [reply_draft] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [forward] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [delete] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [archive] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [move] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [mark_as_read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [add_category] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [remove_category] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [get_attachment] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_list] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_search] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_read] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. \| [group_reply] Optional: Email address of the Outlook account to use. Use this when the user has multiple Outlook accounts connected. If not specified, uses the default Outlook account. (string) |
|
|
47
47
|
| `--id` | No | [read] The ID of a single Outlook message to retrieve. Mutually exclusive with 'thread_id'. (string) |
|
|
48
48
|
| `--thread_id` | No | [read] The Outlook conversationId of the thread to retrieve. Returns every message in the conversation. Mutually exclusive with 'id'. The 'outlook_email_search' tool exposes this value as 'threadId' on each result. \| [group_read] The ID of the email thread to retrieve. This is often the same as the conversationId. \| [group_reply] The ID of the email thread to reply to. Available from trigger data as 'thread_id' or 'emails[0].thread_id'. (string) |
|
|
49
49
|
| `--max_messages` | No | [read] Optional cap on how many messages to return when reading by 'thread_id'. Returns the most-recent N messages (chronological order preserved within the slice). Use this for long conversations to keep the LLM context bounded. Ignored when reading by single 'id'. (integer) |
|
|
@@ -51,15 +51,23 @@ gsk outlook [options]
|
|
|
51
51
|
| `--question` | No | [read] Question to answer guiding how to process the email content \| [group_read] Question to answer guiding how to process the email content (string) |
|
|
52
52
|
| `--download_attachments` | No | [read] Whether need to download attachments from the email to analysis (boolean) |
|
|
53
53
|
| `--aidrive_path` | No | [read] Path in AIDrive where attachments should be saved. Default is /outlook_attachments/ \| [get_attachment] The path in AIDrive to save the attachment. Default: /outlook_attachments/ (string) |
|
|
54
|
-
| `--parent_folder_id` | No | [list_folders] Folder ID whose direct children to list; omit for root folders. (string) |
|
|
54
|
+
| `--parent_folder_id` | No | [list_folders] Folder ID whose direct children to list; omit for root folders. \| [create_folder] Optional parent folder ID; omit for the mailbox root. (string) |
|
|
55
55
|
| `--cursor` | No | [list_folders] Opaque next_cursor from the previous page. \| [list_emails] Opaque next_cursor from the previous page. \| [list_email_changes] Opaque next_cursor while paging the current delta round. (string) |
|
|
56
56
|
| `--page_size` | No | [list_folders] Requested page size (1-100, default 50). \| [list_emails] Requested page size (1-100, default 50). \| [list_email_changes] Requested page size (1-100, default 50). (integer, default: `50`) |
|
|
57
|
+
| `--folder_name` | No | [create_folder] \| [move] The target folder name. Can be a well-known folder (inbox, drafts, sentitems, deleteditems, archive, junkemail, outbox) or a custom folder name. Custom folders will be created if they don't exist. (string) |
|
|
58
|
+
| `--display_name` | No | [create_rule] (string) |
|
|
59
|
+
| `--conditions` | No | [create_rule] Microsoft Graph message-rule conditions. (object) |
|
|
60
|
+
| `--actions` | No | [create_rule] Microsoft Graph message-rule actions. (object) |
|
|
61
|
+
| `--exceptions` | No | [create_rule] Optional Microsoft Graph rule exceptions. (object) |
|
|
62
|
+
| `--sequence` | No | [create_rule] (integer) |
|
|
63
|
+
| `--is_enabled` | No | [create_rule] (boolean, default: `True`) |
|
|
64
|
+
| `--rule_id` | No | [delete_rule] (string) |
|
|
57
65
|
| `--folder_id` | No | [list_emails] Outlook folder ID returned by list_folders. \| [list_email_changes] Outlook folder ID returned by list_folders. (string) |
|
|
58
66
|
| `--received_after` | No | [list_emails] Inclusive UTC date or ISO datetime lower bound. \| [list_email_changes] Initial-round inclusive UTC date or ISO datetime lower bound; omit after a cursor exists. (string) |
|
|
59
67
|
| `--received_before` | No | [list_emails] Exclusive UTC date or ISO datetime upper bound. (string) |
|
|
60
68
|
| `--delta_cursor` | No | [list_email_changes] Opaque delta_cursor saved after the previous completed round. (string) |
|
|
61
|
-
| `--to` | No | [send] A list of email addresses
|
|
62
|
-
| `--subject` | No | [send] The email subject line. \| [draft] Email subject line. (string) |
|
|
69
|
+
| `--to` | No | [send] Optional: A list of primary recipient email addresses. At least one address across to, cc, or bcc is required. \| [draft] Recipient email address(es), comma-separated. \| [reply] Optional: A list of email addresses for primary recipients. If not provided, defaults to the original sender. By default (reply_all=true), all original recipients are included in CC. \| [reply_draft] Optional: A list of email addresses for primary recipients. If not provided, defaults to the original sender. By default (reply_all), all original recipients are included in CC. \| [forward] Optional: A list of email addresses for primary recipients to forward the email to. \| [group_reply] Optional list of recipient email addresses to add as new participants. These recipients will be notified about the reply. (array) |
|
|
70
|
+
| `--subject` | No | [send] Optional: The email subject line. Defaults to empty. \| [draft] Email subject line. (string) |
|
|
63
71
|
| `--body` | No | [send] The email body content. **IMPORTANT**: The format MUST match the content_type parameter: - If content_type='text': Use plain text - If content_type='html': Use HTML format with tags like <h1>, <p>, <ul>, etc. **Note**: Email clients DO NOT support Markdown. Convert Markdown to HTML if needed. \| [draft] Email body content (plain text or HTML). \| [reply] The reply message body. **IMPORTANT**: The format MUST match the content_type parameter: - If content_type='text': Use plain text - If content_type='html': Use HTML format with tags like <h1>, <p>, <ul>, etc. **Note**: Email clients DO NOT support Markdown. Convert Markdown to HTML if needed. \| [reply_draft] The reply content in HTML format. Use HTML tags for formatting (e.g., <br>, <b>, <i>). \| [forward] Optional: Additional message to include above the forwarded content. This is your personal note to recipients. (string) |
|
|
64
72
|
| `--cc` | No | [send] Optional: A list of email addresses for CC recipients. \| [draft] CC recipient(s), comma-separated. \| [reply] Optional: A list of email addresses for CC recipients. If not provided and 'reply_all' is true (default), includes original CC and TO recipients. If 'reply_all' is false, no CC recipients are added. \| [reply_draft] Optional: A list of email addresses for CC recipients. If not provided and 'reply_type' is 'reply_all' (default), includes original CC and TO recipients. If 'reply_type' is 'reply', no CC recipients are added. \| [forward] Optional: A list of email addresses for CC recipients. (array) |
|
|
65
73
|
| `--bcc` | No | [send] Optional: A list of email addresses for BCC recipients. \| [draft] BCC recipient(s), comma-separated. \| [reply] Optional: A list of email addresses for BCC recipients. \| [reply_draft] Optional: A list of email addresses for BCC recipients. \| [forward] Optional: A list of email addresses for BCC recipients. (array) |
|
|
@@ -67,6 +75,8 @@ gsk outlook [options]
|
|
|
67
75
|
| `--content_type` | No | [send] Content type of the body. Default: text/html (recommended) **CRITICAL**: body field format MUST match this parameter: - 'text/plain': body should be plain text - 'text/html': body MUST be valid HTML (not Markdown) Always convert Markdown to HTML before passing to this tool. \| [reply] Content type of the reply body. Default: text/html (recommended) **CRITICAL**: body field format MUST match this parameter: - 'text/plain': body should be plain text - 'text/html': body MUST be valid HTML (not Markdown) Always convert Markdown to HTML before passing to this tool. \| [forward] Content type of the body. Default: text/html \| [group_reply] The format of the content. Use 'text/plain' for plain text or 'text/html' for HTML content. Default is 'text/plain'. (string, one of: text/plain, text/html) |
|
|
68
76
|
| `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [reply] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [forward] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [delete] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [move] If true, skip user confirmation and move immediately. Default is false (require confirmation before moving). (boolean, default: `False`) |
|
|
69
77
|
| `--auto_skip_confirmation` | No | [send] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [reply] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [forward] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [delete] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. \| [move] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. This indicates the node is configured to always skip confirmation. (boolean, default: `False`) |
|
|
78
|
+
| `--client_send_id` | No | [send] Optional stable idempotency key. Normally generated automatically for scheduled and interactive sends. (string) |
|
|
79
|
+
| `--force_resend` | No | [send] Set true only when the user explicitly wants another copy of an otherwise identical email. This bypasses the 10-minute interactive-send deduplication window. (boolean, default: `False`) |
|
|
70
80
|
| `--attachments` | No | [send] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [draft] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [reply] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [reply_draft] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [forward] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). \| [group_reply] Optional file attachments. Each item is either a local file path (read inline by the gsk CLI — the bytes ride in the request body as base64 and are not persisted to blob storage) or an already-hosted URL (file-wrapper URL or other public https). Files are delivered as real email attachments (not links): inline base64 for items ≤3 MB, Microsoft Graph upload session for larger Outlook attachments. CLI alias: --attach / --attachment (repeatable). CLI inline cap: 5 MiB per local file — larger files must be uploaded via 'gsk upload' first and passed as a URL. Per-message raw-payload cap: 18 MiB for Gmail (Gmail's 25 MB send cap is on the base64-encoded RFC 822 message; 18 MiB raw leaves headroom for ~33% encoding overhead) and 150 MB for Outlook (via Graph upload session). (array) |
|
|
71
81
|
| `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
|
|
72
82
|
| `--from_address` | No | [draft] Optional 'From:' identity to send AS — Gmail verified alias, Outlook proxyAddress / mail-enabled group, or a granted SendAs / on-behalf address. Must be an address the from-account is authorized to send as (see 'send_as' on /api/ai-inbox/mailbox/accounts). For Gmail this becomes the draft's MIME 'From:' header; for Outlook the saved draft stays as the from-account and the alias is applied by the eventual send call. (string) |
|
|
@@ -78,7 +88,6 @@ gsk outlook [options]
|
|
|
78
88
|
| `--reply_type` | No | [reply_draft] Type of reply: 'reply' sends only to the original sender, 'reply_all' sends to all recipients of the original email. Default: 'reply_all'. Used to determine default recipients if 'to'/'cc' are not provided. (string, one of: reply, reply_all) |
|
|
79
89
|
| `--include_attachments` | No | [forward] Whether to include original email attachments in the forward. Default: true (boolean, default: `True`) |
|
|
80
90
|
| `--permanent` | No | [delete] Whether to permanently delete the message. Default: false (move to Deleted Items) (boolean) |
|
|
81
|
-
| `--folder_name` | No | [move] The target folder name. Can be a well-known folder (inbox, drafts, sentitems, deleteditems, archive, junkemail, outbox) or a custom folder name. Custom folders will be created if they don't exist. (string) |
|
|
82
91
|
| `--create_if_not_exists` | No | [move] Whether to create the folder if it doesn't exist. Default: true (boolean) |
|
|
83
92
|
| `--message_ids` | No | [mark_as_read] The Outlook message ID(s) to mark. Can be a single ID string or an array of IDs. |
|
|
84
93
|
| `--is_read` | No | [mark_as_read] Set to true to mark as read, false to mark as unread. Default: true (boolean) |
|
|
@@ -96,7 +105,7 @@ gsk outlook [options]
|
|
|
96
105
|
|
|
97
106
|
## Write Confirmation (double-call)
|
|
98
107
|
|
|
99
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
108
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
100
109
|
|
|
101
110
|
## See Also
|
|
102
111
|
|
|
@@ -57,7 +57,7 @@ Parameters that accept URLs (`--sharepoint_url`) also accept local file paths. T
|
|
|
57
57
|
|
|
58
58
|
## Write Confirmation (double-call)
|
|
59
59
|
|
|
60
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
60
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
61
61
|
|
|
62
62
|
## See Also
|
|
63
63
|
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
name: gsk-slack
|
|
3
3
|
version: 1.0.0
|
|
4
4
|
description: 'Slack messaging operations. Actions: send, search, read, lookup, react,
|
|
5
|
-
upload, update, delete, permalink
|
|
5
|
+
upload, update, delete, permalink.'
|
|
6
6
|
metadata:
|
|
7
7
|
category: general
|
|
8
8
|
requires:
|
|
@@ -17,7 +17,7 @@ metadata:
|
|
|
17
17
|
|
|
18
18
|
> **Note:** a unified `gsk connector` flow is rolling out (see `../gsk-connector/SKILL.md`: `gsk connector tools <id>` / `gsk connector call <id> -t <tool>`) and may not be enabled for every account yet. THIS command remains fully supported — use it directly, and it stays the fallback whenever `gsk connector` is unavailable.
|
|
19
19
|
|
|
20
|
-
Slack messaging operations. Actions: send, search, read, lookup, react, upload, update, delete, permalink
|
|
20
|
+
Slack messaging operations. Actions: send, search, read, lookup, react, upload, update, delete, permalink.
|
|
21
21
|
|
|
22
22
|
## Usage
|
|
23
23
|
|
|
@@ -29,19 +29,19 @@ gsk slack [options]
|
|
|
29
29
|
|
|
30
30
|
| Flag | Required | Description |
|
|
31
31
|
|------|----------|-------------|
|
|
32
|
-
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user
|
|
32
|
+
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'search': Search messages by keyword; 'read': Read recent message history of a channel (or one thread); 'lookup': Look up users, channels, or groups; 'react': Emoji-react to a message (or remove your reaction). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'invite': Invite workspace members into a channel. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'upload': Upload a file into a channel, group, or DM. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'update': Edit one of the user's own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'delete': Delete one of the user's own messages. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'permalink': Get the permanent link for a message (string, one of: send, search, read, lookup, react, invite, upload, update, delete, permalink) |
|
|
33
33
|
| `--message` | No | [send] The message content to send. Supports Slack markdown formatting. To @mention someone, embed '<@USER_ID>' (e.g. '<@U01234567>') in the text — a plain '@Name' renders as literal text and notifies nobody. User IDs come from the lookup action. 'content' is accepted as an alias for this parameter. (string) |
|
|
34
34
|
| `--recipient` | No | [send] Optional recipient: 'self' (default), channel ID (e.g., 'C01234567'), or user ID (e.g., 'U01234567'). If not specified, sends to yourself. (string) |
|
|
35
35
|
| `--title` | No | [send] Optional title for the message. If provided, creates a rich formatted message with a header. \| [upload] Optional title shown on the Slack file card. Defaults to the file name. (string) |
|
|
36
36
|
| `--fields` | No | [send] Optional array of field objects with 'title' and 'value' keys to create a structured message layout. (array) |
|
|
37
37
|
| `--thread_ts` | No | [send] Optional thread timestamp to reply in a thread. \| [read] Timestamp ('ts') of a thread's parent message. When set, returns that thread's replies instead of the channel timeline. \| [upload] Optional thread timestamp — share the file as a reply in this thread instead of the conversation root. (string) |
|
|
38
38
|
| `--query` | No | [search] The search query. You can use modifiers like 'in:#channel', 'from:@user', 'has:link', 'before:yyyy-mm-dd'. (string) |
|
|
39
|
-
| `--count` | No | [search] The maximum number of messages to return. Default is 100.
|
|
39
|
+
| `--count` | No | [search] The maximum number of messages to return. Default is 100. (integer) |
|
|
40
40
|
| `--sort` | No | [search] Sort order of results. 'score' for relevance or 'timestamp' for time. Default is 'score'. (string) |
|
|
41
41
|
| `--question` | No | [search] A specific question to answer based on the search results. (string) |
|
|
42
42
|
| `--channel` | No | [read] Conversation ID (channel 'C…', private group 'G…', or DM 'D…') or a channel name (e.g. '#general' or 'general'). IDs come from the lookup action. \| [react] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [invite] Conversation ID of the channel to invite into (public 'C…' or private group 'G…'). \| [upload] Target conversation ID (channel 'C…', private group 'G…', or DM 'D…') the file is shared into. \| [update] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [delete] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [permalink] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). (string) |
|
|
43
43
|
| `--limit` | No | [read] Maximum messages to return (default 20, max 100). \| [lookup] Maximum number of results to return. Default: 50 (integer) |
|
|
44
|
-
| `--cursor` | No | [read] Pagination cursor from a previous call's next_cursor to fetch older messages.
|
|
44
|
+
| `--cursor` | No | [read] Pagination cursor from a previous call's next_cursor to fetch older messages. (string) |
|
|
45
45
|
| `--lookup_type` | No | [lookup] What to look up: 'users' for team members, 'channels' for channels/conversations, 'all' for both. (string, one of: users, channels, all) |
|
|
46
46
|
| `--search_query` | No | [lookup] Optional search query to filter results by name. Case-insensitive partial match on name, display name, or real name. (string) |
|
|
47
47
|
| `--include_bots` | No | [lookup] Whether to include bot users in results. Default: false (boolean) |
|
|
@@ -53,15 +53,13 @@ gsk slack [options]
|
|
|
53
53
|
| `--file_path` | No | [upload] File to upload: a local server file path, a Genspark file-wrapper URL (https://…/api/files/s/<code>), or an AI Drive path (aidrive://…). Provide exactly one of 'content' or 'file_path'. (string) |
|
|
54
54
|
| `--file_name` | No | [upload] File name shown in Slack (include the extension, e.g. 'report.pdf'). Required with 'content'; defaults to the path basename for 'file_path'. (string) |
|
|
55
55
|
| `--initial_comment` | No | [upload] Optional message text posted together with the file. (string) |
|
|
56
|
-
| `--skip_confirmation` | No | [update] Skip the user-confirmation step. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. \| [delete] Skip the user-confirmation step. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false.
|
|
57
|
-
| `--auto_skip_confirmation` | No | [update] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false.
|
|
56
|
+
| `--skip_confirmation` | No | [update] Skip the user-confirmation step. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. \| [delete] Skip the user-confirmation step. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. (boolean) |
|
|
57
|
+
| `--auto_skip_confirmation` | No | [update] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean) |
|
|
58
58
|
| `--text` | No | [update] The full replacement text (mrkdwn) — Slack replaces the whole message body, not a diff. (string) |
|
|
59
|
-
| `--invite_id` | No | [connect_approve] The Slack Connect invite ID (e.g. 'I…'), from the connect_invites list. \| [connect_decline] The Slack Connect invite ID (e.g. 'I…'), from the connect_invites list. (string) |
|
|
60
|
-
| `--target_team` | No | [connect_approve] Optional team/enterprise ID of the other party in the invitation. \| [connect_decline] Optional team/enterprise ID of the other party in the invitation. (string) |
|
|
61
59
|
|
|
62
60
|
## Write Confirmation (double-call)
|
|
63
61
|
|
|
64
|
-
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command: the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true`
|
|
62
|
+
Write actions (send / create / update / delete / react / upload, and write methods through `api` where present) may be confirmation-gated. Completing the confirmation REQUIRES a persistent project: pass `--project-id <id>` or set `GSK_PROJECT_ID` on both calls. Without one, a gated call fails immediately with `confirmation_requires_project` instead of an uncompletable pending. A response carrying `status: "pending_confirmation"` (or a similar needs-confirmation payload) is NOT a failure — it executes nothing and summarizes what would happen. To complete the write, re-run the IDENTICAL command (same project id): the pending record (15-minute TTL) is matched and the operation executes; success clears the record (a further identical call pends again) and a failed execution keeps it, so the retry arc stays open. Where the Flags table lists `--skip_confirmation` for an action, passing `--skip_confirmation true` is honored on the CLI and executes in one call; gated actions without that flag complete ONLY via the double-call.
|
|
65
63
|
|
|
66
64
|
## See Also
|
|
67
65
|
|