@genspark/cli 1.7.0 → 1.8.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (39) hide show
  1. package/README.md +21 -9
  2. package/dist/commands/aidrive-download.d.ts +7 -0
  3. package/dist/commands/aidrive-download.d.ts.map +1 -1
  4. package/dist/commands/aidrive-download.js +17 -1
  5. package/dist/commands/aidrive-download.js.map +1 -1
  6. package/dist/index.d.ts.map +1 -1
  7. package/dist/index.js +87 -44
  8. package/dist/index.js.map +1 -1
  9. package/dist/pendingApproval.d.ts +98 -0
  10. package/dist/pendingApproval.d.ts.map +1 -0
  11. package/dist/pendingApproval.js +252 -0
  12. package/dist/pendingApproval.js.map +1 -0
  13. package/dist/types.d.ts +2 -0
  14. package/dist/types.d.ts.map +1 -1
  15. package/docs/skills.md +4 -4
  16. package/package.json +1 -1
  17. package/skills/gsk-aidrive/SKILL.md +38 -24
  18. package/skills/gsk-batch-crawl-url-and-answer/SKILL.md +7 -7
  19. package/skills/gsk-genteam/SKILL.md +40 -23
  20. package/skills/gsk-github/SKILL.md +1 -1
  21. package/skills/gsk-gmail/SKILL.md +3 -2
  22. package/skills/gsk-google-calendar/SKILL.md +1 -1
  23. package/skills/gsk-google-chat/SKILL.md +4 -2
  24. package/skills/gsk-google-docs/SKILL.md +1 -1
  25. package/skills/gsk-google-drive/SKILL.md +2 -2
  26. package/skills/gsk-google-sheets/SKILL.md +1 -1
  27. package/skills/gsk-google-slides/SKILL.md +1 -1
  28. package/skills/gsk-hub/SKILL.md +1 -1
  29. package/skills/gsk-meeting/SKILL.md +8 -2
  30. package/skills/gsk-microsoft-teams/SKILL.md +6 -5
  31. package/skills/gsk-notion/SKILL.md +1 -1
  32. package/skills/gsk-onedrive/SKILL.md +2 -2
  33. package/skills/gsk-outlook-calendar/SKILL.md +1 -1
  34. package/skills/gsk-outlook-email/SKILL.md +4 -2
  35. package/skills/gsk-phone-call/SKILL.md +19 -11
  36. package/skills/gsk-sharepoint/SKILL.md +2 -2
  37. package/skills/gsk-slack/SKILL.md +4 -3
  38. package/skills/gsk-video-generation/SKILL.md +3 -3
  39. package/skills/gsk-youtube/SKILL.md +11 -4
@@ -2,8 +2,9 @@
2
2
  name: gsk-genteam
3
3
  version: 1.0.0
4
4
  description: 'GenTeam (Genspark team workspace) operations as the calling user. Actions:
5
- join, channels, agents, read, search, send, create_channel, update_channel, invite_link,
6
- members, tasks.'
5
+ join, channels, agents, read, threads, download, search, send, react, delete, update,
6
+ create_channel, update_channel, invite_link, members, tasks, mark_read, forward,
7
+ pins, dm.'
7
8
  metadata:
8
9
  category: general
9
10
  requires:
@@ -16,7 +17,7 @@ metadata:
16
17
 
17
18
  **PREREQUISITE:** Read `../gsk-shared/SKILL.md` for auth, global flags, and security rules.
18
19
 
19
- GenTeam (Genspark team workspace) operations as the calling user. Actions: join, channels, agents, read, search, send, create_channel, update_channel, invite_link, members, tasks.
20
+ GenTeam (Genspark team workspace) operations as the calling user. Actions: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm.
20
21
 
21
22
  ## Usage
22
23
 
@@ -28,41 +29,57 @@ gsk genteam [options]
28
29
 
29
30
  | Flag | Required | Description |
30
31
  |------|----------|-------------|
