Gws Script

Manage Google Apps Script projects.

Security Scan

The skill's commands align with managing Google Apps Script, but it relies on an unstated external auth/file (../gws-shared/SKILL.md) and requests no credentials while clearly needing Google auth — this mismatch is concerning.

Purpose & Capability

Name/description and the listed gws CLI commands match the stated purpose (managing Apps Script). Requiring the 'gws' binary is reasonable. However, the skill does not declare any credentials or config paths even though Apps Script management normally requires Google OAuth/service-account credentials or tooling (gcloud/ADC). That omission is unexpected.

Instruction Scope

The runtime instructions explicitly tell the agent to read '../gws-shared/SKILL.md' for auth, global flags, and security rules, or to run 'gws generate-skills' to create it. That requires reading a relative file outside this skill bundle (an undeclared external dependency). The instructions do not document what auth artifacts are used or where credentials are stored, which gives the agent broad discretion to load external config.

Install Mechanism

There is no install spec and no code files (instruction-only), so nothing is written to disk by the skill itself. Requiring the 'gws' binary is the only runtime dependency and is proportionate.

Credentials

The skill declares no required environment variables or primary credential, but managing Google Apps Script normally requires Google credentials. The instructions refer to an external shared SKILL.md for auth, yet that file is not part of this package and its requested credentials are unknown. Absence of declared secrets where they are expected is a red flag.

Persistence & Privilege

The skill does not request always:true and is user-invocable. It does not request persistent presence or modify other skills. No elevated persistence privileges are declared.

What to consider before installing

Before installing: (1) Inspect the referenced ../gws-shared/SKILL.md — it may request or instruct use of Google credentials; do not proceed unless you can review it. (2) Verify the origin and integrity of the 'gws' binary (where it comes from, checksums, vendor). (3) Confirm exactly which Google credentials (OAuth tokens, service account key files, gcloud ADC) the tool will use and where they are stored; ensure least-privilege scopes. (4) Be cautious running the skill if you cannot review the external shared file or the 'gws' binary—run in an isolated environment or container first. (5) If you want to proceed, prefer providing a dedicated, limited-scope service account and avoid reusing broad user credentials.

script (v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws script <resource> <method> [flags]

Helper Commands

Command	Description
+push	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:

# Browse resources and methods
gws script --help

# Inspect a method's required params, types, and defaults
gws schema script.<resource>.<method>

Use gws schema output to build your --params and --json flags.