agentleFS
raffaelefarinaroraffaelefarinaro/ciaobot/skills/gws-shared/SKILL.md

gws-shared

Skill11 starsChanged 10 days agoApache-2.0View on GitHub

gws CLI: Shared patterns for authentication, global flags, and output formatting.

7 other projects use a version of this, 5 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use gws-calendar-agenda, gws-calendar-insert and 5 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 7 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run every Google API call through the ciao CLI — never bare gws:

    line 16
  2. Very specific:

    Use the chat's GWS_PROFILE unless the user asks otherwise.

    line 22
  3. Very specific:

    Prefer --dry-run for destructive operations

    line 56
  4. Very specific:

    Use --sanitize for PII/content safety screening

    line 57

“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

gws — Shared Reference

Installation

Install gws from Settings → Overview → Google account (or see the Ciaobot README). The binary must be on $PATH.

Authentication (Ciaobot)

Run every Google API call through the ciao CLI — never bare gws:

ciao gws "$GWS_PROFILE" <service> <subcommand> [flags]

Use the chat's GWS_PROFILE unless the user asks otherwise. ciao gws routes credentials and execs gws. Do not source it and do not repeat the gws binary after the profile name.

OAuth setup: Settings → Overview → Google account. Config dirs: secrets/gws-personal/ (personal), secrets/gws/ (work).

Global Flags

FlagDescription
--format <FORMAT>Output format: json (default), table, yaml, csv
--dry-runValidate locally without calling the API
--sanitize <TEMPLATE>Screen responses through Model Armor

CLI Syntax

ciao gws "$GWS_PROFILE" <service> <resource> [sub-resource] <method> [flags]

Method Flags

FlagDescription
--params '{"key": "val"}'URL/query parameters
--json '{"key": "val"}'Request body
-o, --output <PATH>Save binary responses to file
--upload <PATH>Upload file content (multipart)
--page-allAuto-paginate (NDJSON output)
--page-limit <N>Max pages when using --page-all (default: 10)
--page-delay <MS>Delay between pages in ms (default: 100)

Security Rules

  • Never output secrets (API keys, tokens) directly
  • Always confirm with user before executing write/delete commands
  • Prefer --dry-run for destructive operations
  • Use --sanitize for PII/content safety screening

Shell Tips

  • zsh ! expansion: Sheet ranges like Sheet1!A1 contain ! which zsh interprets as history expansion. Use double quotes with escaped inner quotes instead of single quotes:
    # WRONG (zsh will mangle the !)
    ciao gws "$GWS_PROFILE" sheets +read --spreadsheet ID --range 'Sheet1!A1:D10'
    
    # CORRECT
    ciao gws "$GWS_PROFILE" sheets +read --spreadsheet ID --range "Sheet1!A1:D10"
  • JSON with double quotes: Wrap --params and --json values in single quotes so the shell does not interpret the inner double quotes:
    ciao gws "$GWS_PROFILE" drive files list --params '{"pageSize": 5}'

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.