Google Workspace
NousResearch/hermes-agent
Gmail, Calendar, Drive, Docs, Sheets via gws CLI or Python. An agent skill from NousResearch/hermes-agent.
This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google…
Install Google Workspace CLI
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install borghei/Claude-Skills google-workspace-cli --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/engineering/google-workspace-cli .claude/skills/google-workspace-cli && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .claude/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cliType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install borghei/Claude-Skills google-workspace-cli --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/engineering/google-workspace-cli .agents/skills/google-workspace-cli && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .agents/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install borghei/Claude-Skills google-workspace-cli --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/engineering/google-workspace-cli .cursor/skills/google-workspace-cli && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .cursor/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/borghei/Claude-Skills.git --path engineering/google-workspace-cli--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install borghei/Claude-Skills google-workspace-cli --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/engineering/google-workspace-cli .gemini/skills/google-workspace-cli && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .gemini/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install borghei/Claude-Skills google-workspace-cliInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/engineering/google-workspace-cli .github/skills/google-workspace-cli && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .github/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add borghei/Claude-Skills --skill google-workspace-cli -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install borghei/Claude-Skills google-workspace-cli --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/borghei/Claude-Skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/engineering/google-workspace-cli .opencode/skills/google-workspace-cli && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "google-workspace-cli" agent skill from https://github.com/borghei/Claude-Skills/tree/main/engineering/google-workspace-cli into .opencode/skills/google-workspace-cli/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "google-workspace-cli", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
google-workspace-cli- GitHub stars
- 881
- Token cost
- ~1.6k tokens
- SKILL.md length
- 577 words
- Files
- 5 (incl. scripts, references)
- Skills in repo
- 349
- Repo updated
- First seen
- Licence
- MIT
At a glance
This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google…
- Works in 5 steps: Export config - Export GWS settings to… → Audit - Run workspace_audit.py against… → Review findings - Prioritize critical… → …
- Asks to audit Google Workspace
- SKILL.md covers Overview, Clarify First, Quick Start and Tools Overview, plus 3 more sections
- Runs Python scripts from its folder; calls python
What it does
Google Workspace CLI is an agent skill from borghei/Claude-Skills. This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google admin configurations".
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including scripts and reference files (for example `references/gws-admin-guide.md`, `scripts/auth_setup_guide.py` and `scripts/gws_doctor.py`).
It sits in Documents & Office, covering Cloud office suites. It works with Google Workspace. The repository describes itself as: 385 AI skills, 77 expert agents, and 900 stdlib Python tools for every team: engineering, PM, marketing, C-level, compliance, business ops, research, and a LinkedIn toolkit… The licence is MIT.
When your agent uses it
- Asks to audit Google Workspace
- Check GWS security settings
- Set up Google Workspace authentication
- Diagnose Workspace issues
Example prompts
- “audit Google Workspace”
- “check GWS security settings”
- “set up Google Workspace authentication”
- “/google-workspace-cli”
Requirements
- Python 3
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Export config - Export GWS settings to JSON via Admin SDK or manual export
- Audit - Run workspace_audit.py against the config file
- Review findings - Prioritize critical security gaps
- Remediate - Apply recommended settings in Admin Console
- Re-audit - Verify changes resolved findings
What it can do on your machine
Read from SKILL.md and the folder at commit 4a698e8. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Ships 3 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
python
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Google Workspace CLI loads about 1.6k tokens when it runs, and up to ~2.6k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 577 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); the scripts in this folder are not scanned.
SKILL.md
The full file from borghei/Claude-Skills at commit 4a698e8, republished under its MIT licence (© borghei). 577 words, ~1,552 tokens.
Download SKILL.mdSave it as
.claude/skills/google-workspace-cli/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- google-workspace-cli
- description
- This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google admin configurations".
- license
- MIT + Commons Clause
- metadata.version
- 1.0.0
- metadata.author
- borghei
- metadata.category
- engineering
- metadata.domain
- google-workspace
- metadata.updated
- 2026-04-02
- metadata.tags
- google-workspace, gws, admin, security, audit
Google Workspace CLI
Category: Engineering Domain: Google Workspace Administration
Overview
The Google Workspace CLI skill provides tools for auditing Google Workspace configurations, generating authentication setup documentation, and diagnosing common GWS issues. It helps IT administrators maintain secure, well-configured Workspace environments without needing to navigate complex admin consoles.
Clarify First
Before running, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- Task — security audit, auth setup guide, or diagnostics (selects
workspace_audit.pyvsauth_setup_guide.pyvsgws_doctor.py) - Config export or auth method — the GWS config JSON to audit, or the auth method and scopes for a setup guide (sets
--configor--method/--scopes) - Output mode — human-readable vs JSON for automation (sets
--format json)
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
# Audit Workspace security configuration
python scripts/workspace_audit.py --config gws-config.json
# Generate auth setup guide
python scripts/auth_setup_guide.py --method oauth --scopes admin,drive
# Run diagnostics
python scripts/gws_doctor.py --check all
# JSON output for automation
python scripts/workspace_audit.py --config gws-config.json --format jsonTools Overview
workspace_audit.py
Audits Google Workspace configuration exports for security best practices.
| Feature | Description |
|---|---|
| 2FA enforcement | Checks if 2-step verification is required |
| Password policy | Validates password strength requirements |
| Sharing settings | Reviews external sharing configurations |
| App access | Checks third-party app access policies |
| Admin roles | Reviews admin role assignments |
| Mobile management | Checks device management policies |
| Drive settings | Validates Drive sharing and access controls |
auth_setup_guide.py
Generates step-by-step authentication setup documentation for GWS API access.
| Feature | Description |
|---|---|
| OAuth setup | Generates OAuth 2.0 configuration guide |
| Service account | Creates service account setup documentation |
| API scopes | Lists required scopes for each API |
| Domain delegation | Documents domain-wide delegation setup |
| Testing guide | Provides verification steps |
gws_doctor.py
Diagnostic tool for common Google Workspace configuration issues.
| Feature | Description |
|---|---|
| DNS checks | Validates MX, SPF, DKIM, DMARC records format |
| SSL/TLS | Checks certificate and transport security settings |
| Integration health | Validates common integration patterns |
| Config consistency | Checks for conflicting settings |
| Best practices | Compares against GWS recommended settings |
Workflows
Security Audit Workflow
- Export config - Export GWS settings to JSON via Admin SDK or manual export
- Audit - Run workspace_audit.py against the config file
- Review findings - Prioritize critical security gaps
- Remediate - Apply recommended settings in Admin Console
- Re-audit - Verify changes resolved findings
Show full SKILL.md (234 more words)Show less
API Setup Workflow
- Plan - Determine which APIs and scopes are needed
- Generate guide - Run auth_setup_guide.py with desired method
- Follow steps - Create credentials in Google Cloud Console
- Configure - Set up domain delegation if needed
- Verify - Test API access with provided verification steps
Health Check Workflow
- Run diagnostics - Execute gws_doctor.py with all checks
- Review results - Check DNS, email, and integration health
- Fix issues - Address failures in priority order
- Re-check - Verify fixes pass diagnostics
Regular Maintenance
# Monthly security audit
python scripts/workspace_audit.py --config gws-export.json --format json > audit_$(date +%Y%m).json
# Weekly health check
python scripts/gws_doctor.py --check dns,email --format jsonReference Documentation
- GWS Admin Guide - Security settings, API configuration, DNS requirements
Common Patterns Quick Reference
Security Priorities
| Setting | Priority | Impact |
|---|---|---|
| 2FA enforcement | Critical | Prevents account takeover |
| Password policy | Critical | Reduces credential attacks |
| External sharing | High | Prevents data leakage |
| App access control | High | Limits third-party risk |
| Mobile management | Medium | Secures device access |
| Admin role review | Medium | Limits privilege exposure |
DNS Records for Email
| Record | Purpose | Example |
|---|---|---|
| MX | Email routing | ASPMX.L.GOOGLE.COM |
| SPF | Sender verification | v=spf1 include:_spf.google.com ~all |
| DKIM | Email signing | Domain-specific CNAME |
| DMARC | Policy enforcement | v=DMARC1; p=reject; rua=mailto:... |
API Scopes
| API | Scope | Purpose |
|---|---|---|
| Admin SDK | admin.directory.user | User management |
| Drive | drive.readonly | File listing |
| Gmail | gmail.settings.basic | Email settings |
| Calendar | calendar.readonly | Calendar access |
Common Issues
| Issue | Symptom | Fix |
|---|---|---|
| No 2FA | Account takeover risk | Enable 2FA enforcement |
| Weak passwords | Credential stuffing | Set 12+ char minimum |
| Open sharing | Data leakage | Restrict external sharing |
| No DMARC | Email spoofing | Add DMARC DNS record |
| Stale admins | Excessive privileges | Review admin roles quarterly |
© borghei, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts, references) in engineering/google-workspace-cli of borghei/Claude-Skills.
- SKILL.md
- references/gws-admin-guide.md
- scripts/auth_setup_guide.py
- scripts/gws_doctor.py
- scripts/workspace_audit.py
Open the folder on GitHubat commit 4a698e8
Compare with similar skills
Google Workspace CLI next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Google Workspace CLI this skillborghei/Claude-Skills | 881 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Google WorkspaceNousResearch/hermes-agent | 252k | 3 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Managing Google Workspacetaylorwilsdon/google_workspace_mcp | 3.3k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Gogopenclaw/gogcli | 8.5k | — | ~2.9k | Automated safety check: Pass | MIT | |
| Gws Calendar Agendagoogleworkspace/cli | 31k | 1 repos | ~389 | Automated safety check: Pass | Apache-2.0 | |
| Gws Drive Uploadgoogleworkspace/cli | 31k | 1 repos | ~322 | Automated safety check: Pass | Apache-2.0 |
Similar skills
Managing Google Workspace
taylorwilsdon/google_workspace_mcp
Manages Google Workspace operations across 12 services (Gmail, Drive, Calendar, Docs, Sheets, Slides, Forms, Tasks, Contacts, Chat, Apps Script, Custom Search).
Gog
openclaw/gogcli
gog CLI: safe Google Workspace automation, JSON, auth, scoped reads/writes.
Gws Calendar Agenda
googleworkspace/cli
Google Calendar: Show upcoming events across all calendars. An agent skill from googleworkspace/cli.
Gws Drive Upload
googleworkspace/cli
Google Drive: Upload a file with automatic metadata. An agent skill from googleworkspace/cli.
Google Workspace
mitsuhiko/agent-stuff
Access Google Workspace APIs (Drive, Docs, Calendar, Gmail, Sheets, Slides, Chat, People) via local helper scripts without MCP.
More from borghei/Claude-Skills
All 349 skills in this repoAgents In The Team
borghei/Claude-Skills
Run delivery when AI coding and ops agents take tickets. An agent skill from borghei/Claude-Skills.
AI Content Disclosure
borghei/Claude-Skills
Check AI-generated marketing content and reviews for required disclosures under the EU AI Act, FTC rules and platform AI-label policies.
AI Prototyping
borghei/Claude-Skills
Idea to AI-generated prototype to customer validation to engineering handoff.
Analytics Engineer
borghei/Claude-Skills
Analytics engineering across data modeling, dbt, transformation, and semantic layers.
Ansoff Matrix
borghei/Claude-Skills
Ansoff Matrix — 4-quadrant framework for growth options: market penetration, market/product development, and diversification.
Brainstorm Okrs
borghei/Claude-Skills
OKR brainstorming and validation using the Radical Focus framework — outcome objectives, measurable key results, counter-metrics.
Related
Works with
Categories
Questions about Google Workspace CLI
What does Google Workspace CLI do?
This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google…. Google Workspace CLI is an agent skill from borghei/Claude-Skills. This skill should be used when the user asks to "audit Google Workspace", "check GWS security settings", "set up Google Workspace authentication", "diagnose Workspace issues", or "review Google admin configurations".
When should I use Google Workspace CLI?
Google Workspace CLI fits situations like: asks to audit Google Workspace; check GWS security settings; set up Google Workspace authentication; diagnose Workspace issues.
How do I install Google Workspace CLI in Claude Code?
Run `npx skills add borghei/Claude-Skills --skill google-workspace-cli -a claude-code`. Or copy the skill folder (engineering/google-workspace-cli in borghei/Claude-Skills) into .claude/skills/google-workspace-cli in your project. Claude Code loads it when a task matches its description.
How do I install Google Workspace CLI in Codex?
Run `npx skills add borghei/Claude-Skills --skill google-workspace-cli -a codex`. Or copy the skill folder (engineering/google-workspace-cli in borghei/Claude-Skills) into .agents/skills/google-workspace-cli in your project. Codex loads it when a task matches its description.
Can I use Google Workspace CLI in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add borghei/Claude-Skills --skill google-workspace-cli -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/google-workspace-cli, .gemini/skills/google-workspace-cli, .github/skills/google-workspace-cli and .opencode/skills/google-workspace-cli in your project.
What does Google Workspace CLI need to run?
Going by SKILL.md and its folder, Google Workspace CLI needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.
Does Google Workspace CLI access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Google Workspace CLI safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.
What licence does Google Workspace CLI use?
Google Workspace CLI is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Google Workspace CLI use?
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.1k tokens, read only when the agent opens those files.
What are the alternatives to Google Workspace CLI?
Skills that share tags, products or a category with Google Workspace CLI: Google Workspace (NousResearch/hermes-agent, 252k stars), Managing Google Workspace (taylorwilsdon/google_workspace_mcp, 3.3k stars), Gog (openclaw/gogcli, 8.5k stars) and Gws Calendar Agenda (googleworkspace/cli, 31k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Google Workspace CLI?
borghei (a GitHub user) maintains it in borghei/Claude-Skills, which has 881 GitHub stars. The repository holds 349 skills in this directory. The repository was last updated on October 7, 2026.
Source: borghei/Claude-Skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.