31
- | `<action>` (positional) | Yes | Action to perform. 'join': Join a GenTeam workspace or channel from an invite link; 'channels': List the caller's workspaces, or one workspace's channels by server_slug; 'agents': List a workspace's agents visible to the caller by server_slug; each id is a mention target for send; 'read': Read recent messages from a channel, DM, or thread; 'search': Search a workspace (messages, tasks, members, channels, agents) by server_slug, or find-in-channel by channel_id; 'send': Send a message (text, attachment, or thread reply) to a channel or DM as the caller; supports native @mentions (humans and agents) and native quote replies; 'create_channel': Create a channel in a workspace; the caller becomes its manager and auto-joins; 'update_channel': Edit a channel's display name, description, or member permission switches (manager only); 'invite_link': Create, list, or revoke the invite links that genteam_join consumes (workspace or channel scoped); 'members': List, add, or remove channel members (humans and agents) by actor id; 'tasks': Task board: list a channel's or workspace's tasks, get one task with its event history, claim/unclaim it, or change its status (string, one of: join, channels, agents, read, search, send, create_channel, update_channel, invite_link, members, tasks) |
32
+ | `<action>` (positional) | Yes | Action to perform. 'join': Join a GenTeam workspace or group chat from an invite link; 'channels': List the caller's workspaces, or one workspace's group chats by server_slug; 'agents': List a workspace's agents visible to the caller by server_slug; each id is a mention target for send; 'read': Read recent messages from a group chat, DM, or thread; around_message_id fetches the window around one message (e.g. a search hit); a thread is also addressable by its root message id via parent_message_id; 'threads': List a group chat's or DM's threads (thread channel id, root comet_message_id, caller_is_participant, reply count / last activity); channel membership is the only requirement; 'download': Download one message attachment (attachments[].attachment_ref from read output) to a fetchable file-wrapper URL; 'search': Search a workspace by server_slug, or one group chat, DM, or thread by channel_id; 'send': Send a message (text, attachment, or thread reply) to a group chat or DM as the caller; a thread reply is also addressable by its root message id via parent_message_id. Supports native @mentions (humans and agents) and native quote replies. Held for confirmation: the first call returns pending_confirmation (nothing is posted); re-run the identical call to confirm and send. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'react': Emoji-react to a message in a group chat, DM, or thread (or remove your own reaction). 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 in a group chat, DM, or thread (author-only, the same gate the app enforces). 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 (the caption on an attachment message); attachments and existing @mentions are preserved (author-only, the same gate the app enforces). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'create_channel': Create a group chat in a workspace; the caller becomes its manager and auto-joins. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'update_channel': Edit a group chat's display name, description, or member permission switches (manager only). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'invite_link': Create, list, or revoke the invite links that genteam_join consumes (workspace or group chat scoped). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'members': List, add, or remove group chat members (humans and agents) by actor id; op=list also reads a DM's or thread's roster. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'tasks': Task board: list a group chat's, DM's, or workspace's tasks, get one task with its event history, create a task from a message, claim/unclaim it, assign it to one of the caller's agents (op=candidates lists them), rename it, or change its status. Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'mark_read': Mark a group chat, DM, or thread read (clears the caller's unread count), or back to unread with unread=true; 'forward': Forward one message to another group chat or DM you can post to, with the app's forward semantics (original author attribution and preview; optional note above the forwarded card). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'pins': List a group chat's pinned messages, or pin/unpin one by its comet_message_id (any active member may, the same rule the app enforces; a thread id addresses its parent group chat's pins). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes.; 'dm': List the caller's DMs in a workspace (op=list: peer actor_type + actor_id per row), or open a DM with a human contact or agent (op=open: returns the app's deterministic channel_id, reusing an existing DM; held for confirmation). Confirmation-gated: requires --project-id / GSK_PROJECT_ID — the first call returns pending_confirmation, re-running the identical command executes. (string, one of: join, channels, agents, read, threads, download, search, send, react, delete, update, create_channel, update_channel, invite_link, members, tasks, mark_read, forward, pins, dm) |
32
33
  | `--invite_url` | No | [join] Full invite link URL, including the token query parameter. (string) |
33
34
  | `--invite_id` | No | [join] Invite link id (alternative to invite_url; requires token). \| [invite_link] Invite link id to revoke (from op=list or the create result). (string) |
34
35
  | `--token` | No | [join] Invite link token (alternative to invite_url; requires invite_id). (string) |
35
- | `--server_slug` | No | [channels] Workspace slug (from the workspace list or a GenTeam URL path segment). \| [agents] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [search] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). Required unless channel_id is given. \| [create_channel] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [invite_link] Workspace slug; required unless channel_id is given. \| [tasks] list: workspace slug (from genteam_list_channels) for the caller's cross-channel board. (string) |
36
+ | `--server_slug` | No | [channels] Workspace slug (from the workspace list or a GenTeam URL path segment). \| [agents] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [search] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). Required unless channel_id is given. \| [create_channel] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). \| [invite_link] Workspace slug; required unless channel_id is given. \| [tasks] list: workspace slug (from genteam_list_channels) for the caller's workspace-wide board. \| [dm] Workspace slug (from genteam_list_channels or a GenTeam URL path segment). (string) |
36
37
  | `--mine` | No | [agents] When true, return only agents the caller created. Default false. (boolean) |
