Files
Daniel Avila e2cbc8176c feat: Add 107 Google Workspace CLI commands (#403)
Migrated all skills from https://github.com/googleworkspace/cli to claude-code-templates as command components.

## Summary

Added 107 Google Workspace commands across three categories:
- 47 GWS service commands (gmail, drive, calendar, sheets, docs, etc.)
- 10 persona commands (IT admin, project manager, etc.)
- 50 recipe/workflow commands (task automation, team collaboration, etc.)

## GWS Service Commands (47)

Google Workspace API integrations for core services:
- Admin SDK (users, groups, devices, org units)
- Gmail (send, read, manage email)
- Calendar (events, scheduling, agenda)
- Drive (files, folders, sharing, upload)
- Docs/Sheets/Slides (document management)
- Chat/Meet (collaboration)
- Tasks (task management)
- Forms (form creation and responses)
- Classroom (education management)
- Vault (eDiscovery and archiving)
- Apps Script (automation)
- Model Armor (AI safety)
- And more specialized services

## Persona Commands (10)

Role-based workflow personas:
- IT Administrator
- Project Manager
- Executive Assistant
- Content Creator
- Customer Support
- Event Coordinator
- HR Coordinator
- Researcher
- Sales Operations
- Team Lead

## Recipe/Workflow Commands (50)

Task automation workflows:
- Email automation (batch reply, filters, drafts)
- Calendar management (scheduling, free time, events from sheets)
- Drive operations (folder organization, file ownership, sharing)
- Form workflows (feedback forms, response collection)
- Sheet automation (backup, compare tabs, reports)
- Team collaboration (announcements, file sharing, notifications)
- Meeting workflows (scheduling, participant review, materials)
- Security tasks (audit sharing, triage alerts)
- Document workflows (templates, save email to doc)
- And many more productivity automations

## Technical Details

- All commands use proper frontmatter (allowed-tools, argument-hint, description)
- Commands include usage examples and prerequisite checks
- Structured with Task sections for Claude Code execution
- Include Apache 2.0 license attribution
- Reference original skill names for traceability

## Component Catalog

- Updated docs/components.json
- Total commands: 168 → 275 (107 new)
- All new commands in google-workspace category with subcategories

## License & Attribution

Source: Google Workspace CLI (https://github.com/googleworkspace/cli)
License: Apache License 2.0
All commands include proper attribution and license information

Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
2026-03-07 15:25:10 -05:00

2.0 KiB

allowed-tools, argument-hint, description
allowed-tools argument-hint description
Bash, Read, Write, Edit
task-parameters
Push local files to a Google Apps Script project.

Deploy Apps Script

Execute Google Workspace workflow: $ARGUMENTS

Deploy an Apps Script Project

PREREQUISITE: Load the following skills to execute this recipe: gws-apps-script

Push local files to a Google Apps Script project.

Steps

  1. List existing projects: gws apps-script projects list --format table
  2. Get project content: gws apps-script projects getContent --params '{"scriptId": "SCRIPT_ID"}'
  3. Update content: gws apps-script projects updateContent --params '{"scriptId": "SCRIPT_ID"}' --json '{"files": [{"name": "Code", "type": "SERVER_JS", "source": "function main() { ... }"}]}'
  4. Create a new version: gws apps-script projects versions create --params '{"scriptId": "SCRIPT_ID"}' --json '{"description": "v2 release"}'

Task

Execute this workflow with the following parameters: $ARGUMENTS

  1. Prerequisites Check

    • Verify gws CLI is installed: gws --version
    • Confirm authentication: gws auth status
    • Load required GWS skills (check PREREQUISITE section above)
  2. Parameter Preparation

    • Parse task parameters from $ARGUMENTS
    • Validate required inputs
    • Prepare JSON payloads and flags
  3. Execute Workflow Steps

    • Follow the steps outlined above
    • Replace placeholder IDs with actual values
    • Handle errors and retries
    • Log progress and results
  4. Verify Results

    • Confirm each step completed successfully
    • Verify changes in Google Workspace
    • Report final status and any issues

Tips

  • Use --dry-run flag when available to preview changes
  • Always inspect API schemas before calling: gws schema <service>.<resource>.<method>
  • Check command help for all flags: gws <service> <resource> <method> --help

License: Apache License 2.0 Source: Google Workspace CLI Original Skill: recipe-deploy-apps-script