Infra, Ops & WorkflowSûr100100/100
Gws Script
Manage Google Apps Script projects.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ npx arboris-cli@latest install gws-scriptGoogle Workspace
affaan-m/ECC
Contenu à copier
---
name: gws-script
description: "Manage Google Apps Script projects."
metadata:
origin: Google Workspace
version: 0.22.5
openclaw:
category: "productivity"
requires:
bins:
- gws
cliHelp: "gws script --help"
---
# 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 script <resource> <method> [flags]
```
## Helper Commands
| Command | Description |
|---------|-------------|
| [`+push`](../gws-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 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.Colle ce Markdown dans ton agent ou utilise les boutons ci-dessus pour l’écrire dans ton projet.
Ce que fait Gws Script
`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.
`create` — Creates a new, empty script project with no script files and a base manifest file.
`get` — Gets a script project's metadata.
Comment utiliser Gws Script
1
Copie le prompt
Un clic copie le prompt packagé (ou l'envoie à ton agent).
2
L'agent installe le skill
Il ajoute le SKILL.md et ses ressources à ton projet.
3
Activation automatique
Le skill s'active dès que le contexte correspond.
Déclencheurs pour Gws Script
Dis simplement à ton agent quelque chose comme :
Applique le skill gws-script à cette tâche
Utilise gws-script pour améliorer cette implémentation
Passe en revue ce sujet avec gws-script
Skills liés à Gws Script
Add CLI Command (.NET) — SDK Github
Add or change a dotnet CLI command, subcommand, or option across the relevant CLI projects. USE FOR: adding or changing a dotnet CLI command/subcommand, adding a new Option<T> or Argument<T>, registering a subcommand in the command tree, changing an option's help description or a command's runtime message, wiring a command parser, or updating --help output.Add CLI Command (.NET) — Github
Add or change a dotnet CLI command, subcommand, or option across the relevant CLI projects. USE FOR: adding or changing a dotnet CLI command/subcommand, adding a new Option<T> or Argument<T>, registering a subcommand in the command tree, changing an option's help description or a command's runtime message, wiring a command parser, or updating --help output.Add Dotnet Aot Command (.NET)
Add, enable, or review a dotnet CLI command or feature in the Native AOT CLI (src/Cli/dotnet-aot) and prove its compatibility. USE FOR: migrating a command or option to AOT, reviewing an AOT migration PR, defining conservative eligibility and managed fallback, changing AotSourceFiles.props or AotDependencies.props, validating AOT/managed parity, NativeAOT-publishing tests, checking binary-size impact, or using the dn harness and separated SDK layout. DO NOT USE FOR: resolving IL trim/AOT analyzer warnings alone (use dotnet-aot-compat), running dotnet.Tests incrementally (use incremental-test), or pure managed CLI work.