Gws Script Push
Upload local Apps Script sources (.gs, .js, .html, appsscript.json) to a Google Apps Script project with the gws CLI.
Overview
gws-script-push is an agent skill for the Build phase that uploads local Apps Script files to a Google Apps Script project using the gws CLI.
Install
npx skills add https://github.com/googleworkspace/cli --skill gws-script-pushWhat is this skill?
- Replaces ALL remote project files from a local directory via `gws script +push`
- Supports .gs, .js, .html, and appsscript.json; skips hidden files and node_modules
- Required `--script` project ID; optional `--dir` (defaults to current directory)
- Documented as a write command—confirm with the user before executing
- Pairs with gws-shared for auth, global flags, and security rules
- Supports 4 file types: .gs, .js, .html, appsscript.json
- Replaces ALL files in the target Apps Script project on push
Adoption & trust: 10.3k installs on skills.sh; 26.9k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
Your Apps Script changes live only on disk and you need a one-command push to the correct Script Project ID.
Who is it for?
Solo builders using gws + agent workflows who version Apps Script locally and deploy by project ID.
Skip if: Exploratory Drive file cleanup or read-only audits—use Drive list recipes instead; also skip without user consent because push replaces all remote files.
When should I use this skill?
User needs to upload local Apps Script sources to an existing Script Project via gws after local edits.
What do I get? / Deliverables
The remote Apps Script project mirrors your local directory’s supported files, ready to run in Google Workspace.
- Remote Apps Script project synced to local directory
Recommended Skills
Journey fit
How it compares
Task integration around the gws CLI—not a hosted MCP server for Google.
Common Questions / FAQ
Who is gws-script-push for?
Builders and operators who already use the Google Workspace `gws` CLI and want agents to deploy Apps Script from a repo folder.
When should I use gws-script-push?
During Build integrations work after local script edits, when you have a Script Project ID and need to sync .gs/.js/.html/appsscript.json to Google.
Is gws-script-push safe to install?
It performs destructive remote overwrites—confirm targets with the user and review the Security Audits panel on this Prism page before granting network/API access.
SKILL.md
READMESKILL.md - Gws Script Push
# script +push > **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it. Upload local files to an Apps Script project ## Usage ```bash gws script +push --script <ID> ``` ## Flags | Flag | Required | Default | Description | |------|----------|---------|-------------| | `--script` | ✓ | — | Script Project ID | | `--dir` | — | — | Directory containing script files (defaults to current dir) | ## Examples ```bash gws script +push --script SCRIPT_ID gws script +push --script SCRIPT_ID --dir ./src ``` ## Tips - Supports .gs, .js, .html, and appsscript.json files. - Skips hidden files and node_modules automatically. - This replaces ALL files in the project. > [!CAUTION] > This is a **write** command — confirm with the user before executing. ## See Also - [gws-shared](../gws-shared/SKILL.md) — Global flags and auth - [gws-script](../gws-script/SKILL.md) — All manage google apps script projects commands