Gw api
Call ANY Google API method via the generic Discovery invoker — services with no curated command group (Drive, Slides, People, Chat, Keep, Meet, Classroom, Apps Script, Admin SDK, ...) and uncovered methods on curated ones. Includes schema introspection, dry-run validation, NDJSON pagination, and a destructive-method guard. TRIGGERS: "google api", "gw api", "api call", "discovery", "drive api", "slides", "people api", "contacts", "chat api", "admin sdk", "apps script", "classroom", "any google service", "api schema"From its SKILL.md
npx -y skills add Elnora-AI/elnora-google-workspace --skill gw-apiAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 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
4.6 KB, as published. Nobody here has run it
Generic Google API Invoker
Invocation
CLI="python3 ${CLAUDE_PLUGIN_ROOT}/cli/gw.py"
When to Use
- Prefer the curated groups (
gmail,calendar,sheets,docs,tasks,forms) for anything they cover — they have task-shaped flags and validated response shapes. - Use
gw apifor everything else: services without a curated group, or curated services' methods the groups don't expose. - SERVICE is an alias (
gw api listshows all 18) or theapi:versionescape hatch for any Google API, e.g.admin:directory_v1.
Workflow: schema → dry-run → call
Always resolve the method shape before calling:
# 1. Find the service and browse its surface
$CLI api list --compact
$CLI api describe gmail --compact # top-level resources
$CLI api describe gmail users.messages --compact # methods on a resource
# 2. Inspect the method: params, required scopes, request/response schema
$CLI schema gmail.users.messages.list --compact
# 3. Validate the call without executing (offline, no auth needed)
$CLI api call gmail users.messages.list --params '{"userId":"me","maxResults":5}' --dry-run
# 4. Execute
$CLI api call gmail users.messages.list --params '{"userId":"me","maxResults":5}' --compact
--dry-run prints {service, method, httpMethod, uri_template, params, body, required_scopes, destructive} and catches unknown/missing-required params before any network call.
Commands
$CLI api call SERVICE METHOD_PATH [--params '{json}'] [--json '{body}' | --json-file PATH] \
[--dry-run] [--page-all] [--page-limit 10] [--page-delay-ms 100] [--confirm] \
[--no-cache] [--account NAME] --compact
$CLI api list --compact
$CLI api describe SERVICE [RESOURCE.PATH] [--full] --compact
$CLI schema SERVICE.RESOURCE.METHOD [--depth 3] --compact
METHOD_PATHis the dotted resource path from the Discovery doc (users.messages.list).--params= method (query/path) parameters;--json/--json-file= request body.
Pagination
--page-all follows nextPageToken and emits NDJSON — one JSON object per page on stdout. Bound it with --page-limit (default 10 pages):
$CLI api call drive files.list --params '{"pageSize":100,"q":"trashed=false"}' --page-all --page-limit 5
Without --page-all you get a single call with the normal JSON envelope.
Destructive-Method Guard
Methods ending in delete/clear/remove/trash/stop/revoke (or with HTTP DELETE) refuse to run without --confirm (error code CONFIRM_REQUIRED).
Get explicit user confirmation before adding --confirm — never self-confirm a destructive call. Use --dry-run first to show the user exactly what would execute. GW_API_CONFIRM=off disables the guard (power users only).
# Show the user what would happen, then (after they approve):
$CLI api call gmail users.messages.trash --params '{"userId":"me","id":"MSG_ID"}' --dry-run
$CLI api call gmail users.messages.trash --params '{"userId":"me","id":"MSG_ID"}' --confirm
Examples
# Drive: search files (no curated drive group needed)
$CLI api call drive files.list --params '{"q":"name contains \"report\"","pageSize":10}' --compact
# People: list contacts
$CLI api call people people.connections.list --params '{"resourceName":"people/me","personFields":"names,emailAddresses"}' --compact
# Escape hatch — Admin SDK directory
$CLI api call admin:directory_v1 users.list --params '{"customer":"my_customer"}' --compact
# Create via request body
$CLI api call drive files.create --json '{"name":"Notes","mimeType":"application/vnd.google-apps.folder"}' --compact
Notes
- Discovery docs are cached 24h under the gw config dir (
cache/discovery/);--no-cacheforces a refetch. Offline runs fall back to the cache with a stderr note. - On 403 insufficient-scope errors the CLI prints the method's required scopes vs the token's scopes and suggests
gw auth login. --account NAMEselects the account (seegw auth list); default per config.- Empty API responses (e.g. after a delete) print
{"status":"ok"}.