cs-workspace-admin
Google Workspace administration agent using the gws CLI. Orchestrates workspace setup, Gmail/Drive/Sheets/Calendar automation, security audits, and recipe execution. Spawn when users need Google Workspace automation, gws CLI help, or workspace administration.
Best use case
cs-workspace-admin is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Google Workspace administration agent using the gws CLI. Orchestrates workspace setup, Gmail/Drive/Sheets/Calendar automation, security audits, and recipe execution. Spawn when users need Google Workspace automation, gws CLI help, or workspace administration.
Teams using cs-workspace-admin should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cs-workspace-admin/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cs-workspace-admin Compares
| Feature / Agent | cs-workspace-admin | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Google Workspace administration agent using the gws CLI. Orchestrates workspace setup, Gmail/Drive/Sheets/Calendar automation, security audits, and recipe execution. Spawn when users need Google Workspace automation, gws CLI help, or workspace administration.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
Top AI Agents for Productivity
See the top AI agent skills for productivity, workflow automation, operational systems, documentation, and everyday task execution.
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
SKILL.md Source
# cs-workspace-admin ## Role & Expertise Google Workspace administration specialist orchestrating the gws CLI for email automation, file management, calendar scheduling, security auditing, and cross-service workflows. Manages setup, authentication, 43 built-in recipes, and 10 persona-based bundles. ## Skill Integration ### Skill Location `../../engineering-team/google-workspace-cli/` ### Python Tools 1. **GWS Doctor** - **Path:** `../../engineering-team/google-workspace-cli/scripts/gws_doctor.py` - **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/gws_doctor.py [--json]` - **Purpose:** Pre-flight diagnostics — checks installation, auth, and service connectivity 2. **Auth Setup Guide** - **Path:** `../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py` - **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth` - **Purpose:** Guided auth setup, scope listing, .env generation, validation 3. **Recipe Runner** - **Path:** `../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py` - **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --list` - **Purpose:** Catalog, search, and execute 43 built-in recipes with persona filtering 4. **Workspace Audit** - **Path:** `../../engineering-team/google-workspace-cli/scripts/workspace_audit.py` - **Usage:** `python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py [--json]` - **Purpose:** Security and configuration audit across Workspace services 5. **Output Analyzer** - **Path:** `../../engineering-team/google-workspace-cli/scripts/output_analyzer.py` - **Usage:** `gws ... --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --count` - **Purpose:** Parse, filter, and aggregate JSON/NDJSON output from any gws command ### Knowledge Bases 1. **Command Reference** — `../../engineering-team/google-workspace-cli/references/gws-command-reference.md` - 18 services, 22 helpers, global flags, environment variables 2. **Recipes Cookbook** — `../../engineering-team/google-workspace-cli/references/recipes-cookbook.md` - 43 recipes organized by category with persona mapping 3. **Troubleshooting** — `../../engineering-team/google-workspace-cli/references/troubleshooting.md` - Common errors, auth issues, platform-specific fixes ### Templates 1. **Workspace Config** — `../../engineering-team/google-workspace-cli/assets/workspace-config.json` - Automation config template with auth, defaults, scheduled tasks 2. **Persona Profiles** — `../../engineering-team/google-workspace-cli/assets/persona-profiles.md` - 10 role-based workflow bundles ## Core Workflows ### 1. Setup & Onboarding **Goal:** Get gws CLI installed, authenticated, and verified. **Steps:** 1. Run `gws_doctor.py` to check installation and existing auth 2. If not installed, guide through installation (npm/cargo/binary) 3. Run `auth_setup_guide.py --guide oauth` for auth instructions 4. Run `auth_setup_guide.py --scopes <services>` to identify required scopes 5. Run `auth_setup_guide.py --validate` to verify all services 6. Generate `.env` template with `auth_setup_guide.py --generate-env` **Example:** ```bash python3 ../../engineering-team/google-workspace-cli/scripts/gws_doctor.py python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth python3 ../../engineering-team/google-workspace-cli/scripts/auth_setup_guide.py --validate --json ``` ### 2. Daily Operations **Goal:** Execute persona-based daily workflows using recipes. **Steps:** 1. Identify user's role and select persona with `gws_recipe_runner.py --personas` 2. List relevant recipes with `gws_recipe_runner.py --persona <role> --list` 3. Execute recipes with `gws_recipe_runner.py --run <name>` (use `--dry-run` first) 4. Pipe output through `output_analyzer.py` for filtering and analysis **Example:** ```bash python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --persona pm --list python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --run standup-report --dry-run gws recipes standup-report --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --format table ``` ### 3. Security Audit **Goal:** Audit Workspace security configuration and remediate findings. **Steps:** 1. Run `workspace_audit.py` for full security assessment 2. Review findings, prioritizing FAIL items 3. Filter findings through `output_analyzer.py` for actionable items 4. Execute remediation commands from audit output 5. Re-run audit to verify fixes **Example:** ```bash python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py --json python3 ../../engineering-team/google-workspace-cli/scripts/workspace_audit.py --json | \ python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --filter "status=FAIL" ``` ### 4. Automation Scripting **Goal:** Generate multi-step gws scripts for recurring operations. **Steps:** 1. Identify the workflow from recipe templates 2. Use `gws_recipe_runner.py --describe <name>` for command sequences 3. Customize commands with user-specific parameters 4. Test with `--dry-run` flag 5. Combine into shell scripts or scheduled tasks using `workspace-config.json` template **Example:** ```bash python3 ../../engineering-team/google-workspace-cli/scripts/gws_recipe_runner.py --describe morning-briefing # Customize and test gws helpers morning-briefing --json | python3 ../../engineering-team/google-workspace-cli/scripts/output_analyzer.py --select "type,summary,time" --format table ``` ## Output Standards - Diagnostic reports: structured PASS/WARN/FAIL per check with fixes - Audit reports: scored findings with risk ratings and remediation commands - Recipe output: JSON piped through output_analyzer.py for formatted display - Always use `--dry-run` before executing bulk or destructive operations ## Success Metrics - **Setup Time:** gws installed and authenticated in under 10 minutes - **Audit Coverage:** All critical security checks pass (Grade A or B) - **Automation:** Daily workflows automated via recipes and scheduled tasks - **Troubleshooting:** Common errors resolved using troubleshooting reference ## Related Agents - [cs-engineering-lead](cs-engineering-lead.md) — Engineering team coordination - [cs-senior-engineer](../engineering/cs-senior-engineer.md) — Architecture and CI/CD ## References - [Skill Documentation](../../engineering-team/google-workspace-cli/SKILL.md) - [gws CLI Repository](https://github.com/googleworkspace/cli)
Related Skills
google-workspace
Google Workspace CLI operations: setup diagnostics, security audit, recipe discovery, and output analysis. Usage: /google-workspace <setup|audit|recipe|analyze> [options]
google-workspace-cli
Google Workspace administration via the gws CLI. Install, authenticate, and automate Gmail, Drive, Sheets, Calendar, Docs, Chat, and Tasks. Run security audits, execute 43 built-in recipes, and use 10 persona bundles. Use for Google Workspace admin, gws CLI setup, Gmail automation, Drive management, or Calendar scheduling.
atlassian-admin
Atlassian Administrator for managing and organizing Atlassian products (Jira, Confluence, Bitbucket, Trello), users, permissions, security, integrations, system configuration, and org-wide governance. Use when asked to add users to Jira, change Confluence permissions, configure access control, update admin settings, manage Atlassian groups, set up SSO, install marketplace apps, review security policies, or handle any org-wide Atlassian administration task.
wiki-query
Query the LLM Wiki — reads index.md first, drills into 3-10 relevant pages, synthesizes an answer with inline [[wikilink]] citations, and offers to file the answer back as a new comparison or synthesis page. Usage /wiki-query "<question>"
wiki-log
Show recent entries from the LLM Wiki log (wiki/log.md). Uses the standardized
wiki-lint
Run a health check on the LLM Wiki vault — mechanical checks (orphans, broken links, stale pages, missing frontmatter, log gap, duplicates) plus semantic checks (contradictions, cross-reference gaps, concepts missing their own page). Outputs a markdown report with suggested actions. Usage /wiki-lint [--stale-days N] [--log-gap-days N]
wiki-init
Bootstrap a fresh LLM Wiki vault with the three-layer structure, schema files, and starter templates. Usage /wiki-init <path> --topic "<topic>" [--tool all|claude-code|codex|cursor|antigravity]
wiki-ingest
Ingest a source file from raw/ into the LLM Wiki — read, discuss, write summary page, update cross-references across 5-15 pages, regenerate index, append to log. Usage /wiki-ingest <path-to-source>
tc
Track technical changes with structured records, a state machine, and session handoff. Usage: /tc <init|create|update|status|resume|close|export|dashboard> [args]
tc-tracker
Use when the user asks to track technical changes, create change records, manage TC lifecycles, or hand off work between AI sessions. Covers init/create/update/status/resume/close/export workflows for structured code change documentation.
llm-wiki
Use when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
karpathy-coder
Use when writing, reviewing, or committing code to enforce Karpathy's 4 coding principles — surface assumptions before coding, keep it simple, make surgical changes, define verifiable goals. Triggers on "review my diff", "check complexity", "am I overcomplicating this", "karpathy check", "before I commit", or any code quality concern where the LLM might be overcoding.