Capability
Other metadata
- metadata
{
"version": "0.22.5",
"openclaw": {
"category": "productivity",
"requires": {
"bins": [
"gws"
]
}
}
}
Topics
- CLI
- API
- google-workspace
- authentication
- oauth
- service-account
- output-formatting
- shell
What it does
Provides shared CLI patterns for the gws tool, including OAuth and service account authentication, output formatting (JSON, table, YAML, CSV), and pagination across Google Workspace APIs. Use this skill when building gws commands that need consistent flag handling, secret redaction, or dry-run validation before API calls.
Generated from the current SKILL.md.
Frequently asked
Does this skill work with service accounts or only OAuth?
Both. You can use browser-based OAuth with `gws auth login` or service account authentication by setting GOOGLE_APPLICATION_CREDENTIALS to a key.json file.
What output formats are supported?
The skill supports json (default), table, yaml, and csv via the `--format` flag. For paginated results, `--page-all` returns NDJSON output.
How do I safely test commands before running them?
Use the `--dry-run` flag to validate commands locally without making API calls. For destructive operations, always confirm with the user first.
Does this skill handle sensitive data filtering?
Yes. The `--sanitize` flag screens responses through Model Armor for PII and content safety. Never output secrets like API keys or tokens directly.
Are there shell compatibility issues I should know about?
Yes. In zsh, use double quotes with escaped inner quotes for ranges containing `!` (like `Sheet1!A1`) and single quotes for `--params` and `--json` values to prevent shell interpretation of special characters.
Generated from the current SKILL.md. These answers refresh after source changes.