Infra, Ops & WorkflowSûr100100/100
Gws Forms
Read and write Google Forms.
ou envoie-le directement à ton agent.
Installer dans ton projet
$ npx arboris-cli@latest install gws-formsGoogle Workspace
affaan-m/ECC
Contenu à copier
---
name: gws-forms
description: "Read and write Google Forms."
metadata:
origin: Google Workspace
version: 0.22.5
openclaw:
category: "productivity"
requires:
bins:
- gws
cliHelp: "gws forms --help"
---
# forms (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 forms <resource> <method> [flags]
```
## API Resources
### forms
- `batchUpdate` — Change the form with a batch of updates.
- `create` — Create a new form using the title given in the provided form message in the request. *Important:* Only the form.info.title and form.info.document_title fields are copied to the new form. All other fields including the form description, items and settings are disallowed. To create a new form and add items, you must first call forms.create to create an empty form with a title and (optional) document title, and then call forms.update to add the items.
- `get` — Get a form.
- `setPublishSettings` — Updates the publish settings of a form. Legacy forms aren't supported because they don't have the `publish_settings` field.
- `responses` — Operations on the 'responses' resource
- `watches` — Operations on the 'watches' resource
## Discovering Commands
Before calling any API method, inspect it:
```bash
# Browse resources and methods
gws forms --help
# Inspect a method's required params, types, and defaults
gws schema forms.<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 Forms
`batchUpdate` — Change the form with a batch of updates.
`create` — Create a new form using the title given in the provided form message in the request. *Important:* Only the form.info.title and form.info.document_title fields are copied to the new form. All other fields including the form description, items and settings are disallowed. To create a new form and add items, you must first call forms.create to create an empty form with a title and (optional) document title, and then call forms.update to add the items.
`get` — Get a form.
`setPublishSettings` — Updates the publish settings of a form. Legacy forms aren't supported because they don't have the `publish_settings` field.
Comment utiliser Gws Forms
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 Forms
Dis simplement à ton agent quelque chose comme :
Applique le skill gws-forms à cette tâche
Utilise gws-forms pour améliorer cette implémentation
Passe en revue ce sujet avec gws-forms
Skills liés à Gws Forms
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.