@qvac/skills 0.1.10 → 0.1.12

package/hash.js

@@ -1,2 +1,2 @@
 // Autogenerated by scripts/build.mjs from skills/. Do not edit.
-export const SKILLS_HASH = 'b9e592a3199188a6'
+export const SKILLS_HASH = 'b97470e51b8846e3'

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@qvac/skills",
-  "version": "0.1.10",
+  "version": "0.1.12",
   "description": "Skills for the QV.AC app — the SKILL.md tree plus a content-addressed bundle of it.",
   "type": "module",
   "main": "index.js",

package/skills/excel/SKILL.md

@@ -1,127 +1,162 @@
 ---
 name: excel
-description: Create, edit, or read Excel spreadsheets (.xlsx) with openpyxl — deliver workbooks as chat attachments, or read an attached one to summarize it or answer questions in the chat. Computes values in Python; can also write live formulas and embed images. Opens in Numbers and Google Sheets too.
+description: Create, edit, or read Excel spreadsheets (.xlsx) — deliver workbooks as chat attachments, or read an attached one to summarize it or answer questions in the chat. Writes values and live formulas and can embed images. Opens in Numbers and Google Sheets too.
 aliases: [xlsx, spreadsheet, workbook]
-tools: [exec(python)]
-platform: [darwin, linux, win32]
-# Routing tuned on Qwen3.5-4B for QVAC-24106 ("@excel embed this image into a spreadsheet" after a
-# generate_image turn). The bullet list sent 13/14 runs to edit.md, and 6/14 ended with no image in
-# a workbook, most by asking the user to attach one. As a request -> file table: 5/5 to create.md and
-# 5/5 embedded the image; "add a fourth row" to a workbook built in the chat still loads edit.md, 3/3.
-metadata:
-  {
-    "openclaw":
-      {
-        "setup":
-          {
-            "summary": "Runs openpyxl in the in-process Python runtime, from packages that ship with the app. The first use waits for the runtime to start."
-          }
-      }
-  }
+tools: [xlsx]
+platform: [darwin, linux, win32, ios, android]
 ---
 
 # Excel
 
