Read and write Google Forms.
a3768d0PREREQUISITE: Read
../gws-shared/SKILL.mdfor auth, global flags, and security rules. If missing, rungws generate-skillsto create it.
gws forms <resource> <method> [flags]
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' resourcewatches — Operations on the 'watches' resourceBefore calling any API method, inspect it:
# 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.
Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/gws-forms · pinned to the source commit
git clone https://github.com/googleworkspace/cli.git
cd cli
git checkout a3768d0e82ad83cca2da97724e46bea4ff0e6dbd
mkdir -p ".claude/skills/gws-forms"
cp -r "skills/gws-forms" ".claude/skills/gws-forms"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit a3768d0e82ad. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b