agentsclimarketplace

GWS ops

Skill asong56/skills/08-extend/GWS-ops

Use GWS for Google Workspace CLI operations (Drive/Sheets/Docs/Slides). Trigger when a user asks to check, list, search, export, read, or update Google files via GWS; when a Google URL/ID needs parsing; when auth/account selection or safe re...From its SKILL.md

Install
npx -y skills add asong56/skills --skill GWS-ops

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.9 KB, 710 tokens by cl100k_base, as published. Nobody here has run it

GWS Ops

Overview

Standardize GWS usage: verify auth, resolve IDs from URLs, default to read-only checks, then run the minimum command needed.

Quick start

  • Confirm GWS is available: gog --version
  • List accounts and pick one explicitly if more than one: gog auth list
  • Resolve URL to ID with python3 scripts/gog_parse_url.py "<url-or-id>"
  • Run a read-only metadata command first (Drive/Sheets/Docs/Slides)

Workflow decision tree

  1. Identify target type: sheet | doc | slide | file | folder | id | unknown via scripts/gog_parse_url.py.
  2. Choose the smallest read-only command to confirm access:
    • Sheets: gog sheets metadata <spreadsheetId>
    • Docs: gog docs info <docId>
    • Slides: gog slides info <presentationId>
    • Drive file/folder: gog drive get <fileId> or gog drive permissions <fileId>
  3. Only proceed to write operations (update/append/move/share/delete) after explicit user confirmation.

Core tasks

Auth and account selection

  • Show stored accounts: gog auth list
  • Show auth configuration: gog auth status
  • Add/authorize account: gog auth add <email>
  • Always use --account <email> when multiple accounts exist.

Resolve IDs from URLs

  • Parse a URL or ID:
    • python3 scripts/gog_parse_url.py "<url-or-id>"
  • If output type is unknown, ask for a direct ID or a different URL.

Drive (files/folders)

  • List root or a folder: gog drive ls
  • Search by query: gog drive search "<query>"
  • Get metadata: gog drive get <fileId>
  • Download/export: gog drive download <fileId>
  • Permissions check: gog drive permissions <fileId>

Sheets

  • Metadata: gog sheets metadata <spreadsheetId>
  • Read values: gog sheets get <spreadsheetId> <range>
  • Export: gog sheets export <spreadsheetId>
  • Write operations (update/append/clear/format): require explicit confirmation and exact range.

Docs

  • Metadata: gog docs info <docId>
  • Read text: gog docs cat <docId>
  • Export: gog docs export <docId>

Slides

  • Metadata: gog slides info <presentationId>
  • Export: gog slides export <presentationId>

Output modes

  • Use --plain for stable TSV output.
  • Use --json when a caller wants structured output.
  • Use --no-input in non-interactive flows to avoid hanging.

Error handling

  • 403/404: verify account (gog auth list), check permissions (gog drive permissions <fileId>), and confirm the ID.
  • If access fails, request the user to share the file with the selected account or provide the correct account.

Resources

  • See ${CLAUDE_SKILL_DIR}/references/GWS-cheatsheet.md for a compact command list.
  • Use scripts/gog_parse_url.py to normalize URLs into IDs before running commands.

What ships with it: 3 files

2.9 KB alongside SKILL.md, 1 of them executable

agents/

references/

scripts/

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.