AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Gws

skill-fmind-dot-gws · by fmind

Use gws for Google Workspace mail, Drive files, Docs, Sheets, Calendar, and Chat.

— No reviews yet
0 installs
4 views
0.0% view→install

Install

$ agentstack add skill-fmind-dot-gws

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • ✓ Prompt-injection patterns
  • ✓ Secret / credential exfiltration
  • ✓ Dangerous shell & filesystem operations
  • ✓ Untrusted network calls
  • ✓ Known-malicious package signatures

What it can access

  • ✓ Network access No
  • ✓ Filesystem access No
  • ✓ Shell / process execution No
  • ✓ Environment & secrets No
  • ✓ Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-fmind-dot-gws)

Reliability & compatibility

✓ Security review passed
0 installs to date
— no reviews yet
● today

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Gws? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Google Workspace CLI

Use gws for Google Workspace automation from the shell: authentication, API discovery, bounded reads, and verified writes across Drive, Docs, Sheets, Gmail, Calendar, and Chat. Prefer the CLI for supported operations; use a connected app when the requested native editing operation needs its document context or capabilities.

Workflow

  1. Resolve the profile: check gws --version and gws auth status for the account and scopes without printing credentials. Set GOOGLE_WORKSPACE_CLI_CONFIG_DIR before auth commands to isolate profiles; an existing GOOGLE_WORKSPACE_CLI_TOKEN or GOOGLE_WORKSPACE_CLI_CREDENTIALS_FILE can override stored credentials, so verify the effective identity without echoing those values.
  2. Inspect the installed command and live schema: use --help for flags and schema for the API contract. Start without recursive reference expansion; inspect a referenced type separately when needed.

``bash gws schema gws schema ``

  1. Start with a bounded read: pass identifiers and filters through --params; use --page-all --page-limit only when every page is needed.

``bash gws drive files list --params '{"pageSize":10,"q":"trashed = false","fields":"nextPageToken,files(id,name,mimeType)"}' --format json ``

  1. Choose the content path: read [service recipes](references/services.md) for metadata versus bodies, Docs tabs, Sheets ranges, Gmail MIME/replies, Calendar times, Slides and Drive exports. Prefer the installed +read, +reply, +send, +write, or +upload helper when its documented semantics match the request.
  2. Prepare writes exactly: resolve stable identifiers, ranges and recipients first. Follow [file-based requests](references/requests.md) to serialize multiline content, separate --params from --json, and inspect a --dry-run. It validates request construction, not permissions or server acceptance. For Chat, follow [formatting and threads](references/chat.md) before composing text.
  3. Write with authority: reuse authority already supplied by the user for the intended create or edit. Resolve service, IDs or ranges, content, recipients, and sharing effects before execution; ask only for missing consequential scope. Sending mail or Chat, destructive changes, and permission changes require explicit authority. Prepare the concrete request before asking for missing approval.
  4. Apply the smallest call: no broad search followed by an unreviewed batch mutation; keep retries idempotent with stable request identifiers or a read-before-write guard where the API supports them.
  5. Verify by reading back: fetch the changed resource and compare the requested fields; for messages and events, separate accepted API state from recipient-visible delivery.

For paginated calls, --page-all emits NDJSON with one object per page, not one JSON array. Preserve nextPageToken (and Drive incompleteSearch) in field selections; reaching --page-limit with a remaining token means the result is incomplete. Request only the fields, date range, and records needed; save stdout and check the CLI exit status before processing it.

Task guides

  • [cli-details](references/cli-details.md): Use local Workspace helpers and diagnose CLI authentication, schema, pagination, or request failures.

Official Skills

Upstream: googleworkspace/cli skills, which generates a shared base skill plus one selection per API. Discover with skills add googleworkspace/cli --list. Follow the shared [vendor-skill policy](../agent-project/references/vendor-skills.md) and include the base dependency required by the chosen service.

Documentation

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

  • Author: fmind
  • Source: fmind/dot
  • License: MIT
  • Homepage: https://fmind.dev

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.