Google Apps Script: Manage and execute Apps Script projects.
Scanned 5/27/2026
Install via CLI
openskills install pleaseai/claude-code-plugins---
name: gws-apps-script
version: 1.0.0
description: "Google Apps Script: Manage and execute Apps Script projects."
metadata:
openclaw:
category: "productivity"
requires:
bins: ["gws"]
cliHelp: "gws apps-script --help"
---
# apps-script (v1)
> **PREREQUISITE:** Read `../gws-shared/SKILL.md` for auth, global flags, and security rules. If missing, run `gws generate-skills` to create it.
```bash
gws apps-script <resource> <method> [flags]
```
## Helper Commands
| Command | Description |
|---------|-------------|
| [`+push`](../gws-apps-script-push/SKILL.md) | Upload local files to an Apps Script project |
## API Resources
### processes
- `list` — List information about processes made by or on behalf of a user, such as process type and current status.
- `listScriptProcesses` — List information about a script's executed processes, such as process type and current status.
### projects
- `create` — Creates a new, empty script project with no script files and a base manifest file.
- `get` — Gets a script project's metadata.
- `getContent` — Gets the content of the script project, including the code source and metadata for each script file.
- `getMetrics` — Get metrics data for scripts, such as number of executions and active users.
- `updateContent` — Updates the content of the specified script project. This content is stored as the HEAD version, and is used when the script is executed as a trigger, in the script editor, in add-on preview mode, or as a web app or Apps Script API in development mode. This clears all the existing files in the project.
- `deployments` — Operations on the 'deployments' resource
- `versions` — Operations on the 'versions' resource
### scripts
- `run` —
## Discovering Commands
Before calling any API method, inspect it:
```bash
# Browse resources and methods
gws apps-script --help
# Inspect a method's required params, types, and defaults
gws schema apps-script.<resource>.<method>
```
Use `gws schema` output to build your `--params` and `--json` flags.
No comments yet. Be the first to comment!
Playbook for creating and editing uCoz landing pages via MCP tools (`templates_tool`, `ftp_tool`, `modules_tool`). Use for tasks such as: "build a landing page", "update the homepage as a landing page", "create a promo page on the homepage", "add a lead form / menu / SEO to the homepage". Homepage: `page_list`, `page_get`; first publish — `page_update` with full `page_tmpl`; HTML edits after generation — `patch_template` (module_id=2, template_id=1), not `update_template`. Activate the mail f...
Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
Digital Audio Workstation usage, music composition, interactive music systems, and game audio implementation for immersive soundscapes.
Instantly.ai cold email outreach API - manage campaigns, leads, accounts, and analytics. Use for cold email automation, lead management, campaign creation/monitoring, and email account warmup.
Run a single Terminal-Bench problem through Paperclip in a bounded, human-in-the-loop improvement cycle until the smoke passes, the board rejects the next fix, the iteration budget is exhausted, or a real blocker is named. Each iteration runs a bounded smoke against an isolated Paperclip App worktree, captures artifacts, diagnoses the exact stop point with `/diagnose-why-work-stopped`, requests board confirmation before any product fix, then reruns against the same worktree. Use whenever an i...