-Build or edit an `.xlsx` workbook by running openpyxl through the `exec` tool with
-`language: "python"`. Declare the workbook in `outputs` and it comes back as a chat
-attachment the user can save. To answer *from* a workbook instead of building one,
-run a read call — no `outputs` — and reply in the chat.
+Every workbook job is one or two `xlsx` tool calls. A call with `ops` saves a
+new file named `output` and attaches it to the chat; a call without `ops`
+changes nothing and returns what the workbook holds.
+
+## Pick the Call
+
+| The user wants                                                                        | The calls                                                           |
+| ------------------------------------------------------------------------------------- | ------------------------------------------------------------------- |
+| "make a spreadsheet of …", "embed this image into a spreadsheet" — no `.xlsx` here yet | one call: `create` + `ops` + `output`                                |
+| "change B2 to 125", "add this image to my budget.xlsx" — an `.xlsx` is here           | one call: `attachmentId` + `ops` + `output`                          |
+| "add a total row", "fix the wrong prices" — the change depends on what is in it        | read (`attachmentId` alone), then one edit call                     |
+| "what is the total in this sheet?", "summarize this workbook"                         | read (`attachmentId` alone), then reply in the chat — no second call |
+| "summarize this workbook into a new file"                                             | read, then one `create` call written from what the read returned    |
+
+A workbook already in this chat is never rebuilt with `create` — that throws
+away everything the user has. Its `attachmentId` is in the tool result that
+produced it, or on the user's `[Attached file …]` line:
+
+```
+[Attached file "budget.xlsx" (application/vnd.openxmlformats-officedocument.spreadsheetml.sheet) — attachmentId: 4f9c2ab1]
+```
+
+Copy the id verbatim. Never make one up.
+
+**An image this chat generated is already attached.** A `generate_image` result
+in any earlier turn is the image "this image" means, and its `attachmentId` is
+the one to use. Never ask the user to attach an image the conversation already
+has.
+
+## A New Workbook
+
+```json
+{
+  "create": { "sheets": ["Sales"] },
+  "ops": [
+    { "op": "setCells", "sheet": "Sales", "cells": {
+      "A1": { "value": "Quarter", "bold": true },
+      "B1": { "value": "Units", "bold": true },
+      "C1": { "value": "Price", "bold": true },
+      "D1": { "value": "Revenue", "bold": true }
+    } },
+    { "op": "appendRows", "sheet": "Sales", "rows": [
+      ["Q1", 120, 9.5, "=B2*C2"],
+      ["Q2", 135, 9.5, "=B3*C3"],
+      ["Q3", 150, 10, "=B4*C4"],
+      ["Total", "=SUM(B2:B4)", null, "=SUM(D2:D4)"]
+    ] },
+    { "op": "setColumnWidth", "sheet": "Sales", "column": "A", "width": 14 }
+  ],
+  "output": "sales.xlsx"
+}
+```
+
+## Values and Formulas
+
+Text that starts with `=` is a formula. Nothing computes it here — the
+spreadsheet app does, the moment the user opens the file. So:
+
+- For a total, an average, or anything derived from other cells, write the
+  formula (`"=SUM(D2:D4)"`). It stays right when the user edits the numbers.
+- For numbers the user gave you or that you know, write the number.
+- A formula cell shows no value in the chat preview. Say so in the reply: "the
+  totals are live formulas, so they appear when you open the file."
+
+## Reading a Workbook
+
+```json
+{ "attachmentId": "4f9c2ab1" }
+```
+
+It returns every sheet — its name and used range, its rows of values, and a map
+of the formula in each formula cell. A formula's value is the result the file
+last saved, or `null` if nothing computed it yet — a `null` total is not missing
+data: compute it from the rows the formula names. Dates come back as ISO text.
+You cannot write a summary or a fix in the same call that reads, because the
+words are fixed before the workbook is opened. Read, then write from what came
+back. If the result says it was cut short, answer from what came back and say
+the answer covers the workbook up to that point.
+
+## Editing a Workbook
+
+```json
+{
+  "attachmentId": "4f9c2ab1",
+  "ops": [
+    { "op": "setCells", "sheet": "Sales", "cells": { "B3": 125, "A7": "Note", "D7": "=SUM(D3:D5)" } },
+    { "op": "appendRows", "sheet": "Sales", "rows": [["Q4", 80, 10.5, "=B8*C8"]] }
+  ],
+  "output": "budget_revised.xlsx"
+}
+```
+
+A `sheet` is its name or its index from 0. Cells are A1 references and rows
+count from 1, as in Excel.
+
+| The change                 | The op                                                                                      |
+| -------------------------- | ------------------------------------------------------------------------------------------- |
+| Set cells                  | `{ "op": "setCells", "sheet": "Sales", "cells": { "B3": 125, "C3": "=B3*2" } }`              |
+| Clear a cell               | `{ "op": "setCells", "sheet": "Sales", "cells": { "B3": null } }`                            |
+| Format a cell              | `{ "op": "setCells", "sheet": "Sales", "cells": { "F4": { "value": 0.3, "format": "0.0%", "bold": true, "fill": "FFF2CC" } } }` |
+| A date                     | `{ "op": "setCells", "sheet": "Sales", "cells": { "G4": { "date": "2026-06-30" } } }`        |
+| Add rows at the end        | `{ "op": "appendRows", "sheet": "Sales", "rows": [["Q4", 80, 10.5]] }`                        |
+| Insert rows                | `{ "op": "insertRows", "sheet": "Sales", "at": 3, "rows": [["Q1b", 60, 9.5]] }`              |
+| Delete rows                | `{ "op": "deleteRows", "sheet": "Sales", "at": 5, "count": 2 }`                               |
+| Delete columns             | `{ "op": "deleteColumns", "sheet": "Sales", "column": "E", "count": 1 }`                      |
+| Column width               | `{ "op": "setColumnWidth", "sheet": "Sales", "column": "A", "width": 20 }`                    |
+| Add a sheet                | `{ "op": "addSheet", "name": "Notes" }`                                                       |
+| Rename a sheet             | `{ "op": "renameSheet", "sheet": "Notes", "name": "Commentary" }`                             |
+| Delete a sheet             | `{ "op": "deleteSheet", "sheet": "Scratch" }`                                                 |
+| Add a picture              | `{ "op": "addImage", "sheet": "Sales", "image": { "attachmentId": "9be07c12" }, "cell": "F2" }` |
+
+Renaming a sheet rewrites every formula that names it. `insertRows` and
+`deleteRows` are refused on a sheet with formulas, merges or tables that would
+not move with the rows — the error names which; use `setCells` and
+`appendRows` there instead.
+
+Name the output after the workbook you opened: `budget.xlsx` →
+`budget_revised.xlsx`. Never the input's own name. A macro-enabled `.xlsm` is
+saved as `.xlsx`: add `{ "op": "removeMacros" }` and tell the user the macros
+were not kept.
+
+## Images
+
+- An image this chat generated: `"image": { "attachmentId": "<id from the generate_image result>" }`.
+- An image the user attached to their latest message: `"image": {}` — an
+  uploaded image shows no id, and the empty form picks it up.
+- An image behind a URL cannot be downloaded. Say so, and ask the user to attach
+  it or offer `generate_image`.
 