37
- | `--channel_id` | No | [read] Channel id (from genteam_list_channels). \| [search] Find-in-channel target (from genteam_list_channels). When given, the search is scoped to this one channel. \| [send] Target channel id (from genteam_list_channels). \| [update_channel] Channel id (from genteam_list_channels). \| [invite_link] Channel id — scopes create/list to that channel's join links. \| [members] Channel id (from genteam_list_channels). \| [tasks] list: channel board target (from genteam_list_channels). Mutually exclusive with server_slug. (string) |
38
- | `--limit` | No | [read] Messages to return (1..200). Default 20. \| [search] Workspace mode only: max hits per group (default 8). Channel mode pages are a fixed 20 per request. \| [tasks] list (channel mode): page size, 1..100 (default 20). (integer) |
38
+ | `--channel_id` | No | [read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). Optional when parent_message_id is passed. \| [threads] Group chat or DM id whose threads to list (from genteam_list_channels). \| [download] Group chat, DM, or thread id the attachment's message lives in (the channel_id on the read output's attachment row). \| [search] Group chat, DM, or thread to search within (group chats and DMs from genteam_list_channels; thread ids from genteam_threads or genteam_tasks output). \| [send] Target group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). Optional when parent_message_id is passed. \| [react] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [delete] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update] Group chat, DM, or thread id the message lives in (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [update_channel] Group chat id (from genteam_list_channels). \| [invite_link] Group chat id — scopes create/list to that group chat's join links. \| [members] Group chat id (from genteam_list_channels); op=list also accepts a DM or thread id. \| [tasks] list: group chat or DM board target (from genteam_list_channels). Mutually exclusive with server_slug. create/candidates: the group chat or DM whose board is targeted (required). \| [mark_read] Group chat, DM, or thread id (group chats and DMs from genteam_list_channels; thread ids arrive in context, e.g. genteam_tasks output). \| [forward] Group chat, DM, or thread id the message lives in (from genteam_list_channels; thread ids arrive in context, e.g. genteam_read output). \| [pins] Group chat id (from genteam_list_channels); a thread id resolves to its parent group chat's pins. (string) |
39
+ | `--parent_message_id` | No | [read] comet_message_id of a thread's root message: read that message's thread without knowing the thread channel id. If channel_id is also passed it must agree (the thread itself, or the group chat/DM containing the root message). \| [send] comet_message_id of a thread's root message: post this message as a reply in that message's thread without knowing the thread channel id. If channel_id is also passed it must agree (the thread itself, or the group chat/DM containing the root message). (string) |
40
+ | `--limit` | No | [read] Messages to return (1..200). Default 20. \| [search] Workspace mode only: max hits per group (default 8). Conversation mode pages are a fixed 20 per request. \| [tasks] list (channel_id mode): page size, 1..100 (default 20). (integer) |
39
41
  | `--before_message_id` | No | [read] Message id cursor: return messages strictly older than this id. (string) |
40
42
  | `--after_message_id` | No | [read] Message id cursor: return messages strictly newer than this id. Mutually exclusive with before_message_id. (string) |
43
+ | `--around_message_id` | No | [read] Anchor message id (comet_message_id from search, read, or threads output): return the visible window around it — roughly half of limit older, the anchor itself, and half newer. Errors if the anchor is not in this conversation. Mutually exclusive with before_message_id and after_message_id. (string) |
44
+ | `--attachment_ref` | No | [download] Attachment reference '{comet_message_id}:{index}' from genteam_read output (attachments[].attachment_ref). (string) |
41
45
  | `--query` | No | [search] Search keywords. (string) |
42
- | `--scope` | No | [search] Workspace mode: everything (default), messages, tasks, members, channels, or agents. Channel mode: messages (default), contacts, or files. (string) |
43
- | `--cursor` | No | [search] Channel mode only: opaque paging cursor echoed by the previous page. \| [tasks] list (channel mode): opaque paging cursor echoed by the previous page as next_cursor. (string) |
46
+ | `--scope` | No | [search] Workspace mode: everything (default), messages, tasks, members, channels, or agents. Conversation mode: messages (default), contacts, or files. (string) |
47
+ | `--cursor` | No | [search] Conversation mode only: opaque paging cursor echoed by the previous page. \| [tasks] list (channel_id mode): opaque paging cursor echoed by the previous page as next_cursor. (string) |
44
48
  | `--content` | No | [send] Plain-text message body; with file_path it is the attachment caption (optional in that case). (string) |
45
49
  | `--file_path` | No | [send] File to attach: a Genspark file-wrapper URL (https://…/api/files/s/<code>, from `gsk upload`) or an AI Drive path (aidrive://…). (string) |
46
50
  | `--file_name` | No | [send] Display file name for the attachment; defaults to the name derived from file_path. (string) |
47
- | `--mentions` | No | [send] Members to @mention — humans or agents: agent ids (agent_…, from genteam_list_agents), human member ids (UUID), or exact display names (must be unambiguous in the channel). Each must already be a member of the target channel. Mention chips are rendered natively and the mentioned members are notified (agents wake and process the message). (array) |
48
- | `--quote_message_id` | No | [send] comet_message_id of an existing message in this channel (from genteam_read) to quote — renders as the app's native quote block. Text sends only. (string) |
49
- | `--operation_id` | No | [send] Idempotency key: retries with the same operation_id return the already-sent message instead of posting a duplicate. (string) |
50
- | `--name` | No | [create_channel] Channel slug: lowercase letters, digits, '-' and '_', max 30 chars (e.g. 'release-train'). Immutable after creation — URLs and mentions depend on it; only display_name can change later. (string) |
51
- | `--display_name` | No | [create_channel] Optional human-readable channel name (max 80 chars). \| [update_channel] New human-readable channel name (max 80 chars); empty string clears the override. (string) |
52
- | `--description` | No | [create_channel] Optional channel description (max 500 chars). \| [update_channel] New channel description (max 500 chars); empty string clears it. (string) |
53
- | `--member_invite_enabled` | No | [update_channel] Whether ordinary members may create invite links for this channel. (boolean) |
54
- | `--member_agent_add_enabled` | No | [update_channel] Whether ordinary members may add their own agents to this channel. (boolean) |
55
- | `--op` | No | [invite_link] Operation to perform. \| [members] Operation to perform. \| [tasks] Operation to perform. (string, one of: create, list, revoke) |
51
+ | `--mentions` | No | [send] Members to @mention — humans or agents: agent ids (agent_…, from genteam_list_agents), human member ids (UUID), or exact display names (must be unambiguous in the target conversation). Each must already be a member of the target conversation. Mention chips render natively. Humans are notified; agents wake unless creator-only mode blocks the sender. Read any owner_only_mentions advisory in the reply before expecting an answer. A canonical @[name](id) token is auto-prepended to the body for each mention, skipped when the body already contains that member's token — so do NOT also write the token inline for the same member (it would be redundant, not doubled). (array) |
52
+ | `--quote_message_id` | No | [send] comet_message_id of an existing message in this conversation (from genteam_read) to quote — renders as the app's native quote block. Text sends only. (string) |
53
+ | `--operation_id` | No | [send] Idempotency key with two roles in the double-call confirmation flow: while the send is pending_confirmation, re-running the IDENTICAL call (same operation_id and arguments) is the confirmation itself and performs the send; after a successful send, retries with the same operation_id return the already-sent message instead of posting a duplicate. \| [forward] Optional idempotency key (8-64 chars of [A-Za-z0-9_-]). After a successful forward, retries with the same operation_id return the already-forwarded message instead of posting a duplicate. Without it a re-run posts a duplicate forward. (string) |
54
+ | `--skip_sent_via_tag` | No | [send] Messages sent through this tool carry a small 'via API' source tag next to the sender name. Set true to send this one message without the tag. (boolean) |
55
+ | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending: the first call returns pending_confirmation and an identical re-run confirms). On LLM agent paths the flag is only honored after the user actually confirmed. \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [delete] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [update] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [create_channel] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [update_channel] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [invite_link] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [members] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [tasks] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [forward] If true, skip user confirmation and forward immediately. Default is false (require confirmation before posting: the first call returns pending_confirmation and an identical re-run confirms). \| [pins] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [dm] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). (boolean, default: `False`) |
56
+ | `--auto_skip_confirmation` | No | [send] Set by the workflow engine when the node is configured to skip confirmation. \| [react] 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. \| [update] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [create_channel] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [update_channel] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [invite_link] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [members] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [tasks] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [forward] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [pins] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [dm] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean) |
57
+ | `--message_id` | No | [react] comet_message_id of the message to react to (from genteam_read). \| [delete] comet_message_id of YOUR OWN message to delete (from genteam_read). \| [update] comet_message_id of YOUR OWN message to edit (from genteam_read). \| [mark_read] Optional comet_message_id (from genteam_read). Marking read: the highest message to mark read (inclusive); omit to mark the whole conversation read. Marking unread: the first message to show as unread (group chats and DMs only — threads take no anchor); omit to anchor at the latest message. \| [forward] comet_message_id of the message to forward (from genteam_read of the source conversation). \| [pins] pin/unpin: comet_message_id of the target message (from genteam_read or op=list output). (string) |
58
+ | `--emoji` | No | [react] The emoji as a unicode character itself, e.g. '👍' or '🎉' (not ':thumbsup:'). (string) |
59
+ | `--remove` | No | [react] true removes YOUR OWN existing reaction instead of adding one. Default: false. (boolean, default: `False`) |
60
+ | `--text` | No | [update] The full replacement text (not a diff). Replaces the message body, or the caption on an attachment message. (string) |
61
+ | `--name` | No | [create_channel] Group chat slug: lowercase letters, digits, '-' and '_', max 30 chars (e.g. 'release-train'). Immutable after creation — URLs and mentions depend on it; only display_name can change later. (string) |
62
+ | `--display_name` | No | [create_channel] Optional human-readable group chat name (max 80 chars). \| [update_channel] New human-readable group chat name (max 80 chars); empty string clears the override. (string) |
63
+ | `--description` | No | [create_channel] Optional group chat description (max 500 chars). \| [update_channel] New group chat description (max 500 chars); empty string clears it. \| [tasks] create: optional task description (max 4000 chars). (string) |
64
+ | `--member_invite_enabled` | No | [update_channel] Whether ordinary members may create invite links for this group chat. (boolean) |
65
+ | `--member_agent_add_enabled` | No | [update_channel] Whether ordinary members may add their own agents to this group chat. (boolean) |
66
+ | `--op` | No | [invite_link] Operation to perform. \| [members] Operation to perform. \| [tasks] Operation to perform. \| [pins] Operation to perform. \| [dm] Operation to perform. (string, one of: create, list, revoke) |
56
67
  | `--max_uses` | No | [invite_link] create: how many joins the link allows (default per workspace size). (integer) |
