gws-script

Manage Google Apps Script projects, content, deployments, versions, and executions.

Updated Apr 6, 2026
One-click install
npx skills add https://github.com/cellarwood/figurio --skill gws-script
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gws-script
Source: https://github.com/cellarwood/figurio/tree/main/skills/gws-script
Command: npx skills add https://github.com/cellarwood/figurio --skill gws-script

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a single, CLI-driven interface to manage Google Apps Script projects so developers and operators avoid manual edits in the Apps Script editor and streamline deployments, versioning, and execution monitoring. It consolidates common API operations behind the gws script command and points to shared auth and security rules in the sibling gws-shared skill.

Core Features & Use Cases

  • Project management: create and retrieve script project metadata and full project content.
  • Content operations: get and update project content to sync local source files with Apps Script projects.
  • Deployment & versioning: list and manage deployments and versions to promote stable releases.
  • Process & execution: list script processes, get metrics, and run script functions for automation tasks.
  • Use case: upload a local Apps Script codebase, create a new version, and create a deployment to publish an automated workflow.

Quick Start

Use the gws script command to upload local project files to a target Apps Script project and create a new deployment.

Frequently Asked Questions about gws-script

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I deploy Google Apps Script projects from the command line?

To deploy Google Apps Script projects from the command line, use a CLI-driven interface to upload local project files, create a new version, and generate a deployment for stable releases. This avoids manual edits in the Apps Script editor.

Can I sync local source files with my Apps Script project content?

Yes, you can sync local source files with Apps Script project content by using CLI content operations to get and update project sources. This ensures your local codebase matches the script project without manual editor interactions.

Do I need authenticated Google Workspace credentials to run Apps Script automation?

Yes, authenticated Google Workspace credentials are required to run Apps Script automation. The CLI integrates with these credentials to securely list, create, and manage script projects, deployments, and executions.

What is the best way to monitor Google Apps Script processes and executions?

The best way to monitor Google Apps Script processes and executions is using a CLI tool that lists script processes, retrieves metrics, and runs script functions for automation tasks. This consolidates operations into a single interface.

How does versioning work when managing Google Apps Script deployments?

Versioning for Google Apps Script deployments involves creating distinct versions of your project content to promote stable releases. You can list and manage these versions via the CLI to control which iteration your deployment targets.

Why avoid manual edits in the Google Apps Script editor for deployments?

Avoiding manual edits in the Google Apps Script editor prevents inconsistencies during deployments and versioning. A CLI-driven interface streamlines developer workflows by automating content updates and execution monitoring.