gws-apps-script

What This Skill Does

The gws-apps-script skill provides a powerful command-line interface for OpenClaw to interact with the Google Apps Script API. It enables users to automate the management, deployment, and execution of Google Apps Script projects directly from their workspace. The skill supports granular operations such as creating new projects, fetching existing metadata and project contents, updating code, and managing deployments and versions. By integrating with OpenClaw, this skill acts as a bridge between your local development environment and your Google Cloud projects, allowing for seamless synchronization and execution of serverless scripts that automate tasks across the Google Workspace ecosystem.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/googleworkspace-bot/gws-apps-script Before executing commands, ensure you have initialized your Google Workspace authentication by running gws generate-skills to satisfy the prerequisites defined in ../gws-shared/SKILL.md. Always review the security guidelines provided in the shared configuration before enabling sensitive operations.

Use Cases

This skill is ideal for developers and power users who need to automate Google Workspace workflows. Common use cases include:

• Automated Deployment: Programmatically pushing updated script code to production environments to ensure consistent behavior across team projects.
• Monitoring and Auditing: Retrieving process execution logs and metrics to analyze script usage patterns, track active users, and troubleshoot performance bottlenecks.
• Environment Syncing: Using the getContent and updateContent methods to maintain local project backups or sync script versions between different Google Cloud projects.
• Trigger-based Execution: Running specific script functions remotely to perform data processing, sheet manipulation, or email automation without needing to open the browser-based editor.

Example Prompts

1. "Check the current status and execution metrics for my Apps Script project with ID 1abc-2def-3ghi."
2. "Update the project content for my automation script with the latest local source files from my directory."
3. "List all recent executions and process statuses for the 'CustomerOnboarding' script to check for potential errors."

Tips & Limitations

• Discovering Commands: Always use gws apps-script --help to explore available resources and gws schema apps-script.<resource>.<method> to understand parameter requirements before making calls. This prevents runtime errors and helps in constructing accurate --params flags.
• Auth Context: The skill relies heavily on the gws-shared authentication layer. Ensure your service account or user credentials have the necessary Scopes (e.g., https://www.googleapis.com/auth/script.projects and https://www.googleapis.com/auth/script.deployments) enabled.
• HEAD Version: Be cautious with updateContent, as it modifies the HEAD version used in the editor and trigger environments. Always test changes in a sandbox project first.
• Documentation: Refer to the official Google Apps Script API documentation if you are unsure about the specific JSON structure required for updates.