gws-script-push

Synchronize local Apps Script files to a remote project by ID.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes local Apps Script files with a remote Apps Script project by ID.

Core Features & Use Cases

  • Uploads local script files to a Google Apps Script project by ID.
  • Supports .gs, .js, .html, and appsscript.json; can target a specific local directory; fully replaces remote project contents.
  • Includes a safety CAUTION note that requires user confirmation before execution.

Quick Start

Push your local Apps Script project files to the remote project by ID, optionally specifying the directory to upload.

Frequently Asked Questions about gws-script-push

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

FAQPage Schema
How do I upload local Apps Script files to a remote Google Apps Script project?

You can upload local Apps Script files to a remote project by providing the specific Script ID, which synchronizes your local workspace files directly to the remote Google Apps Script project.

What file types are supported when pushing code to a Google Apps Script project?

Pushing code to a Google Apps Script project supports .gs, .js, .html, and appsscript.json file formats, ensuring your local script files and manifest are fully synchronized with the remote project.

Can I fully replace the contents of a remote Apps Script project during an upload?

Yes, uploading local Apps Script files can fully replace the remote project contents, applying batch updates or a complete project replacement by targeting a specific local directory and the Script ID.

Does pushing local files to an Apps Script project require confirmation before writing?

Yes, pushing local files to an Apps Script project enforces a safety prompt that requires user confirmation before execution, ensuring you approve the batch updates before any changes are written to the remote project.

Is a Script ID required to synchronize local files with a remote Apps Script project?

Yes, a Script ID is required to synchronize local files with a remote Apps Script project, as it targets the exact remote destination for applying your local workspace updates and replacements.

Can I target a specific local directory when uploading files to an Apps Script project?

Yes, you can target a specific local directory when uploading files to an Apps Script project, allowing you to push only the relevant .gs, .js, .html, and appsscript.json files from your workspace.