@acedatacloud/skills 2026.504.5 → 2026.505.0

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@acedatacloud/skills",
-  "version": "2026.504.5",
+  "version": "2026.505.0",
   "description": "Agent Skills for AceDataCloud AI services — music, image, video generation, LLM chat, web search. Compatible with Claude Code, GitHub Copilot, Gemini CLI, OpenAI Codex, and 30+ AI coding agents.",
   "keywords": [
     "agent-skills",

package/skills/google-calendar/SKILL.md

@@ -15,7 +15,7 @@ allowed_tools: [Bash]
 license: Apache-2.0
 metadata:
   author: acedatacloud
-  version: "1.1"
+  version: "1.2"
 ---
 
 Drive Google Calendar via `curl + jq`. The user's OAuth bearer token
@@ -43,6 +43,72 @@ user to confirm. When attendees are involved, also confirm whether
 they want Google to email the attendees — that's controlled by the
 `sendUpdates` query parameter.
 
+## Optional: Google Workspace CLI (`gws`) for agenda + create
+
+[`gws`](https://github.com/googleworkspace/cli) is Google's official CLI
+(not officially supported — community-maintained on the `googleworkspace`
+org). It dynamically builds its command surface from Google's Discovery
+Document, exits non-zero on API errors, and ships hand-crafted helper
+commands (prefixed `+`) for time-aware workflows.
+
+**Use `gws` for two specific cases:**
+
+- `+agenda` reads the user's account timezone from `Settings.timezone`
+  (cached for 24 h) and renders today's events in that zone, so you don't
+  have to fetch the timezone yourself before formatting times.
+- `+insert` shapes the create-event JSON for you (attendees, sendUpdates,
+  reminders) so a one-line invocation produces a well-formed request.
+
+For everything else (events.list / patch / move / delete, freebusy,
+calendarList) the curl recipes below are equivalent and shorter — stay
+on those.
+
+### Install
+
+```sh
+npm install -g @googleworkspace/cli   # or: brew install googleworkspace-cli
+# Pre-built binaries also at https://github.com/googleworkspace/cli/releases
+gws --version
+```
+
+### Auth
+
+`gws` reads its OAuth bearer token from the `GOOGLE_WORKSPACE_CLI_TOKEN`
+environment variable. The Calendar token used in this skill is in
+`$GOOGLE_CALENDAR_TOKEN`, so re-export it once at the top of every shell
+block that calls `gws`:
+
+```sh
+export GOOGLE_WORKSPACE_CLI_TOKEN="$GOOGLE_CALENDAR_TOKEN"
+```
+
+### Agenda + create
+
+```sh
+# Today on the primary calendar, in the account's own timezone
+gws calendar +agenda
+
+# Today / week, with explicit overrides
+gws calendar +agenda --today --tz America/New_York
+gws calendar +agenda --range week
+
+# Create an event (auto-shapes attendees + sendUpdates JSON)
+gws calendar +insert --calendar primary \
+  --json '{
+    "summary":"Standup",
+    "start":{"dateTime":"2026-05-06T10:00:00-04:00"},
+    "end":  {"dateTime":"2026-05-06T10:30:00-04:00"},
+    "attendees":[{"email":"alice@example.com"}]
+  }' \
+  --params '{"sendUpdates":"all"}'
+```
+
+Both helpers exit non-zero with a structured JSON error on stderr if
+Google rejects the request — surface that verbatim. `+insert` against
+attendees requires the broader `calendar` scope; on `403
+insufficientPermissions` ask the user to re-install with read+write
+checked.
+
 ## Recipes
 
 ### Verify auth + discover calendars (always run first)

package/skills/google-drive/SKILL.md

@@ -14,7 +14,7 @@ allowed_tools: [Bash]
 license: Apache-2.0
 metadata:
   author: acedatacloud
-  version: "1.1"
+  version: "1.2"
 ---
 
 Drive Google Drive via `curl + jq`. The user's OAuth bearer token is
@@ -39,6 +39,61 @@ name + path you're about to touch.
 **Always start with `/about?fields=user`** to confirm the connection
 works AND learn which Google account you're operating against.
 
+## Optional: Google Workspace CLI (`gws`) for uploads
+
+[`gws`](https://github.com/googleworkspace/cli) is Google's official CLI
+(not officially supported — community-maintained on the `googleworkspace`
+org). It dynamically builds its command surface from Google's Discovery
+Document, exits non-zero on API errors, supports `--page-all`
+auto-pagination, and ships a `+upload` helper that wraps the multipart
+upload protocol.
+
+**Use `gws` for uploads.** A Drive multipart upload requires a
+hand-formatted `multipart/related` body with a JSON metadata part and a
+binary file part separated by a boundary string — easy to get wrong from
+curl. `gws drive +upload` does it correctly. **For everything else**
+(list, search, get, export, rename, move, trash, delete) the curl recipes
+below are equivalent and shorter — stay on those.
+
+### Install
+
+```sh
+npm install -g @googleworkspace/cli   # or: brew install googleworkspace-cli
+# Pre-built binaries also at https://github.com/googleworkspace/cli/releases
+gws --version
+```
+
+### Auth
+
+`gws` reads its OAuth bearer token from the `GOOGLE_WORKSPACE_CLI_TOKEN`
+environment variable. The Drive token used in this skill is in
+`$GOOGLE_DRIVE_TOKEN`, so re-export it once at the top of every shell
+block that calls `gws`:
+
+```sh
+export GOOGLE_WORKSPACE_CLI_TOKEN="$GOOGLE_DRIVE_TOKEN"
+```
+
+### Upload
+
+```sh
+# Simple upload to My Drive (auto-detects MIME type, sets the file name
+# from --name; falls back to the local filename if --name is omitted)
+gws drive +upload ./report.pdf --name "Q1 Report"
+
+# Upload into a specific folder, or with explicit metadata, via the
+# generic Discovery method + --upload (multipart wire format handled
+# for you)
+gws drive files create \
+  --json '{"name":"report.pdf","parents":["FOLDER_ID"],"description":"Q1"}' \
+  --upload ./report.pdf
+```
+
+Both exit non-zero with a structured JSON error on stderr if Google
+rejects the request — surface that verbatim. Uploads need the broader
+`drive` scope; on `403 insufficientPermissions` ask the user to
+re-install the connector with read+write checked.
+
 ## Recipes
 
 ### Verify auth (always run first)

package/skills/google-gmail/SKILL.md

@@ -16,7 +16,7 @@ allowed_tools: [Bash]
 license: Apache-2.0
 metadata:
   author: acedatacloud
-  version: "1.1"
+  version: "1.2"
 ---
 
 Drive Gmail via `curl + jq`. The user's OAuth bearer token is in
@@ -45,6 +45,76 @@ AND learn which Gmail account you're operating against. Mailbox payloads
 can be huge — fetch metadata first, only `format=full` when the user
 actually wants the body of a specific message.
 
+## Optional: Google Workspace CLI (`gws`) for outbound mail
+
+[`gws`](https://github.com/googleworkspace/cli) is Google's official CLI
+(not officially supported — community-maintained on the `googleworkspace`
+org). It dynamically builds its command surface from Google's Discovery
+Document, exits non-zero on API errors, and ships hand-crafted helper
+commands (prefixed `+`) that handle the message-encoding boilerplate.
+
+**Use `gws` for sending mail.** The Gmail REST API requires every
+outbound message to be a fully-formed RFC 822 message, base64url-encoded
+into a `raw` field, with reply / forward threading carried in
+`In-Reply-To` / `References` / `threadId`. The `+send / +reply /
++reply-all / +forward` helpers do all of that for you. **For everything
+else** (read, search, labels, attachments) `gws` and curl are equivalent,
+so the curl recipes below are usually shorter — stay on those.
+
+### Install
+
+```sh
+npm install -g @googleworkspace/cli   # or: brew install googleworkspace-cli
+# Pre-built binaries also at https://github.com/googleworkspace/cli/releases
+gws --version
+```
+
+### Auth
+
+`gws` reads its OAuth bearer token from the `GOOGLE_WORKSPACE_CLI_TOKEN`
+environment variable. The Gmail token used in this skill is in
+`$GOOGLE_GMAIL_TOKEN`, so re-export it once at the top of every shell
+block that calls `gws`:
+
+```sh
+export GOOGLE_WORKSPACE_CLI_TOKEN="$GOOGLE_GMAIL_TOKEN"
+```
+
+You can confirm the active account with `gws gmail users getProfile
+--params '{"userId":"me"}'`.
+
+### Send / reply / forward
+
+```sh
+# New message
+gws gmail +send \
+  --to alice@example.com \
+  --cc team@example.com \
+  --subject "Q1 status" \
+  --body "Numbers attached."
+
+# Reply (handles threadId, In-Reply-To, References automatically;
+# To is the original sender, Subject gets the "Re: " prefix)
+gws gmail +reply --message-id MSG_ID --body "Thanks — looks good."
+
+# Reply-all
+gws gmail +reply-all --message-id MSG_ID --body "+1"
+
+# Forward to new recipients (preserves the original message body
+# inline; original headers are summarised in the forward block)
+gws gmail +forward --message-id MSG_ID --to bob@example.com
+```
+
+Each helper exits with a non-zero status and a JSON error on stderr if
+Google rejects the request — surface that error verbatim. `+send` /
+`+reply` need the `gmail.send` scope; if the user only granted
+`gmail.readonly` you'll see `403 insufficientPermissions` and should ask
+them to re-install the connector with the send box checked.
+
+All the read / list / search / label / attachment recipes below are
+intentionally **not** rewritten to `gws` — a one-line `curl ... | jq` is
+shorter and easier to compose with shell pipelines.
+
 ## Recipes
 
 ### Verify auth (always run first)

package/skills/tencentcloud-cls-alarm/scripts/cls_alarm.py

@@ -17,8 +17,7 @@ Quick examples:
 
 Environment:
   Reads TENCENTCLOUD_SECRET_ID, TENCENTCLOUD_SECRET_KEY, TENCENTCLOUD_REGION
-  from the sandbox environment (auto-injected by aichat2 from the user's
-  AceDataCloud BYOC connection; or set manually in `.env`).
+  from the environment.
 """
 
 from __future__ import annotations