57
68
  | `--expires_days` | No | [invite_link] create: link validity in days (default per workspace size). (integer) |
58
- | `--actor_type` | No | [members] add/remove: whether the target is a human or an agent. (string, one of: human, agent) |
59
- | `--actor_id` | No | [members] add/remove: the member id — a cogen UUID for humans, an agent_… id for agents. (string) |
60
- | `--task_id` | No | [tasks] get/claim/unclaim/status: the task id (task_…, from op=list). (string) |
69
+ | `--actor_type` | No | [members] add/remove: whether the target is a human or an agent. \| [dm] open: whether the DM target is a human or an agent. (string, one of: human, agent) |
70
+ | `--actor_id` | No | [members] add/remove: the member id — a cogen UUID for humans, an agent_… id for agents. \| [dm] open: the DM target — a cogen UUID for humans, an agent_… id for agents (from op=list, genteam_members, or genteam_list_agents). (string) |
71
+ | `--task_id` | No | [tasks] get/claim/unclaim/status/assign/rename: the task id (task_…, from op=list). (string) |
72
+ | `--source_message_id` | No | [tasks] create: the message the task anchors to (message id from genteam_read_channel or genteam_search). Creating again from the same message returns the existing task (created=false). (string) |
73
+ | `--title` | No | [tasks] create: optional title (defaults to a snapshot of the source message). rename: the new title (required, max 400 chars). (string) |
74
+ | `--assignee_id` | No | [tasks] assign: the agent to assign (agent id from op=candidates; only agents the caller created and that are active channel members are assignable). (string) |
61
75
  | `--status` | No | [tasks] op=list: status filter — active (default, = not done), all, or a comma list of todo, in_progress, in_review, done. op=status: the new status (one of those four). (string) |
