← Back to Skills Marketplace
Gws Apps Script Push
by
googleworkspace-bot
· GitHub ↗
· v1.0.0
300
Downloads
0
Stars
2
Active Installs
1
Versions
Install in OpenClaw
/install gws-apps-script-push
Description
Google Apps Script: Upload local files to an Apps Script project.
README (SKILL.md)
apps-script +push
PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
Upload local files to an Apps Script project
Usage
gws apps-script +push --script \x3CID>
Flags
| Flag | Required | Default | Description |
|---|---|---|---|
--script |
✓ | — | Script Project ID |
--dir |
— | — | Directory containing script files (defaults to current dir) |
Examples
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 — Global flags and auth
- gws-apps-script — All manage and execute apps script projects commands
Usage Guidance
Before installing or enabling this skill: 1) Confirm the provenance and integrity of the 'gws' CLI (where it comes from and whether you trust it). 2) Open and review ../gws-shared/SKILL.md (or run gws generate-skills as suggested) to see what authentication method and credentials it requires — do not assume there are no secrets involved. 3) Be aware this command will replace all files in the target Apps Script project (back up the project first). 4) If you are uncomfortable with autonomous agent actions that perform writes, require explicit user confirmation or disable autonomous invocation for this skill. 5) Test with a non-production script/project and a dry-run (if gws supports one) before running against important projects.
Capability Analysis
Type: OpenClaw Skill
Name: gws-apps-script-push
Version: 1.0.0
The skill bundle provides a standard interface for pushing local files to a Google Apps Script project using the 'gws' CLI tool. The documentation in SKILL.md is transparent about its functionality, including a safety warning that it overwrites remote files, and contains no indicators of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
The skill is instruction-only and requires the 'gws' CLI binary, which is coherent with the described function (pushing files to Apps Script). However, the SKILL.md references an external '../gws-shared/SKILL.md' for auth and global flags but this skill's metadata declares no required credentials or config paths, creating a mismatch between declared requirements and the actual authentication dependency.
Instruction Scope
Runtime instructions are limited to invoking the 'gws' CLI to push files and explicitly caution that this is a write operation. They also instruct the agent to read '../gws-shared/SKILL.md' for auth, flags, and security rules — that single external-file dependency expands the agent's read scope beyond the skill's own SKILL.md and could expose or rely on credentials/config not declared here.
Install Mechanism
No install specification and no code files are present — lowest-risk installation model. The skill is instruction-only and will invoke an already-installed 'gws' binary; nothing is downloaded or written by the skill itself.
Credentials
The skill does not declare any required environment variables or primary credentials, yet it explicitly defers authentication to a separate '../gws-shared/SKILL.md'. Because pushing replaces all files in a remote Apps Script project, this operation necessarily requires Google auth tokens/credentials. The omission of declared credential requirements is a discrepancy: users should inspect gws-shared to see exactly what secrets or tokens are read/used.
Persistence & Privilege
always:false and no special persistence requested. The skill doesn't claim to modify other skills' configurations. The primary autonomy concern is the normal platform default (agent can invoke the skill) combined with a destructive write operation — consider requiring user confirmation before autonomous runs.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install gws-apps-script-push - After installation, invoke the skill by name or use
/gws-apps-script-push - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial release: Upload local files to a Google Apps Script project.
- Adds command: gws apps-script +push for uploading files to a specified Apps Script project.
- Supports .gs, .js, .html, and appsscript.json files; skips hidden files and node_modules.
- Accepts --script (project ID, required) and --dir (optional local directory) flags.
- Replaces all files in the target Apps Script project.
- Includes precautions to confirm with user before overwriting project files.
Metadata
Frequently Asked Questions
What is Gws Apps Script Push?
Google Apps Script: Upload local files to an Apps Script project. It is an AI Agent Skill for Claude Code / OpenClaw, with 300 downloads so far.
How do I install Gws Apps Script Push?
Run "/install gws-apps-script-push" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Gws Apps Script Push free?
Yes, Gws Apps Script Push is completely free (open-source). You can download, install and use it at no cost.
Which platforms does Gws Apps Script Push support?
Gws Apps Script Push is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Gws Apps Script Push?
It is built and maintained by googleworkspace-bot (@googleworkspace-bot); the current version is v1.0.0.
More Skills