-## Load the Recipe File First
-
-This file contains no Python. The working recipes live in three reference files —
-load the one for the job with the `skill` tool BEFORE writing any Python, then
-copy its recipe and change the content:
-
-Each load is a real `skill` tool call — printing the call as JSON or text in
-your reply loads nothing.
-
-Pick the file by whether an `.xlsx` is already in this chat:
-
-| The request                                                                         | Load                                            |
-| ----------------------------------------------------------------------------------- | ----------------------------------------------- |
-| "make a spreadsheet of …", "embed this image into a spreadsheet" — no `.xlsx` yet    | `references/create.md`                          |
-| "add a row", "change B2", "add this image to my budget.xlsx" — an `.xlsx` is here    | `references/edit.md`                            |
-| "what is the total in this sheet?", "summarize this workbook" — the answer is a reply | `references/read.md`                            |
-| "summarize this workbook into a new file"                                           | `references/read.md` first, then create or edit |
-
-Load it with the `skill` tool: `name: "excel"` and that `file`.
-
-**An image this chat generated is already attached.** A `generate_image` result in
-any earlier turn is the image "this image" means, and its `attachmentId` stages it.
-Never ask the user to attach an image the conversation already has.
+## Rules for Every Job
 
-Never write the Python from memory. The recipes carry required patterns (the
-fill-in template, staging rules, guard asserts) that fail in non-obvious ways
-when improvised; loading the file is one cheap read-only call.
+**You build it, not the user.** The workbook exists only when an `xlsx` call
+with `ops` returns its attachment. Never answer with a markdown table instead
+of the file the user asked for, and never tell the user to run anything.
 
-## When to Use
+**Success = stop.** When the result lists the attachment, reply with one line —
+the file name and the sheets and rows it holds — and call nothing else.
 
-- The user asks for a spreadsheet, workbook, `.xlsx`, Excel, or Numbers/Sheets-openable file.
-- The user attaches a spreadsheet and wants cells changed, rows/columns/sheets added or removed, or data extracted from it.
-- The user attaches a spreadsheet and asks what it holds — a summary, a question
-  answered, or values pulled out into the chat.
-- The user wants a workbook that embeds an image — one generated in this chat or
-  one they uploaded. Both recipe files carry it.
+**Errors name the fix.** A failed call returns a message that says what exists
+— the sheet names, the used range. Correct that one op and call again. Never
+repeat an identical call.
 
 ## When NOT to Use
 