62
76
  | `--reason` | No | [tasks] op=status: optional note recorded on the status-change event. (string) |
63
- | `--involvement` | No | [tasks] list (channel mode): me narrows to tasks the caller has a tie to (assignee, requester, creator, or thread participant). Default all. (string, one of: all, me) |
77
+ | `--involvement` | No | [tasks] list (channel_id mode): me narrows to tasks the caller has a tie to (assignee, requester, creator, or thread participant). Default all. (string, one of: all, me) |
64
78
  | `--assignee` | No | [tasks] list: assignee filter — current (the caller), unassigned, agent:<id>, or human:<cogen_id>. (string) |
65
79
  | `--requester` | No | [tasks] list: requester/owner filter — same forms as assignee. (string) |
80
+ | `--unread` | No | [mark_read] true marks the conversation back to unread (Slack-style 'come back later') instead of read. Default: false. (boolean, default: `False`) |
81
+ | `--target_channel_id` | No | [forward] Group chat or DM to forward into (from genteam_list_channels). Threads are not valid targets — the app forwards into channels and DMs only. (string) |
82
+ | `--note` | No | [forward] Optional message of your own shown above the forwarded card (plain text). (string) |
66
83
 
67
84
  ## Local File Support
68
85
 
@@ -70,7 +87,7 @@ Parameters that accept URLs (`--invite_url`) also accept local file paths. The C
70
87
 
71
88
  ## Write Confirmation (double-call)
72
89
 
73
- 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
90
+ 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.
74
91
 
75
92
  ## See Also
76
93
 
@@ -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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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
 
@@ -30,7 +30,7 @@ gsk gmail [options]
30
30
 
31
31
  | Flag | Required | Description |
32
32
  |------|----------|-------------|
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; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email; 'forward': Forward an email to new recipients; 'delete': Delete an email; 'archive': Archive an email; 'move': Move an email to a different label/folder; '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; '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; 'get_signature': Get the signature of a send-as address; 'update_signature': Set or clear the signature of a send-as address (string, one of: 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) |
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. 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; '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, get_attachment, list_send_as, get_vacation, update_vacation, get_signature, update_signature) |
34
34
  | `--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
35
  | `--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
36
  | `--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) |
@@ -55,6 +55,7 @@ gsk gmail [options]
55
55
  | `--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
56
  | `--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
57
  | `--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) |
58
+ | `--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
59
  | `--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
60
  | `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
60
61
  | `--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) |
@@ -86,7 +87,7 @@ gsk gmail [options]
86
87
 
87
88
  ## Write Confirmation (double-call)
88
89
 
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
90
+ 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
91
 
91
92
  ## See Also
92
93
 
