Sponsor Suno AI Music arrow_forward
Claude Cowork

Claude Cowork

Language

English 中文 日本語 한국어 繁體中文 Español Deutsch Français Português (BR) Italiano Русский Nederlands Polski Tiếng Việt Indonesia
download Download Get Started
Subagent

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.

Type
Subagent
Repository
alirezarezvani/claude-skills
GitHub stars
26.6k
License
MIT
Repo last updated
Aug 30, 2026
Source file
agents/engineering-team/cs-workspace-admin.md
Model
opus

What Cs Workspace Admin is

Cs Workspace Admin is a subagent published in the alirezarezvani/claude-skills repository on GitHub, which has about 26.6k stars. The repository describes itself as: “380 Claude Code skills & agent skills & plugins (30+ Agents, 70+ custom commands, 380+ skills, customizable references, scripts)for Claude Code, Codex, Gemini CLI, Cursor, and 8 more coding agents — engineering, marketing, product, compliance, C-level advisory, research, business operations, commercial & finance, and your daily productivity skills.”

A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.

Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Cs Workspace Admin and get back a compact result.

It is set up to use these tools: Read, Write, Bash, Grep, Glob. Limiting tools is a good sign: the subagent can only do what those tools allow.

How to install Cs Workspace Admin

Claude Code

  1. Download cs-workspace-admin.md from the repository.
  2. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
  3. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Claude Cowork

  1. Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
  2. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from agents/engineering-team/cs-workspace-admin.md, shared under the repository's MIT license. Read the full file on GitHub.

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/skills/google-workspace-cli/scripts/gws_doctor.py
  • Usage: python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_doctor.py [--json]
  • Purpose: Pre-flight diagnostics — checks installation, auth, and service connectivity
  1. Auth Setup Guide
  • Path: ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py
  • Usage: python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth
  • Purpose: Guided auth setup, scope listing, .env generation, validation
  1. Recipe Runner
  • Path: ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py
  • Usage: python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --list
  • Purpose: Catalog, search, and execute 43 built-in recipes with persona filtering
  1. Workspace Audit
  • Path: ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py
  • Usage: python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py [--json]
  • Purpose: Security and configuration audit across Workspace services
  1. Output Analyzer
  • Path: ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/output_analyzer.py
  • Usage: gws ... --json | python3 ../../engineering-team/google-workspace-cli/skills/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/skills/google-workspace-cli/references/gws-command-reference.md
  • 18 services, 22 helpers, global flags, environment variables
  1. Recipes Cookbook — ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/references/recipes-cookbook.md
  • 43 recipes organized by category with persona mapping
  1. Troubleshooting — ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/references/troubleshooting.md
  • Common errors, auth issues, platform-specific fixes

Templates

  1. Workspace Config — ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/assets/workspace-config.json
  • Automation config template with auth, defaults, scheduled tasks
  1. Persona Profiles — ../../engineering-team/google-workspace-cli/skills/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 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:

python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_doctor.py
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/auth_setup_guide.py --guide oauth
python3 ../../engineering-team/google-workspace-cli/skills/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 --list
  3. Execute recipes with gws_recipe_runner.py --run (use --dry-run first)
  4. Pipe output through output_analyzer.py for filtering and analysis

Example:

python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --persona pm --list
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/gws_recipe_runner.py --run standup-report --dry-run
gws recipes standup-report --json | python3 ../../engineering-team/google-workspace-cli/skills/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:

python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py --json
python3 ../../engineering-team/google-workspace-cli/skills/google-workspace-cli/scripts/workspace_audit.py --json | \
  python3 ../../engineering-team/google-workspace-cli/skills/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 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:

python3 ../../engineering-team/google-workspace-cli/skills/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/skills/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 — Engineering team coordination

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is Cs Workspace Admin?

Cs Workspace Admin is a subagent for Claude Code and Claude Cowork from the alirezarezvani/claude-skills repository on GitHub. 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.

How do I install Cs Workspace Admin in Claude Code?

Download cs-workspace-admin.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.

Can I use Cs Workspace Admin in Claude Cowork?

Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.

Is Cs Workspace Admin safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.