-- The user wants a table in the chat built from content already in the
-  conversation — no workbook involved — write a markdown table. Answering or
-  summarizing from an attached workbook **is** this skill: load
-  `references/read.md`.
-- The user wants a comma-separated text file only — write the `.csv` directly with Python's `csv` module (`.csv` is an allowed output), no openpyxl needed.
-
-## Values vs Formulas — decide before writing
-
-This runtime has no spreadsheet engine: openpyxl writes a formula as text and
-computes nothing. A formula cell has **no value** until the user opens the file
-in a spreadsheet app and it recalculates. So pick the mode from what the user
-wants:
+- A table in the chat built from what is already in the conversation, with no
+  workbook involved — write a markdown table.
 
-- **They want numbers** (a report, totals, statistics, cleaned data): compute in
-  Python and write **literal values**. This is the default.
-- **They want a live spreadsheet** (totals that update when they edit cells):
-  write formulas — and say so in the reply, because the formula cells look empty
-  in the chat preview: "the total is a live formula, so it shows up once you
-  open the file in Excel, Numbers, or Sheets."
-- Never write a formula and then read it back expecting a number, and never
-  "verify" a formula by reloading the file — there is nothing to verify.
-
-Writing both is fine: literal values everywhere, plus a `=SUM(...)` total row if
-the user wants it to stay live.
-
-## Rules for Every Job
+## What This Cannot Do
 
-**You build it, not the user.** Deliver the workbook, never the recipe. Do NOT
-print the python source in chat, do NOT tell the user to install openpyxl, run
-a script, or open a terminal — they have no terminal in this chat and the code
-would not run there. The workbook exists only if an `exec` call with `outputs`
-succeeds and returns the attachment.
-
-**Success = stop.** When `exitCode` is `0` and `attachments` lists the `.xlsx`,
-the workbook is done — do not call `exec` again, not to "confirm", not to
-"improve", not to reload the file to "check the formulas". Exactly one
-successful *build* call per request (a no-`outputs` read that precedes a build
-delivers nothing and is not one of them, but it belongs before the build, never
-after). Reply with a single line: file name + the sheet/row summary from stdout.
-If the result has `missingOutputs`, read stderr first: an `AssertionError` there
-means a guard stopped the save on purpose and its message names what to fix;
-only when stderr is clean check the `save()` name matches the declared output
-and rerun once.
-
-**Failures are fixed in the code, not around it.** If a run fails, fix the
-Python against the loaded reference file's recipes and Errors table and call
-`exec` again. If two consecutive calls fail with the same error, re-read the
-traceback line-by-line before a third. An error is never a fault in openpyxl or
-the runtime — keep `packages: ["openpyxl==3.1.5"]`, never wrap source in
-`python -c` or shell, never "debug" with `os.listdir` or no-op scripts.
-
-**The runtime is sealed.** No shell (`ls`, `cat` raise `SyntaxError` — the
-`command` is Python source) and no network (`requests` and `urllib` fail — a
-URL to a spreadsheet cannot be downloaded; ask the user to attach the file).
-The working directory starts empty on every call: a file from an earlier call
-is gone unless staged again via `inputs`, and a file you write but do not
-declare in `outputs` is discarded.
-
-**Never overwrite a staged input.** Edits always save under a new output name.
+Say so instead of faking it: charts in a workbook, pivot tables, editing
+conditional formatting or data validation (both are kept as they are), and
+legacy `.xls` files.

package/skills/gmail/SKILL.md