@@ -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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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,13 +30,15 @@ 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); 'upload': Upload a file (local path, file-wrapper URL, AI Drive path, or text content) to a space as a message attachment; 'update': Edit the text of one of your own messages; 'delete': Delete one of your own messages; 'react': Add or remove an emoji reaction on a message (unicode emoji; remove affects your own reaction only); 'list_members': List all members of a space (full roster) (string, one of: list_spaces, read, send, upload, update, delete, react, list_members) |
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) |
37
37
  | `--thread` | No | [read] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to return only that thread's messages — e.g. to verify where a threaded reply landed. \| [send] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to reply in a thread. Omit to start a new thread. If the thread cannot be replied to, the API starts a NEW thread instead — the response then carries 'thread_fallback': true and 'actual_thread' (set 'strict_thread' to fail instead). \| [upload] Optional thread resource name (e.g. 'spaces/AAAAxxxx/threads/yyyy') to attach in a thread. Omit to start a new thread. If the thread cannot be replied to, the API starts a NEW thread instead — the response then carries 'thread_fallback': true and 'actual_thread' (set 'strict_thread' to fail instead). (string) |
38
38
  | `--message` | No | [send] The message text to send. Supports Google Chat formatting. To @mention someone, embed '<users/{user_id}>' in the text — a plain '@Name' renders as literal text and notifies nobody. User ids come from google_chat_list_members ('user' field) or the 'mentions' field on read messages; '<users/all>' mentions the whole space. 'content' is accepted as an alias for this parameter. \| [upload] Optional caption text sent with the attachment. \| [update] Message resource name to edit, e.g. 'spaces/AAAAxxxx/messages/yyyy'. \| [delete] Message resource name to delete, e.g. 'spaces/AAAAxxxx/messages/yyyy'. \| [react] Message resource name, e.g. 'spaces/AAAAxxxx/messages/yyyy'. (string) |
39
39
  | `--strict_thread` | No | [send] If true and 'thread' is set, fail with an error when the thread cannot be replied to instead of falling back to a new thread. Default: false. \| [upload] If true and 'thread' is set, fail with an error when the thread cannot be replied to instead of falling back to a new thread. Default: false. (boolean, default: `False`) |
