Gws Shared
v1.0.13gws CLI: Shared patterns for authentication, global flags, and output formatting.
⭐ 0· 1.1k·23 current·24 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (shared patterns for the gws CLI) match the instructions: the skill is an instruction-only reference and only needs the gws binary. The SKILL.md links to the googleworkspace/cli repo which aligns with purpose, but the registry metadata lacks a homepage and the SKILL.md internal version (0.22.5) differs from the registry version (1.0.13), which is a minor inconsistency.
Instruction Scope
The runtime instructions reference the environment variable GOOGLE_APPLICATION_CREDENTIALS for service-account auth, but the skill metadata lists no required env vars. SKILL.md also instructs saving uploads/outputs to files and using interactive auth — these are expected for a CLI, but the undocumented env var use is an inconsistency that should be clarified.
Install Mechanism
There is no install spec and no code files; this is instruction-only and only requires the gws binary to already be on PATH, which is the lowest-risk install posture.
Credentials
Although the skill declares no required environment variables, the documentation explicitly references GOOGLE_APPLICATION_CREDENTIALS for service accounts. Requesting or advising use of that credential without declaring it in metadata is a mismatch that could lead to surprises; otherwise there are no additional credentials requested.
Persistence & Privilege
The skill is not always-enabled and makes no claims to modify other skills or agent-wide configuration. It does not request elevated persistence.
Assessment
This is an instruction-only reference for the gws CLI and appears to be what it says, but check a few things before installing: 1) Verify you will install the gws binary from the official googleworkspace/cli source and trust that binary. 2) The SKILL.md mentions GOOGLE_APPLICATION_CREDENTIALS (service account key) but the skill metadata doesn't declare env requirements — confirm whether the skill will actually need that env var and avoid exposing service-account keys unless necessary. 3) Be cautious when running write/delete commands — the doc recommends confirming with the user and using --dry-run; ensure any agent using this skill actually prompts you before destructive actions. 4) If you need higher assurance, ask the publisher for a homepage/repo link and an explanation of the metadata version mismatch before enabling the skill.Like a lobster shell, security has layers — review code before you run it.
latestvk9769jmajsgadcy0fbgadyca7983zyr8
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
Binsgws