@@ -18,13 +18,16 @@ metadata:
             "credentialKey": "gmail_access_token",
             "description": "Read, search, send, and manage Gmail messages and labels",
             "steps": [
-              "Click Connect and approve access in the browser. Approving grants access to your Gmail only.",
+              "Click Connect and approve access in the browser. Approving grants access to read, compose, and send mail in your Gmail account, and to change labels and move messages to the trash. It does not permanently delete mail.",
               "Each Google skill is connected separately, with its own app and its own approval."
             ],
             "configSteps": [
-              "[Open Google Cloud Console](https://console.cloud.google.com/flows/enableapi?apiid=gmail.googleapis.com) to enable the Gmail API",
-              "[Open OAuth clients](https://console.cloud.google.com/auth/clients) to create an OAuth client — choose \"Desktop app\" as the type",
-              "[Open OAuth audience](https://console.cloud.google.com/auth/audience) and add your Google account as a test user"
+              "[Create a project](https://console.cloud.google.com/projectcreate) if you do not have one. Select that project in the console and stay in it for every step below.",
+              "[Enable the Gmail API](https://console.cloud.google.com/flows/enableapi?apiid=gmail.googleapis.com) on that project. Reading, sending, labels, and trash all use the Gmail API.",
+              "[Open Branding](https://console.cloud.google.com/auth/branding). If setup has not been started, click Get started: app name, user support email, audience External, a contact email, agree to the user data policy, then Create.",
+              "[Open Data Access](https://console.cloud.google.com/auth/scopes), choose Add or remove scopes, add https://www.googleapis.com/auth/gmail.modify, and save.",
+              "[Open Audience](https://console.cloud.google.com/auth/audience). While Publishing status is Testing, click Add users and add the Google account that will click Connect.",
+              "[Open Clients](https://console.cloud.google.com/auth/clients), click Create Client, and choose Desktop app. Copy the Client ID and Client Secret into the fields below."
             ],
             "fields": [
               {

package/skills/google-calendar/SKILL.md

@@ -18,13 +18,16 @@ metadata:
             "credentialKey": "google_calendar_access_token",
             "description": "List, create, update, and delete Google Calendar events",
             "steps": [
-              "Click Connect and approve access in the browser. Approving grants access to your calendars only.",
+              "Click Connect and approve access in the browser. Approving grants access to all of the calendars you can access. This app uses that access to list, create, change, and delete events, check free/busy, and add Google Meet links.",
               "Each Google skill is connected separately, with its own app and its own approval."
             ],
             "configSteps": [
-              "[Open Google Cloud Console](https://console.cloud.google.com/flows/enableapi?apiid=calendar-json.googleapis.com) to enable the Google Calendar API",
-              "[Open OAuth clients](https://console.cloud.google.com/auth/clients) to create an OAuth client — choose \"Desktop app\" as the type",
-              "[Open OAuth audience](https://console.cloud.google.com/auth/audience) and add your Google account as a test user"
+              "[Create a project](https://console.cloud.google.com/projectcreate) if you do not have one. Select that project in the console and stay in it for every step below.",
+              "[Enable the Google Calendar API](https://console.cloud.google.com/flows/enableapi?apiid=calendar-json.googleapis.com) on that project. Events, free/busy, and Meet links use the Calendar API.",
+              "[Open Branding](https://console.cloud.google.com/auth/branding). If setup has not been started, click Get started: app name, user support email, audience External, a contact email, agree to the user data policy, then Create.",
+              "[Open Data Access](https://console.cloud.google.com/auth/scopes), choose Add or remove scopes, add https://www.googleapis.com/auth/calendar, and save.",
+              "[Open Audience](https://console.cloud.google.com/auth/audience). While Publishing status is Testing, click Add users and add the Google account that will click Connect.",
+              "[Open Clients](https://console.cloud.google.com/auth/clients), click Create Client, and choose Desktop app. Copy the Client ID and Client Secret into the fields below."
             ],
             "fields": [
               {

package/skills/google-docs/SKILL.md

@@ -17,13 +17,16 @@ metadata:
             "credentialKey": "google_docs_access_token",
             "description": "Create, read, and edit Google Docs documents",
             "steps": [
-              "Click Connect and approve access in the browser. Approving grants access to your documents and Drive files only.",
+              "Click Connect and approve access in the browser. Approving grants access to all of your Google Drive files. This app uses that access to create, read, and edit Google Docs, find a document, and move it to the trash.",
               "Each Google skill is connected separately, with its own app and its own approval."
             ],
             "configSteps": [
-              "[Open Google Cloud Console](https://console.cloud.google.com/flows/enableapi?apiid=docs.googleapis.com,drive.googleapis.com) to enable the Google Docs API",
-              "[Open OAuth clients](https://console.cloud.google.com/auth/clients) to create an OAuth client — choose \"Desktop app\" as the type",
-              "[Open OAuth audience](https://console.cloud.google.com/auth/audience) and add your Google account as a test user"
+              "[Create a project](https://console.cloud.google.com/projectcreate) if you do not have one. Select that project in the console and stay in it for every step below.",
+              "[Enable the Google Docs API and the Drive API](https://console.cloud.google.com/flows/enableapi?apiid=docs.googleapis.com,drive.googleapis.com) on that project. Document text uses the Docs API. Finding a document and moving it to the trash use the Drive API.",
+              "[Open Branding](https://console.cloud.google.com/auth/branding). If setup has not been started, click Get started: app name, user support email, audience External, a contact email, agree to the user data policy, then Create.",
+              "[Open Data Access](https://console.cloud.google.com/auth/scopes), choose Add or remove scopes, add https://www.googleapis.com/auth/drive, and save.",
+              "[Open Audience](https://console.cloud.google.com/auth/audience). While Publishing status is Testing, click Add users and add the Google account that will click Connect.",
+              "[Open Clients](https://console.cloud.google.com/auth/clients), click Create Client, and choose Desktop app. Copy the Client ID and Client Secret into the fields below."
             ],
             "fields": [
               {
@@ -43,7 +46,6 @@ metadata:
               "tokenUrl": "https://oauth2.googleapis.com/token",
               "tokenAuth": "secret-in-body",
               "scopes": [
-                "https://www.googleapis.com/auth/documents",
                 "https://www.googleapis.com/auth/drive"
               ],
               "extraAuthParams": {

package/skills/google-drive/SKILL.md

@@ -17,13 +17,16 @@ metadata:
             "credentialKey": "google_drive_access_token",
             "description": "Search, list, and manage Google Drive files and folders",
             "steps": [
-              "Click Connect and approve access in the browser. Approving grants access to your Drive files only.",
+              "Click Connect and approve access in the browser. Approving grants access to all of your Google Drive files. This app uses that access to search, list, export, rename, and move files and folders to the trash.",
               "Each Google skill is connected separately, with its own app and its own approval."
             ],
             "configSteps": [
-              "[Open Google Cloud Console](https://console.cloud.google.com/flows/enableapi?apiid=drive.googleapis.com) to enable the Google Drive API",
-              "[Open OAuth clients](https://console.cloud.google.com/auth/clients) to create an OAuth client — choose \"Desktop app\" as the type",
-              "[Open OAuth audience](https://console.cloud.google.com/auth/audience) and add your Google account as a test user"
+              "[Create a project](https://console.cloud.google.com/projectcreate) if you do not have one. Select that project in the console and stay in it for every step below.",
+              "[Enable the Google Drive API](https://console.cloud.google.com/flows/enableapi?apiid=drive.googleapis.com) on that project. Search, export, rename, and trash all use the Drive API.",
+              "[Open Branding](https://console.cloud.google.com/auth/branding). If setup has not been started, click Get started: app name, user support email, audience External, a contact email, agree to the user data policy, then Create.",
+              "[Open Data Access](https://console.cloud.google.com/auth/scopes), choose Add or remove scopes, add https://www.googleapis.com/auth/drive, and save.",
+              "[Open Audience](https://console.cloud.google.com/auth/audience). While Publishing status is Testing, click Add users and add the Google account that will click Connect.",
+              "[Open Clients](https://console.cloud.google.com/auth/clients), click Create Client, and choose Desktop app. Copy the Client ID and Client Secret into the fields below."
             ],
             "fields": [
               {

package/skills/google-sheets/SKILL.md

@@ -18,13 +18,16 @@ metadata:
             "credentialKey": "google_sheets_access_token",
             "description": "Create, read, and update Google Sheets spreadsheets",
             "steps": [
-              "Click Connect and approve access in the browser. Approving grants access to your spreadsheets and Drive files only.",
+              "Click Connect and approve access in the browser. Approving grants access to all of your Google Drive files. This app uses that access to create, read, and edit Google Sheets, find a spreadsheet, and move it to the trash.",
               "Each Google skill is connected separately, with its own app and its own approval."
             ],
             "configSteps": [
-              "[Open Google Cloud Console](https://console.cloud.google.com/flows/enableapi?apiid=sheets.googleapis.com,drive.googleapis.com) to enable the Google Sheets API",
-              "[Open OAuth clients](https://console.cloud.google.com/auth/clients) to create an OAuth client — choose \"Desktop app\" as the type",
-              "[Open OAuth audience](https://console.cloud.google.com/auth/audience) and add your Google account as a test user"
+              "[Create a project](https://console.cloud.google.com/projectcreate) if you do not have one. Select that project in the console and stay in it for every step below.",
+              "[Enable the Google Sheets API and the Drive API](https://console.cloud.google.com/flows/enableapi?apiid=sheets.googleapis.com,drive.googleapis.com) on that project. Cell values use the Sheets API. Finding a spreadsheet and moving it to the trash use the Drive API.",
+              "[Open Branding](https://console.cloud.google.com/auth/branding). If setup has not been started, click Get started: app name, user support email, audience External, a contact email, agree to the user data policy, then Create.",
+              "[Open Data Access](https://console.cloud.google.com/auth/scopes), choose Add or remove scopes, add https://www.googleapis.com/auth/drive, and save.",
+              "[Open Audience](https://console.cloud.google.com/auth/audience). While Publishing status is Testing, click Add users and add the Google account that will click Connect.",
+              "[Open Clients](https://console.cloud.google.com/auth/clients), click Create Client, and choose Desktop app. Copy the Client ID and Client Secret into the fields below."
             ],
             "fields": [
               {
@@ -44,7 +47,6 @@ metadata:
               "tokenUrl": "https://oauth2.googleapis.com/token",
               "tokenAuth": "secret-in-body",
               "scopes": [
-                "https://www.googleapis.com/auth/spreadsheets",
                 "https://www.googleapis.com/auth/drive"
               ],
               "extraAuthParams": {

package/skills/music-generation/SKILL.md

@@ -42,6 +42,21 @@ prompt says.
 Set `duration` when the user asks for a specific length ("30 seconds", "a
 two-minute track"); otherwise leave it unset and let the model choose.
 
+## Sheet music
+
+`generate_music` can also write the finished track out as sheet music, saved as a
+score attachment, with `sheetMusic: true`. Offer it before generating whenever
+the request sounds like someone will play the result (a melody, a piano or guitar
+piece, a practice backing) or when they mention notes, chords or a score.
+
+Sheet music never changes the track. Generate what the user asked for: their
+duration, their instrumentation, their genre. Dense or long material makes a
+crowded score, so say so when the result comes back rather than quietly writing
+something sparser than they asked for. When the choice is genuinely open, a
+sparse 30 to 60 second piece gives a score a person can actually read.
+
+To write out audio that already exists, that is `transcribe_music`, not this.
+
 ## Parameters
 
 - `prompt` (required) - describe the genre, instruments, mood, and vocal