40
+ | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [upload] If true, skip user confirmation and send immediately. Default is false. \| [update] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [delete] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). (boolean, default: `False`) |
41
+ | `--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. \| [upload] Set to true ONLY if the workflow step has [AUTO_SKIP_CONFIRMATION] marker. \| [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. \| [react] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean, default: `False`) |
40
42
  | `--file_path` | No | [upload] Path or URL of the file to upload. Accepts (1) a local server filesystem path; (2) a Genspark file-wrapper URL (``https://www.genspark.ai/api/files/s/<code>``); or (3) an AI Drive path (``/mnt/aidrive/...``, ``/aidrive/...``, ``aidrive://...``). Mutually exclusive with ``content``. (string) |
41
43
  | `--content` | No | [upload] Text content to upload as the file body (UTF-8). Requires ``file_name``. Mutually exclusive with ``file_path``. (string) |
42
44
  | `--file_name` | No | [upload] File name including extension (e.g. 'report.pdf'). Required with ``content``; defaults to the source basename with ``file_path``. (string) |
@@ -46,7 +48,7 @@ gsk google_chat [options]
46
48
 
47
49
  ## Write Confirmation (double-call)
48
50
 
49
- 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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.
50
52
 
51
53
  ## See Also
52
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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
 
@@ -29,7 +29,7 @@ gsk hub [options]
29
29
 
30
30
  | Flag | Required | Description |
31
31
  |------|----------|-------------|
32
- | `<action>` (positional) | Yes | Action to perform. 'list_hubs': List the user's Genspark Hubs; 'read_hub': Read one hub's metadata, members, files, and projects; 'read_file': Read a hub file's extracted text (line numbers, limit/offset pagination); 'read_long_line': Read the full content of a truncated file line; 'grep_files': Regex-search hub file text (optional include file filter; 10 files per call, page with file_offset); 'get_file_url': Get a shareable URL for the original hub file (raw bytes, for download / binary analysis); 'search_sessions': Find previous sessions in a hub by keyword (empty query = recent sessions); 'grep_session': Regex-search one hub session's conversation history; 'read_session': Read one hub session's conversation history (line numbers, limit/offset pagination); 'read_long_line_session': Read the full content of a truncated session line (string, one of: list_hubs, read_hub, read_file, read_long_line, grep_files, get_file_url, search_sessions, grep_session, read_session, read_long_line_session) |
32
+ | `<action>` (positional) | Yes | Action to perform. 'list_hubs': List the user's Genspark Hubs; 'read_hub': Read one hub's metadata, members, files, and projects; 'read_file': Read a hub file's extracted text (line numbers, limit/offset pagination); 'read_long_line': Read the full content of a truncated file line; 'grep_files': Regex-search hub file text (optional include file filter; 10 files per call, page with file_offset); 'get_file_url': Get a shareable URL for the original hub file (raw bytes, for download / binary analysis); 'search_sessions': Find previous sessions in a hub by keyword (empty query = recent sessions); also lists this session's own archived conversations; 'grep_session': Regex-search one hub session's conversation history; 'read_session': Read one hub session's conversation history (line numbers, limit/offset pagination); 'read_long_line_session': Read the full content of a truncated session line (string, one of: list_hubs, read_hub, read_file, read_long_line, grep_files, get_file_url, search_sessions, grep_session, read_session, read_long_line_session) |
33
33
  | `--include_archived` | No | [list_hubs] Also include archived hubs. Default: false. (boolean) |
34
34
  | `--hub_id` | No | [read_hub] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [read_file] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [read_long_line] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [grep_files] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [get_file_url] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [search_sessions] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [grep_session] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [read_session] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. \| [read_long_line_session] Hub ID (from hub_list_hubs). Optional when the calling project belongs to a hub — defaults to that hub. (string) |
35
35
  | `--file_name` | No | [read_file] Exact file name from hub_read_hub's files list. \| [read_long_line] Exact file name from hub_read_hub's files list. \| [get_file_url] Exact file name from hub_read_hub's files list. (string) |
@@ -1,7 +1,13 @@
1
1
  ---
2
2
  name: gsk-meeting
3
3
  version: 1.0.0
4
- description: 'Meeting notes operations. Actions: list, search, get.'
4
+ description: 'Meeting notes operations. Actions: list, search, get. Covers the user''s
5
+ meeting/voice notes from ALL capture apps: notes created in AI Meeting Notes / AI
6
+ Notes (web & mobile app), Speakly, or SecondBrain Notes (hardware recorder) are
7
+ all stored here — when the user names one of these products, use these meeting-notes
8
+ tools. Completed notes are searchable by content; use the product name itself as
9
+ a search keyword only if the note content is actually about it. Voice dictation
10
+ history is NOT searchable by these tools.'
5
11
  metadata:
6
12
  category: general
7
13
  requires:
@@ -14,7 +20,7 @@ metadata:
14
20
 
15
21
  **PREREQUISITE:** Read `../gsk-shared/SKILL.md` for auth, global flags, and security rules.
16
22
 
17
- Meeting notes operations. Actions: list, search, get.
23
+ Meeting notes operations. Actions: list, search, get. Covers the user's meeting/voice notes from ALL capture apps: notes created in AI Meeting Notes / AI Notes (web & mobile app), Speakly, or SecondBrain Notes (hardware recorder) are all stored here — when the user names one of these products, use these meeting-notes tools. Completed notes are searchable by content; use the product name itself as a search keyword only if the note content is actually about it. Voice dictation history is NOT searchable by these tools.
18
24
 
19
25
  ## Usage
20
26
 
@@ -33,8 +33,9 @@ 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); '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; '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); 'upload': Share a file into a chat (uploads to the sender's OneDrive Teams folder, posts a file card); '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) (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
- | `--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. \| [upload] Text content to upload as a file (UTF-8). Provide exactly one of 'content' or 'file_path'. (string) |
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
+ | `--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
+ | `--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`) |
38
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) |
39
40
  | `--channel_type` | No | [send] Type of channel: 'teams_chat' for 1:1 or group chats, 'teams_channel' for team channels. Default: 'teams_chat' (string, one of: teams_chat, teams_channel) |
40
41
  | `--team_id` | No | [send] Required if channel_type is 'teams_channel'. The team ID where the channel belongs. \| [list_channels] Associated team ID from list_teams. \| [list_channel_messages] Host team ID from the selected list_channels result (host_team_id). \| [list_channel_replies] Host team ID from the selected list_channels result (host_team_id). \| [download_attachment] Team ID (GUID) for a channel message; requires channel_id. \| [react] Team ID, for reacting to a channel message (together with channel_id). \| [list_members] ID of the team to list members of. Mutually exclusive with chat_id. \| [delete_message] Team ID, for deleting a channel message (together with channel_id). (string) |
@@ -44,6 +45,8 @@ gsk teams [options]
44
45
  | `--mention_user_ids` | No | [send] List of user IDs (GUIDs) to @mention in the message. Use search_users to find user IDs first. The message content should include {mention_N} placeholders where N is the index (0-based), e.g., '{mention_0} thank you' will @mention the first user in the list. (array) |
45
46
  | `--mention_user_names` | No | [send] Display names for mentioned users, in same order as mention_user_ids. If not provided, will use user IDs as display names. (array) |
46
47
  | `--reply_to_message_id` | No | [send] Optional ID of an existing message to reply to. For team channels: posts this message as a threaded reply under that root message. For chats: renders a quoted block of the referenced message above your text (like the Teams client's Reply action). Message IDs come from microsoft_teams_read_chat / microsoft_teams_list_channel_messages. \| [download_attachment] For a channel reply: the ROOT message ID the reply belongs to. (string) |
48
+ | `--skip_confirmation` | No | [send] If true, skip user confirmation and send immediately. Default is false (require confirmation before sending). \| [api] Skip the user-confirmation step for a write method. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. \| [react] If true, skip user confirmation and apply immediately. Default is false (require confirmation before applying). \| [upload] If true, skip user confirmation and upload immediately. Default is false (require confirmation before uploading). \| [delete_message] If true, skip user confirmation and delete immediately. Default is false (require confirmation before deleting). (boolean, default: `False`) |
49
+ | `--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. \| [api] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [react] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [upload] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. \| [delete_message] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean, default: `False`) |
47
50
  | `--cursor` | No | [list_channels] Opaque next_cursor from the previous page. \| [list_chats] Pagination cursor returned in a previous response's ``next_cursor`` field. Pass it back verbatim to fetch the next page; omit on the first call. \| [read_chat] Pagination cursor from a previous response's ``next_cursor``; omit on the first call. \| [list_channel_messages] Opaque next_cursor from the previous page. \| [list_channel_replies] Opaque next_cursor from the previous page. \| [list_teams] Opaque next_cursor from the previous page. \| [search] Pagination cursor returned in a previous response's ``next_cursor`` field. Pass it back verbatim to fetch the next page; omit on the first call. Stop paging as soon as the returned hits satisfy your need. (string) |
