Lark CLI (lark-cli)
larksuite/cliThe official Lark/Feishu command-line tool with 200+ commands and about 29 agent skills for messaging, docs, Base, sheets, calendar, mail, tasks and more.
Recommended
Check first Depth 4/5
Google Workspace CLI (gws) Claude skills
A command-line tool for Drive, Gmail, Calendar, Sheets, Docs and Chat that builds its commands from Google's Discovery Service, plus about 40 thin agent skills.
Our verdict Recommended with caveats
A capable CLI with sensible credential handling, but it is unofficial, pre-1.0 and gives the agent real access to mail and files, so set scopes carefully.
What Google Workspace CLI (gws) does
gws is a command-line client for Google Workspace APIs. Instead of a fixed command list, it reads Google's Discovery Service at runtime and builds commands for Drive, Gmail, Calendar, Sheets, Docs, Slides, Chat, Admin and other APIs. Output is structured JSON, with --dry-run to preview requests, auto-pagination, and a schema command to inspect any method. Credentials can come from an OAuth login, a pre-obtained token, a credentials file or a service account, and stored credentials are encrypted at rest with the key held in the OS keyring.
The repository's skills are the agent-facing layer: roughly one SKILL.md per API (gws-drive, gws-gmail, gws-sheets and so on), helper skills for common actions such as gws-gmail-send, gws-gmail-triage, gws-calendar-agenda and gws-sheets-append, a few workflow recipes, and Model Armor skills that sanitize prompts and responses through Google Cloud Model Armor. The skills are short (about 1.7 KB each) and mostly tell the agent which gws command to run; there are no scripts or references in the skill folders. The README states plainly that this is not an officially supported Google product and that breaking changes are expected before v1.0. You need a Google Cloud project to create OAuth credentials.
Good for
- Letting an agent read and write Drive, Sheets, Docs and Calendar through one CLI
- Scripting Workspace admin and reporting tasks with JSON output
- Teams already comfortable creating a Google Cloud OAuth client
Not for
- Anyone who cannot or will not set up a Google Cloud project and OAuth consent
- Users who need a supported, stable Google product (the README says it is not official and is pre-1.0)
What's inside depth 2/5
About 40 skill folders averaging 1.7 KB with no scripts or references; the real substance is the CLI binary, which sits outside the skill folders.
- Skills
- 95
- Reference docs
- 0
- Scripts
- 0
- Tests / evals
- 0
- Templates
- 0
- Avg SKILL.md
- 1.6 KB
Counted from the repository file tree. How we score depth.
Dependencies and costs
- A Google account and a Google Cloud project with OAuth credentials
- The gws binary (GitHub releases, npm, Homebrew or cargo)
- Node.js 18+ only for the npm install route
- Google Cloud Model Armor templates for the optional sanitization skills
- Telemetry: none found in the README or skills
Security review
Review before installingA Rust command-line tool plus about 95 generated skills that let an agent read and change your Google Workspace data (Gmail, Drive, Calendar, Docs, Sheets, Chat). Once you authorize it, anything those skills run can send mail or edit files with your account; the shared skill tells the agent to confirm write and delete commands, and --dry-run is available. Tokens are only sent to Google endpoints, are stored encrypted locally, and no telemetry was found. Most of the Rust source was not read line by line in this review.
Worth knowing
- Installs packages or toolsThe npm package runs a postinstall script (npm/install.js) that downloads the prebuilt gws binary from GitHub Releases, checks its SHA256 against a .sha256 file from the same release, and extracts it with tar/unzip/PowerShell.npm/package.json:19
- Makes network requestsThe gws CLI sends your OAuth/service-account bearer token and request data to Google Workspace API hosts (googleapis.com, oauth2.googleapis.com, Model Armor endpoints) and fetches API discovery documents.crates/google-workspace-cli/src/executor.rs:186
- Changes files outside your projectStores AES-GCM-encrypted credentials and a token cache in the gws config directory, and puts the encryption key in the OS keyring or an .encryption_key file;
gws auth setupalso drives gcloud to create/configure a Cloud project and OAuth client.crates/google-workspace-cli/src/credential_store.rs:150 - Relies on a CLI or package we could not review
gws auth setupshells out to the gcloud CLI, whose code is not in this repository.crates/google-workspace-cli/src/setup.rs:445
What we checked
The repository (222 files) on Oct 29, 2026. Not a full review: we read 20 of 58 code files; it relies on code outside the repository: prebuilt gws release binaries downloaded by the npm postinstall step (built from the Rust source here, but the binaries were not checked against it); gcloud CLI used by `gws auth setup`; Rust crate dependencies (yup-oauth2, reqwest, keyring, aes-gcm and others).
NVIDIA SkillSpector static scan: 438 pattern hits (Privilege Escalation 306, Agent Snooping 95, Data Exfiltration 17, MCP Rug Pull 5, Memory Poisoning 4, Tool Misuse 3). Credential hits are the CLI's own OAuth, keyring and credential-file handling, README documentation and .env.example placeholders. '/etc/passwd' is a path-traversal test string, 'Write skill' is the skill generator, and 'send the message to' is help text for the chat helper. CI workflow sudo/credentials lines belong to the repository's own pipeline.
A review, not a certification. Skills change after we check them — read the files before installing.
License
Apache-2.0 — commercial use allowed.
Can it run unattended?
Not really. These are command wrappers for interactive Workspace tasks; they have no loop, stop conditions or verification logic.
Skills in this repository
| Skill | Installs |
|---|---|
| gws-gmail | 83K |
| gws-gmail-send | 75K |
| gws-drive | 75K |
| gws-shared | 67K |
| gws-calendar | 62K |
Linked skills have their own review.
Alternatives to Google Workspace CLI (gws)
Anthropic Agent Skills
anthropics/skillsAnthropic's reference skills repo: 20 skills including document tools (docx, pptx, xlsx, pdf), frontend-design, skill-creator and mcp-builder.
Recommended
Check first Depth 4/5
Awesome Claude Skills (Composio)
ComposioHQ/awesome-claude-skillsA curated list of Claude skills plus hundreds of templated app-automation skills that run through Composio's hosted Rube MCP.
With caveats
Broad access Depth 1/5
FAQ
What is the Google Workspace CLI (gws)?
gws is an open-source command-line tool that gives access to Drive, Gmail, Calendar, Sheets, Docs, Chat and other Workspace APIs with JSON output. The repo also includes agent skills so tools like Gemini CLI or OpenClaw can drive it. It is not an officially supported Google product.
How do I install gws?
Download a binary from the GitHub releases page, or run npm install -g @googleworkspace/cli, brew install googleworkspace-cli, or cargo install --git https://github.com/googleworkspace/cli --locked. Then run gws auth setup and gws auth login. Add the agent skills with npx skills add https://github.com/googleworkspace/cli.
Is gws safe to give to an AI agent?
It stores credentials encrypted with a key in the OS keyring, and we found no hidden network calls. The risk is the access itself: an agent with mail and Drive scopes can be steered by malicious content, so grant minimal scopes and consider the Model Armor sanitization option.
gws vs the Lark CLI: how do they compare?
Both expose a workplace suite to agents through a command-line tool. gws covers Google Workspace and generates commands from Google's Discovery Service, while larksuite/cli covers Lark and Feishu with hand-curated commands and much longer skills.
Sources: GitHub repository (stars, license, file tree, last push Oct 26, 2026); install counts from skills.sh via Best Skills (CC BY 4.0). Review based on the README and SKILL.md files as published.