gws-apps-script-push

What This Skill Does

The gws-apps-script-push skill is a powerful automation tool designed to bridge the gap between local development environments and Google Apps Script projects. As a professional developer, maintaining code in a browser-based editor can be limiting; this skill allows you to use your preferred local code editors (like VS Code, Sublime Text, or IntelliJ) to write, debug, and structure your Google Apps Script projects, then synchronize them seamlessly to the cloud. By executing a simple CLI command, the skill parses your local directory, identifies supported files (such as .gs, .js, .html, and appsscript.json), and replaces the existing project files on Google's servers with your updated local versions.

Installation

To integrate this functionality into your OpenClaw environment, you must have the base gws framework configured. Once your authentication is handled via the gws-shared prerequisites, execute the following command in your terminal: clawhub install openclaw/skills/skills/googleworkspace-bot/gws-apps-script-push. Ensure that you have the necessary Google Cloud or Workspace permissions enabled for the script project you intend to modify, as this tool requires write-access to your Apps Script environment.

Use Cases

This skill is ideal for developers building complex Google Workspace add-ons, enterprise automation tools, or custom functions for Google Sheets. It is particularly useful for teams who want to incorporate version control systems like Git into their Apps Script workflow, as it allows for pushing tested code from a local feature branch directly to a staging or production script project. It is also perfect for those who require the use of build tools, linters, or TypeScript transpilation, allowing the processed output to be pushed to the Google environment.

Example Prompts

1. "Sync my local project in the src directory to my Apps Script project with ID 1A2B3C4D5E6F7G8H9I0."
2. "Push the current folder's contents to my Apps Script project (ID: SCRIPT_ID)."
3. "I have finished my updates to the web app components; use the push skill to update my Apps Script project now."

Tips & Limitations

• Caution: This command is destructive in nature; it replaces all existing files in the destination project. Always ensure you have a backup of your cloud-based code if needed.
• Automation: The skill intelligently skips internal artifacts like node_modules and hidden files, ensuring only your relevant source code is uploaded.
• Authentication: Always ensure you have run the auth flow described in gws-shared before attempting to push, as the skill relies on the session token generated there.
• Environment: If you have multiple scripts, verify you have the correct project ID; there is no 'undo' button once the push command completes.