@genspark/cli 1.13.0 → 1.14.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.
- package/README.md +10 -7
- package/dist/client.d.ts +14 -0
- package/dist/client.d.ts.map +1 -1
- package/dist/client.js +62 -2
- package/dist/client.js.map +1 -1
- package/dist/commands/aidrive-operands.d.ts +29 -0
- package/dist/commands/aidrive-operands.d.ts.map +1 -0
- package/dist/commands/aidrive-operands.js +178 -0
- package/dist/commands/aidrive-operands.js.map +1 -0
- package/dist/commands/aidrive-upload.d.ts +149 -0
- package/dist/commands/aidrive-upload.d.ts.map +1 -1
- package/dist/commands/aidrive-upload.js +344 -0
- package/dist/commands/aidrive-upload.js.map +1 -1
- package/dist/commands/design.d.ts +9 -0
- package/dist/commands/design.d.ts.map +1 -1
- package/dist/commands/design.js +12 -2
- package/dist/commands/design.js.map +1 -1
- package/dist/commands/genteam-download.d.ts +34 -0
- package/dist/commands/genteam-download.d.ts.map +1 -0
- package/dist/commands/genteam-download.js +95 -0
- package/dist/commands/genteam-download.js.map +1 -0
- package/dist/config.d.ts +13 -0
- package/dist/config.d.ts.map +1 -1
- package/dist/config.js +18 -0
- package/dist/config.js.map +1 -1
- package/dist/index.d.ts.map +1 -1
- package/dist/index.js +477 -63
- package/dist/index.js.map +1 -1
- package/docs/skills.md +2 -2
- package/package.json +1 -1
- package/skills/gsk-aidrive/SKILL.md +232 -26
- package/skills/gsk-audio-generation/SKILL.md +1 -1
- package/skills/gsk-genteam/SKILL.md +3 -3
- package/skills/gsk-google-drive/SKILL.md +25 -6
- package/skills/gsk-google-sheets/SKILL.md +1 -1
- package/skills/gsk-meeting/SKILL.md +1 -0
- package/skills/gsk-second-brain/SKILL.md +87 -20
- package/skills/gsk-shared/SKILL.md +4 -2
- package/skills/gsk-slack/SKILL.md +10 -8
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: gsk-second-brain
|
|
3
|
-
version: 0.
|
|
4
|
-
description: "What the user's Second Brain is (Notes + Drive, theirs and their team's), where each kind of thing lives,
|
|
3
|
+
version: 0.2.0
|
|
4
|
+
description: "What the user's Second Brain is (Notes + Drive, theirs and their team's), where each kind of thing lives, how to read, write and edit it through `gsk sb-brain`, `gsk sb-git` and `gsk drive`, and how a document card in a GenTeam conversation is read. Read this before any Second Brain task; the per-command references (gsk-sb-brain, gsk-aidrive) hold the flags."
|
|
5
5
|
metadata:
|
|
6
6
|
category: foundation
|
|
7
7
|
requires:
|
|
@@ -61,10 +61,13 @@ Drive has two containers and one view:
|
|
|
61
61
|
|
|
62
62
|
Things you must know about Drive:
|
|
63
63
|
|
|
64
|
-
- **Address = drive + entry.** Every file and folder is identified by the drive it lives in plus its entry id. Drive URLs carry both (`/s/<drive>/<entry>`, `?id=<entry>&link=<drive>`). `gsk drive --url <pasted link>` or `--id <entry> --owner <drive>` resolves them for you.
|
|
64
|
+
- **Address = drive + entry.** Every file and folder is identified by the drive it lives in plus its entry id. Drive URLs carry both (`/s/<drive>/<entry>`, `?id=<entry>&link=<drive>`). `gsk drive ls --url <pasted link>` or `--id <entry> --owner <drive>` resolves them for you.
|
|
65
65
|
- **Shortcuts.** A share card, or a linked entry inside a Team Drive, is a pointer to a source entry in another drive. It has no bytes of its own. Resolve it first — a `LinkNode` row returns `link_workspace_id`; reuse it as `--source` — and read the source. Permission comes from the source, never from the pointer.
|
|
66
|
+
- **Reusable addresses.** `ls` and `find` return `entry_locator`: reuse its workspace/source/path together. Reading a shortcut by that path follows the live source. Its `content_source_id` or `link_workspace_id` instead mounts the source at `/`; do not append the alias's old path to that mount. `rm` and `move` on the alias operate on the shortcut itself. A child path operates inside the source, with fresh authorization.
|
|
67
|
+
- **Only a name is known.** Use `gsk drive find --scope all -q <name>` across My Drive and shared sources; `mine` or `shared` narrows it. A matching name is a candidate, not a unique identity: compare source and parent path. Inspect `coverage`: shared searches have source/result limits and indexed content may be incomplete. Empty results do not prove absence. A source-specific folder search covers its immediate children.
|
|
66
68
|
- **GenTeam channel and DM drives are flat.** No `mkdir`, no directory upload, no moving native entries into subfolders (`GENTEAM_DRIVE_FLAT_LAYOUT`). Members with content-edit access upload at the root; moving, renaming or deleting native files needs conversation admin.
|
|
67
|
-
- **
|
|
69
|
+
- **Shared projections are fixed entries.** They cannot be moved or renamed. Unlinking preserves source bytes but may end sharing to that audience (`share_ended` in the result). A shared source root cannot be removed through its mount. A source name and a projection label are separate: remounting or changing an alias is not proof that the requested source or projection was renamed. Do not unlink/remount to bypass a rename refusal, or explain an unchanged label as refresh delay without evidence. Report the actual operation and result.
|
|
70
|
+
- **Editing permission** comes from the backend verdict for the operation. Content operations through a mount retain its read-only cap; Office access may also recognize an independent edit grant. A card label alone does not establish the effective permission.
|
|
68
71
|
|
|
69
72
|
## 4. Who you are right now
|
|
70
73
|
|
|
@@ -76,7 +79,8 @@ Your reach depends on the runtime you run in. Check which applies before you act
|
|
|
76
79
|
|
|
77
80
|
- `gsk sb-brain` works on any member's turn. Whoever asks, the results are your creator's private notes: relay what the task needs, do not surface unrelated material to other members.
|
|
78
81
|
- `gsk drive` runs **only on your creator's own turn**. This is enforced by the server (`TOOL_OWNER_ONLY`), not by you. On a teammate's turn it will refuse — including plain `ls` and `find`.
|
|
79
|
-
- Files in THIS conversation are yours to read on any member's turn through the conversation's own path: `de channel-files --target current`, then `de attachment-view --ref "<ref>" --target <channel>`.
|
|
82
|
+
- Files in THIS conversation are yours to read on any member's turn through the conversation's own path: `de channel-files --target current`, then `de attachment-view --ref "<ref>" --target <channel>`. That path serves native attachments and **document cards whose share is open to this conversation**: such a row shows `is_link: true` with a `view_command`, and `attachment-view` streams the source document under the card's own ref. A **folder card** (a shared Second Brain folder) lists its contents with `de attachment-list --ref "<ref>" --target <channel>` — the children of the folder, or of a sub-folder with `--entry <folder id>`; `--after <entry id>` turns the page — and each listed row spells the command that opens it: a child file reads with `de attachment-view --ref "<ref>" --entry <child id> --target <channel>`, a sub-folder lists with `attachment-list --entry`. It refuses a project card and a card whose share is not open here (404, the detail says which); a card whose owner turned downloads off is refused with `ATTACHMENT_DOWNLOAD_DISABLED` — say so, never guess the content.
|
|
83
|
+
- **A document card** — a Second Brain link someone posted; readers see a card — reads through `de attachment-view` (above) on any member's turn when its share is open to the conversation. When that path refuses it, or your runtime has no `de`, read it through the Drive on your creator's turn in three steps: take the card's link from the message text (`/second-brain/s/<drive>/<entry>` or `/aidrive/s/...`); resolve it with `gsk drive ls --url <link>` (or list this conversation's drive with `ls --workspace shared_drive --source <its source_id>` and pass the card row's `link_workspace_id` as `--source`); then `get_readable_url` the resolved entry and read the bytes yourself; `download` the same bytes to a local path when the format needs a parser on disk (Office, PDF). Reading here is downloading: a share whose owner turned downloads off cannot be read either way — say so. A card whose target is a project (the row's `link_target_kind`) is read with `gsk read-project <link_target_id>`. A folder card is listed with `de attachment-list` (above) on any member's turn while its share is open to the conversation; traversing it through the Drive stays the creator-turn alternative. A DM card remains a reference requiring the reader's own source grant. Never substitute the creator's private access for a teammate's request or guess content from a card's name.
|
|
80
84
|
- When `gsk drive` refuses, say plainly that reading or writing the Drive from this conversation needs the creator to ask. Do not fall back to scanning chat for a substitute, and do not write a copy somewhere else.
|
|
81
85
|
|
|
82
86
|
## 5. Reading
|
|
@@ -87,15 +91,61 @@ Decide where the thing lives, then use that door once:
|
|
|
87
91
|
|---|---|
|
|
88
92
|
| Something they knew, wrote, received or decided | `gsk sb-brain grep -q <short keyword>` across sources, or `-s <source>` when they named one. Then `read -s <hit.source> --repo_id <hit.repo_id> -p <hit.path>` the best hit. `grep` is a fixed string, case-insensitive; not a regex |
|
|
89
93
|
| Themselves, their preferences, open loops | `read -s memo -p System/memory/Memory.md` first |
|
|
90
|
-
| A
|
|
91
|
-
| A
|
|
92
|
-
|
|
|
93
|
-
|
|
|
94
|
+
| A known Drive file | `gsk drive read --id <entry>` or `read --path <path>`; preserve a selected `--source`. Discover only an unknown filename with `find --scope all -q <name>` |
|
|
95
|
+
| A topic inside a selected Drive folder | `gsk drive search --query <topic> --query_scope subtree` with the selected `--id`, `--path` or `--source` |
|
|
96
|
+
| A Drive folder's contents | `gsk drive tree` with the selected address; existing overviews help navigation |
|
|
97
|
+
| An unknown Team Drive or shared source | `ls --workspace shared_drive` or `ls --workspace shared_with_me`, then reuse its `source_id` with `read`/`search`/`tree` |
|
|
98
|
+
| A pasted Drive link or share card | `gsk drive read --url <link>` for files, `gsk drive tree --url <link>` for folders; the resolver follows live shortcuts |
|
|
99
|
+
| A document card in a GenTeam conversation | `de attachment-view --ref "<the card row's attachment_ref>" --target <channel>` on any member's turn while its share is open to the conversation; when that refuses, the three steps in §4 on your creator's turn: the link from the message text, `gsk drive ls --url <link>`, then `get_readable_url` (or `download` for Office and PDF) |
|
|
100
|
+
| A folder card in a GenTeam conversation | `de attachment-list --ref "<the card row's attachment_ref>" --target <channel>` lists its children (`--entry <folder id>` for a sub-folder, `--after <entry id>` for the next page); `de attachment-view --ref "<the card ref>" --entry <child id> --target <channel>` reads one child — both on any member's turn while its share is open to the conversation |
|
|
94
101
|
| An attachment in the current conversation | The conversation's own attachment path, not the Drive |
|
|
95
102
|
| Meaning-based search across their Drive documents | `gsk doc-search query -q <question>` when it is available to you. Today it covers My Drive only |
|
|
96
103
|
|
|
97
104
|
Always `read` or fetch a file before quoting or acting on it. If nothing relevant comes back, try one variant (shorter prefix, nickname, the user's other language), then say what you covered. Conflicting sources: surface both with dates.
|
|
98
105
|
|
|
106
|
+
For a topical question, stop collecting once original evidence covers the
|
|
107
|
+
requested facts. Read another file or range to close a named gap or resolve a
|
|
108
|
+
conflict, not just for completeness. A request for a full-document summary still
|
|
109
|
+
requires every range. Do not expand the source root again after locating the
|
|
110
|
+
relevant files unless the evidence is insufficient.
|
|
111
|
+
|
|
112
|
+
Batch `read --ids` accepts at most **6 files**, sharing a **16 KB text budget**
|
|
113
|
+
(with response metadata bounded separately); `char_limit` is not a promise of
|
|
114
|
+
24 KB per file or per batch. Use small batches and follow each file's own
|
|
115
|
+
`next_read`. Pass these limits and source identifiers to delegated readers too.
|
|
116
|
+
|
|
117
|
+
Choose the next evidence-gathering or editing step once and execute it. Revisit
|
|
118
|
+
the plan only when a result, constraint or user request changes it. Reuse facts,
|
|
119
|
+
file identifiers and guides already available in this conversation.
|
|
120
|
+
For an overview of a large folder, track which file groups support each topic
|
|
121
|
+
and fill uncovered groups before claiming complete coverage. Reading selected
|
|
122
|
+
concept summaries alone is sampling, not reading every file in the folder.
|
|
123
|
+
|
|
124
|
+
For Drive, follow `../gsk-aidrive/SKILL.md` for read ranges, search cursors and
|
|
125
|
+
coverage. Existing overview helps choose vocabulary and a starting folder; it
|
|
126
|
+
is not source evidence and must not exclude relevant sibling folders. Missing
|
|
127
|
+
or stale overview does not block search. Request up to 6 useful overviews with `--ids` per call; missing/stale summaries enqueue asynchronously. Continue search/read without polling. Use summaries to plan the next search/read, then read original text for exact facts or uncovered details. Folder summaries can use names and child summaries; they do not prove every descendant was read.
|
|
128
|
+
`coverage=complete`/`source_complete` describe the index; `contains_full_document`
|
|
129
|
+
describes this response. A full summary needs all ranges from offset 0: follow
|
|
130
|
+
the returned `next_read` fields as flags to `gsk drive read` until exhausted and
|
|
131
|
+
`source_complete` is true. On older servers, use `--id` with `next_offset` and
|
|
132
|
+
`source_version`; do not combine multi-file `--ids` with a shared offset.
|
|
133
|
+
Use `--char_limit`/`--limit`/`--byte_limit` to bound output; do not truncate JSON
|
|
134
|
+
with `head` and lose coverage or continuation. Context query results are directly
|
|
135
|
+
in `data`; `get_readable_url` uses `session_state.aidrive_result.readable_url`.
|
|
136
|
+
For `index_pending`, reuse `retry_read` as flags to `gsk drive read` once; it waits
|
|
137
|
+
within a bounded server budget, so do not add a shell sleep. Use `gsk --refresh`
|
|
138
|
+
for that retry the first time you see `wait_seconds`, so a cached CLI schema
|
|
139
|
+
recognizes the new flag. Older servers return
|
|
140
|
+
only `retry_after_seconds`: wait that interval and retry once. If still unavailable
|
|
141
|
+
or incomplete, use `get_readable_url --id <entry>` or `download` and an appropriate
|
|
142
|
+
parser, stating the actual coverage. Use `--id`, not restore's `--entry_id`.
|
|
143
|
+
If a new action/flag is rejected, retry once with `gsk --refresh`; an older server
|
|
144
|
+
may still need the byte-read fallback. Active Office content uses `wo-peer` (§7).
|
|
145
|
+
Permission refusals are not a reason to try another read lane.
|
|
146
|
+
Cite `[title](returned url)` verbatim for Drive evidence. Never prefix that
|
|
147
|
+
URL with `memo:`, which opens a vault note instead of the Drive source.
|
|
148
|
+
|
|
99
149
|
## 6. Writing
|
|
100
150
|
|
|
101
151
|
Decide WHERE before you write, in this order:
|
|
@@ -107,10 +157,10 @@ Decide WHERE before you write, in this order:
|
|
|
107
157
|
Commands:
|
|
108
158
|
|
|
109
159
|
- Notes: `gsk sb-git commit` — full file content, `expected_parent` set.
|
|
110
|
-
- My Drive: `gsk drive upload --upload_path <path> --
|
|
160
|
+
- New My Drive files: `gsk drive upload --local_file <file> --upload_path <path> --on-conflict error`. Never keep the `/My Drive` spelling in the path; that literal would create a `My Drive/` folder. If the path exists, resolve whether the user meant that existing entry (§7) or a genuinely new file with a distinct name. Do not retry with overwrite or let automatic renaming turn an update into a duplicate.
|
|
111
161
|
- Team Drive or a shared source: add `--workspace shared_drive|shared_with_me --source <source_id>`. The source drive owns the bytes and quota. GenTeam channel drives take files at the root only.
|
|
112
|
-
-
|
|
113
|
-
-
|
|
162
|
+
- `upload` replies carry the new entry's `url` and `item.id`; return that URL directly. A `read` result's `url` is also ready to cite. Do not run `gsk me`, `find`, or reconstruct a link when the result already supplies its URL. Only on an older runtime whose reply lacks it, recover the id with `find -q <name>` in the destination.
|
|
163
|
+
- Only when a URL is missing, the `<drive>` part of a link is the user's own id for My Drive — reuse a known owner; otherwise `gsk me` returns it as `cogen_id`. For a Team Drive or shared source it is the `drive_id` on that source's row (the part of `source_id` before the colon).
|
|
114
164
|
|
|
115
165
|
**The link you hand back.** For anything in Drive, the only link for people is the entry's share link:
|
|
116
166
|
|
|
@@ -120,15 +170,29 @@ Commands:
|
|
|
120
170
|
|
|
121
171
|
When a `gsk drive` reply already carries one, hand that `url` back as it is: `share`, `access` and `link` replies print `Link: ...`, and shortcut rows in `ls`/`find` show one. It may start with `/aidrive/s/` instead of `/second-brain/s/` — the same landing for an account whose Second Brain drive surface is not rolled out yet; both forms open, so never rewrite one into the other. Build the link yourself only when no reply gave you one (a file you just uploaded, a `find` hit), from the `<drive>` rule above and the row's `id`.
|
|
122
172
|
|
|
173
|
+
A reply's `Open folder` / `browse_url` opens the containing folder by the same entry-link scheme; use it only when the user wants the folder. For an uploaded or read file, prefer its `Link` / `url`. Only the caller's Drive home uses a home-page URL. Do not reconstruct folder links with `?path=` or file links with `#p_fid=`.
|
|
174
|
+
|
|
123
175
|
Never hand out a `get_readable_url` (a signed download that opens nothing), a `/aidrive/files/...` folder page, or an editor route (`/second-brain/doc?id=...` is an in-app destination, not a share link). For Notes, hand back the `memo:` link.
|
|
124
176
|
|
|
125
|
-
**
|
|
177
|
+
**Handing a file to a GenTeam conversation.** Choose one delivery for each result, within the current turn's permissions:
|
|
178
|
+
|
|
179
|
+
- For a new local artifact or an explicitly requested export/copy: attach it once (`de message-send --target <channel> --attachment <local-path>`). It lands in the conversation's drive as a native file and everyone there can open it. This works on any member's turn for content you are authorized to read; it never bypasses creator-only Drive access.
|
|
180
|
+
- On your creator's turn, for a Drive entry that should stay one document: `gsk drive share --id <entry> --to channel:<server_id>:<channel_id>` opens it to the members and posts its card (`--post_card false` opens it without a message). `<server_id>` is the workspace id (`gsk genteam channels` lists it beside the slug) and `<channel_id>` the conversation id. A DM is a person, not a channel: the tool refuses `channel:` for a DM — share to that person by email instead.
|
|
181
|
+
|
|
182
|
+
After a successful share posts its card, delivery is complete: do not also attach the downloaded original or generated local file, upload it into the conversation, or send a second link-only message. A short completion summary can refer to the posted card. If card posting fails, report that separately from any successful access grant; use the returned share link once, without attaching a copy or repeating the grant. When editing an entry already shared here, update it in place and acknowledge the change; do not re-share or re-attach it by default. Only an explicit request for an additional export/copy calls for another attachment.
|
|
183
|
+
|
|
184
|
+
Never change an entry's `general_access` (`link`, `org`) to hand out a link. The share link opens for whoever already has access; widening access is the user's decision, never a delivery step.
|
|
185
|
+
|
|
186
|
+
**A new Office file.** A doc / Word / DOCX, a sheet / Excel / XLSX, or a deck the user wants as a file is a Drive file, not a project deliverable. Author the real file first (the `docx` / `xlsx` skill when your runtime packs them; a deck is built as web slides and exported with `gsk slide export <deck> -f pptx -o <deck>.pptx`; a PDF is a paginated web document published and exported with `gsk doc export <name> -f pdf -o <name>.pdf`), then `gsk drive upload --local_file <file> --upload_path /<name>.<ext> --on-conflict error` into the folder the write router above picked — the My Drive root when nothing anchors or names a place. Hand back the entry's link: the reply's `url`, or build it from the reply's `item.id`; when sending it to GenTeam, follow the single-delivery rule above. This first upload creates a new entry; it is never the edit path for an existing document. Never publish it to the project as a render card or a deliverable instead, and never write a note in its place; if the upload fails, say why.
|
|
126
187
|
|
|
127
188
|
## 7. Editing an existing document
|
|
128
189
|
|
|
129
|
-
- **
|
|
130
|
-
- **A
|
|
131
|
-
- **
|
|
190
|
+
- **Every existing Office document** (`docx`, `xlsx`, `pptx`, in My Drive or shared): edit it through the `wo-peer` collaboration room on its source id. Never download, edit locally and overwrite it. An empty presence probe, a closed editor or `wo-peer close` does not make file replacement safe: room state can persist after users leave. Use the room for text, images, formatting, sheets and slides. If it is unavailable, return the proposed change as text and say the document was not updated.
|
|
191
|
+
- **A shared Office document:** when using Drive, resolve the source first; in GenTeam use the card route below. `get_readable_url` returns `collaboration.file_id` and `collaboration.link_workspace_id`; use `wo-peer open <file_id> --context <context>` (`--link-workspace-id` is an alias). This joins the native file's room and preserves the permission context for saving. A shortcut ID is not a room ID; an editor token is not proof that an edit was acknowledged or persisted.
|
|
192
|
+
- **In a GenTeam conversation** the room lane is `wo-peer` as well, on PATH when your creator is enabled for it (`gk_sb_collab_peer`): use `de channel-files` to get the card row's `link_target_id` as `<f_id>` (else the `<entry>` segment of its share link) and its `link_workspace_id`, then run `wo-peer open <f_id> --context <link_workspace_id>`. This card route does not require a creator-only `gsk drive` call. `wo-peer probe <f_id> --context <link_workspace_id>` is optional presence information, never a choice between room editing and overwrite. Omit `--context` only when the row shows none; `~/.gsk/skills/wo-peer/SKILL.md` has the GenTeam section. Two lanes, and the backend picks per call: on your creator's turn, any document your creator may edit; on a member's turn, only a card shared *editable* to this conversation — the room then acts as that member, with the authority they have in the browser. Every `wo-peer call` is re-checked for the current turn: `TOOL_OWNER_ONLY` means neither lane admits this turn (a teammate's turn on a document not shared editable here) — tell them, do not retry; "open under another person's authority" means run `open` again for this turn. Without `wo-peer` on PATH, existing Office files cannot be edited from here: say so and hand the change back as text in your reply.
|
|
193
|
+
- **A Markdown file in Drive:** there is no live co-editing through `wo-peer`. Do not apply an edit by replacing the whole file with an upload; return the proposed text and explain that it has not been applied. This does not change Notes writes through `sb-git` with `expected_parent`.
|
|
194
|
+
- **Replacing a standalone media or archive asset** (an image, audio/video file or ZIP): when the user explicitly asks to replace that exact asset, resolve its native source entry, record its id, and reuse that source's workspace/source/path with `gsk drive upload --local_file <replacement> --upload_path <resolved native path> --on-conflict overwrite`. This replaces the asset's bytes, subject to the existing write permissions and creator-turn gate. Never upload against a projection/alias path. Verify the returned `item.id` matches the original source id before claiming an in-place update; report a refusal or unexpected new id without retrying as a renamed copy. This lane excludes Office, Markdown, PDF and other documents; an image inside a document is edited through the document's room.
|
|
195
|
+
- **Anything you cannot edit:** say why — this turn is not authorized, view-only grant, no room in this runtime, no editor for this type. Never create a new copy in place of the update.
|
|
132
196
|
|
|
133
197
|
## 8. When to open the brain
|
|
134
198
|
|
|
@@ -140,13 +204,14 @@ Most requests are self-contained; do not open the brain for them. Open it on one
|
|
|
140
204
|
|
|
141
205
|
Then one round: one focused `grep` (or one `find` for files) and one `read` of the best hit; answer only what it supports. Widen only when the user asks or pushes back on a negative, and keep the scope they gave ("search all my meetings" stays in `-s meeting`). A calculation, a rewrite of pasted text, or a public-web question never needs the brain. Your runtime's own prompt may ask for more on its surface — the Second Brain chat reads the user's `Memory.md` before answering anything about them — and it wins there.
|
|
142
206
|
|
|
143
|
-
## 9. Known limits, as of 2026-09-
|
|
207
|
+
## 9. Known limits, as of 2026-09-18
|
|
144
208
|
|
|
145
|
-
- Markdown has no live co-editing;
|
|
209
|
+
- Drive Markdown has no live co-editing; whole-file upload can lose concurrent changes, so return proposed edits as text (§7).
|
|
146
210
|
- A PDF is produced by exporting a paginated web document (`gsk doc export -f pdf`) and uploading it; PDF content cannot be edited in place from an agent. `download_file --file_url` can import one.
|
|
147
211
|
- `upload` replies carry `url` and `item.id` since 2026-09-15; on an older runtime recover the id with `find`.
|
|
148
|
-
- `doc-search` indexes My Drive only.
|
|
149
|
-
-
|
|
212
|
+
- `doc-search` indexes My Drive only. It is switched on for internal accounts only.
|
|
213
|
+
- `gsk drive read` returns persisted indexed text, not the live Office room. Pending or partial extraction is not complete evidence; use the reading guidance in §5. Byte downloads remain subject to the source owner's download policy.
|
|
214
|
+
- In GenTeam, `gsk drive` is creator-turn only, DM roots are discoverable without granting access to referenced sources, and `wo-peer` is on PATH only when your creator is enabled for it (`gk_sb_collab_peer`) — without it, Office documents cannot be changed from there. Since 2026-09-18 a member's turn may change a card shared editable to the conversation through the room (the room acts as that member); everything else in the room stays creator-turn only. A document shared into a DM grants the person, not the conversation; the recipient finds it under `shared_with_me`.
|
|
150
215
|
|
|
151
216
|
Each line disappears as the platform closes it. If a limit below is gone, this skill is stale — say so.
|
|
152
217
|
|
|
@@ -156,3 +221,5 @@ Each line disappears as the platform closes it. If a limit below is gone, this s
|
|
|
156
221
|
- 2026-09-08: an upload over an open shared docx failed; the agent read it as read-only and dropped a v0.5 copy in the root. Rule: open editor means the room; never a copy.
|
|
157
222
|
- 2026-09-15: a diary asked to be saved as a doc came back as a render_doc web page in the chat's project, with nothing in My Drive. Rule: a new Office file is a Drive upload, never a project deliverable.
|
|
158
223
|
- 2026-09-11: a GenTeam agent asked to edit a shared document wrote a new file instead. Rule: resolve the shortcut, check who you are, explain a refusal.
|
|
224
|
+
- 2026-09-17: asked what the document cards in a channel said, a GenTeam agent pointed `de attachment-view` at them and reported "share link, not a file". Since 2026-09-18 that path follows a card whose share is open to the conversation and names the reason when it refuses (not open here, a folder or project, downloads off). Rule: relay the refusal as given; fall back to the Drive read (§4) only where your runtime has `gsk`.
|
|
225
|
+
- 2026-09-17: asked for "a link I can open", an agent set the new file's `general_access` to `link`, then `org`. Rule: hand back the share link; never widen access to deliver it.
|
|
@@ -213,13 +213,15 @@ The `gsk drive upload` command supports streaming local files directly to AI Dri
|
|
|
213
213
|
# Upload a local file to AI Drive (streaming, supports 100MB+ files)
|
|
214
214
|
gsk drive upload --local_file ./report.pdf --upload_path /docs/report.pdf
|
|
215
215
|
gsk drive upload --local_file ./photo.png # defaults to /photo.png
|
|
216
|
-
gsk drive upload --local_file ./doc.pdf --upload_path /docs/doc.pdf --
|
|
216
|
+
gsk drive upload --local_file ./doc.pdf --upload_path /docs/doc.pdf --overwrite true # edit in place: same id, same link
|
|
217
|
+
gsk drive upload --local_file ./report.pdf --upload_path /docs/report.pdf --to ann@example.com # upload and share; reply carries the link
|
|
217
218
|
```
|
|
218
219
|
|
|
219
220
|
| Flag | Description |
|
|
220
221
|
|------|-------------|
|
|
221
222
|
| `--local_file <path>` | Local file path to upload (streaming, no size limit) |
|
|
222
|
-
| `--
|
|
223
|
+
| `--overwrite true` | Replace the existing file at the destination path in place; the file keeps its id and share link (`--override` is the older spelling) |
|
|
224
|
+
| `--to`, `--general_access` | Share the uploaded file right away (My Drive); the reply's `url` opens for those people |
|
|
223
225
|
|
|
224
226
|
## Connectors (integrations)
|
|
225
227
|
|
|
@@ -1,8 +1,8 @@
|
|
|
1
1
|
---
|
|
2
2
|
name: gsk-slack
|
|
3
3
|
version: 1.0.0
|
|
4
|
-
description: 'Slack messaging operations. Actions: send, search,
|
|
5
|
-
upload, update, delete, permalink.'
|
|
4
|
+
description: 'Slack messaging operations. Actions: send, search, search_files, read,
|
|
5
|
+
download_file, lookup, react, upload, update, delete, permalink.'
|
|
6
6
|
metadata:
|
|
7
7
|
category: general
|
|
8
8
|
requires:
|
|
@@ -17,7 +17,7 @@ metadata:
|
|
|
17
17
|
|
|
18
18
|
> **Note:** a unified `gsk connector` flow is rolling out (see `../gsk-connector/SKILL.md`: `gsk connector tools <id>` / `gsk connector call <id> -t <tool>`) and may not be enabled for every account yet. THIS command remains fully supported — use it directly, and it stays the fallback whenever `gsk connector` is unavailable.
|
|
19
19
|
|
|
20
|
-
Slack messaging operations. Actions: send, search, read, lookup, react, upload, update, delete, permalink.
|
|
20
|
+
Slack messaging operations. Actions: send, search, search_files, read, download_file, lookup, react, upload, update, delete, permalink.
|
|
21
21
|
|
|
22
22
|
## Usage
|
|
23
23
|
|
|
@@ -29,20 +29,22 @@ gsk slack [options]
|
|
|
29
29
|
|
|
30
30
|
| Flag | Required | Description |
|
|
31
31
|
|------|----------|-------------|
|
|
32
|
-
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'search': Search messages by keyword; 'read': Read recent message history of a channel (or one thread), including each message's emoji reactions; 'lookup': Look up users, channels, or groups; 'react': Emoji-react to a message (or remove your reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'invite': Invite workspace members into a channel. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'upload': Upload a file into a channel, group, or DM. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update': Edit one of the user's own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete': Delete one of the user's own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'permalink': Get the permanent link for a message (string, one of: send, search, read, lookup, react, invite, upload, update, delete, permalink) |
|
|
32
|
+
| `<action>` (positional) | Yes | Action to perform. 'send': Send a message to a channel or user. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'search': Search messages by keyword; 'search_files': Search files shared in Slack by keyword; each hit's id feeds download_file; 'read': Read recent message history of a channel (or one thread), including each message's emoji reactions and uploaded files; 'download_file': Download one file shared in Slack by its id; returns a file URL; 'lookup': Look up users, channels, or groups; 'react': Emoji-react to a message (or remove your reaction). Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'invite': Invite workspace members into a channel. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'upload': Upload a file into a channel, group, or DM. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'update': Edit one of the user's own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'delete': Delete one of the user's own messages. Confirmation-gated: on a CLI with client-side confirmation the command runs as a single call after the [y/N] prompt (or --yes).; 'permalink': Get the permanent link for a message (string, one of: send, search, search_files, read, download_file, lookup, react, invite, upload, update, delete, permalink) |
|
|
33
33
|
| `--message` | No | [send] The message content to send. Supports Slack markdown formatting. To @mention someone, embed '<@USER_ID>' (e.g. '<@U01234567>') in the text — a plain '@Name' renders as literal text and notifies nobody. User IDs come from the lookup action. 'content' is accepted as an alias for this parameter. (string) |
|
|
34
34
|
| `--recipient` | No | [send] Optional recipient: 'self' (default), channel ID (e.g., 'C01234567'), or user ID (e.g., 'U01234567'). If not specified, sends to yourself. (string) |
|
|
35
35
|
| `--title` | No | [send] Optional title for the message. If provided, creates a rich formatted message with a header. \| [upload] Optional title shown on the Slack file card. Defaults to the file name. (string) |
|
|
36
36
|
| `--fields` | No | [send] Optional array of field objects with 'title' and 'value' keys to create a structured message layout. (array) |
|
|
37
37
|
| `--thread_ts` | No | [send] Optional thread timestamp to reply in a thread. \| [read] Timestamp ('ts') of a thread's parent message. When set, returns that thread's replies instead of the channel timeline. \| [upload] Optional thread timestamp — share the file as a reply in this thread instead of the conversation root. (string) |
|
|
38
|
-
| `--
|
|
39
|
-
| `--
|
|
40
|
-
| `--
|
|
38
|
+
| `--workspace` | No | Optional. Which linked Slack workspace to act in: its team id (e.g. 'T0123ABCD') or its workspace name. Omit to use the default (most recently connected) workspace. The lookup action with lookup_type='workspaces' lists the choices. (string) |
|
|
39
|
+
| `--query` | No | [search] The search query. You can use modifiers like 'in:#channel', 'from:@user', 'has:link', 'before:yyyy-mm-dd'. \| [search_files] Search terms; Slack modifiers such as 'in:#channel', 'from:@user', 'before:yyyy-mm-dd' are honored. (string) |
|
|
40
|
+
| `--count` | No | [search] The maximum number of messages to return. Default is 100. \| [search_files] Maximum files to return (default 20, max 100). (integer) |
|
|
41
|
+
| `--sort` | No | [search] Sort order of results. 'score' for relevance or 'timestamp' for time. Default is 'score'. \| [search_files] 'score' (relevance, default) or 'timestamp' (newest first). (string) |
|
|
41
42
|
| `--question` | No | [search] A specific question to answer based on the search results. (string) |
|
|
42
43
|
| `--channel` | No | [read] Conversation ID (channel 'C…', private group 'G…', or DM 'D…') or a channel name (e.g. '#general' or 'general'). IDs come from the lookup action. \| [react] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [invite] Conversation ID of the channel to invite into (public 'C…' or private group 'G…'). \| [upload] Target conversation ID (channel 'C…', private group 'G…', or DM 'D…') the file is shared into. \| [update] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [delete] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). \| [permalink] Conversation ID containing the message (channel 'C…', private group 'G…', or DM 'D…'). (string) |
|
|
43
44
|
| `--limit` | No | [read] Maximum messages to return (default 20, max 100). \| [lookup] Maximum number of results to return. Default: 50 (integer) |
|
|
44
45
|
| `--cursor` | No | [read] Pagination cursor from a previous call's next_cursor to fetch older messages. (string) |
|
|
45
|
-
| `--
|
|
46
|
+
| `--file_id` | No | [download_file] Slack file id (starts with 'F'), from a message's files list (read action) or a search_files hit. (string) |
|
|
47
|
+
| `--lookup_type` | No | [lookup] What to look up: 'users' for team members, 'channels' for channels/conversations, 'all' for both, 'workspaces' for the Slack workspaces linked to this account (their team_id feeds the 'workspace' parameter). (string, one of: users, channels, all, workspaces) |
|
|
46
48
|
| `--search_query` | No | [lookup] Optional search query to filter results by name. Case-insensitive partial match on name, display name, or real name. (string) |
|
|
47
49
|
| `--include_bots` | No | [lookup] Whether to include bot users in results. Default: false (boolean) |
|
|
48
50
|
| `--timestamp` | No | [react] The message's 'ts' value (e.g. '1752600000.000100'). \| [update] The message's 'ts' value (e.g. '1752600000.000100'). Must be a message the connected user authored. \| [delete] The message's 'ts' value (e.g. '1752600000.000100'). Must be a message the connected user authored. \| [permalink] The message's 'ts' value (e.g. '1752600000.000100'). (string) |
|