48
51
  | `--topic` | No | [list_chats] Search for chats by topic/name (case-insensitive partial match). Use this to find a specific group chat by its name. Example: 'WorkflowTest' to find a chat with that topic. Filter is applied per-page; if no match on the current page, use ``next_cursor`` to keep searching. \| [create_chat] Topic/name for the group chat. Required for group chats (2+ members), ignored for 1:1 chats. (string) |
49
52
  | `--chat_type` | No | [list_chats] Filter by chat type. 'oneOnOne' for 1:1 chats, 'group' for group chats, 'meeting' for meeting chats, 'all' for all types. Default: 'all' (string, one of: oneOnOne, group, meeting, all) |
@@ -57,8 +60,6 @@ gsk teams [options]
57
60
  | `--graph_version` | No | [api] Graph API version. Default v1.0; 'beta' is an explicit opt-in. (string, one of: v1.0, beta) |
58
61
  | `--method` | No | [api] HTTP method. Default GET. Write methods are held for user confirmation before executing. (string, one of: GET, POST, PATCH, PUT, DELETE) |
59
62
  | `--body` | No | [api] JSON request body for write methods (object or array, passed to Graph verbatim). Not allowed on GET. (string) |
60
- | `--skip_confirmation` | No | [api] Skip the user-confirmation step for a write method. Only honored right after this tool returned pending_confirmation and the user confirmed. Default: false. (boolean) |
61
- | `--auto_skip_confirmation` | No | [api] Internal: set by workflow nodes configured with skip_confirmation=true. Default: false. (boolean) |
62
63
  | `--query` | No | [search] The search query using KQL (Keyword Query Language). **Query Behavior**: • Spaces = AND: 'project meeting' finds messages with BOTH terms • OR operator: 'project OR meeting' finds messages with EITHER term • KQL modifiers: 'from:john', 'hasAttachment:true', 'IsRead:false' • Date filters: prefer the ``since``/``until`` arguments; inline date ops ('sent>=2026-02-01 sent<=2026-03-05', 'sent:2026-02-01..2026-03-05') are also honored — both bounds are enforced • Examples: 'urgent project', 'bug OR issue', 'from:alice budget', 'hasAttachment:true report' \| [search_users] Search query - can be a name, email, or partial match. Example: 'John', 'john@company.com', 'Smith' (string) |
63
64
  | `--unread_only` | No | [search] Set to true to search for unread messages only. Default is false. (boolean) |
64
65
  | `--question` | No | [search] A specific question to answer based on the search results. (string) |
@@ -79,7 +80,7 @@ gsk teams [options]
79
80
 
80
81
  ## Write Confirmation (double-call)
81
82
 
82
- 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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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.
83
84
 
84
85
  ## See Also
85
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
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
 
@@ -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; 'draft': Save an email to the Drafts folder without sending; 'reply': Reply to an existing email; 'reply_draft': Create a reply draft without sending; 'forward': Forward an email to new recipients; 'delete': Delete an email; 'archive': Archive an email; 'move': Move an email to a different folder; '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, 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) |
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. 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, 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) |
@@ -67,6 +67,8 @@ gsk outlook [options]
67
67
  | `--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
68
  | `--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
69
  | `--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`) |
70
+ | `--client_send_id` | No | [send] Optional stable idempotency key. Normally generated automatically for scheduled and interactive sends. (string) |
71
+ | `--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
72
  | `--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
73
  | `--body_type` | No | [draft] Body format: 'html' (default) or 'text'. (string) |
72
74
  | `--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) |
@@ -96,7 +98,7 @@ gsk outlook [options]
96
98
 
97
99
  ## Write Confirmation (double-call)
98
100
 
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` right after a pending response is honored; gated actions without that flag complete ONLY via the double-call.
101
+ 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
102
 
101
103
  ## See Also
102
104