# Manage Google Forms with the gws CLI

Managing Google Forms manually makes repeatable administration slow and error-prone. This skill guides reliable form creation, updates, retrieval, publishing, response operations, and schema discovery.

## Install

```bash
npx skillstore add googleworkspace/gws-forms
```

## Metadata

- Status: approved
- Slug: googleworkspace-gws-forms
- Version: 0.23.0
- Author version: 0.23.0
- Skillstore revision: r2
- Version status: valid
- Tree hash: 79f8dc81b863685a314149a54d52f5f22b65302527723bf1414ec506aad00ed9
- Author: googleworkspace
- GitHub username: googleworkspace
- License: MIT
- Repository: https://github.com/googleworkspace/cli/tree/main/skills/gws-forms/
- Ref: 286d37c9c189ddd1aafd3548415fb031d1df79d5
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands, filesystem
- Quality score: 80
- Quality tier: silver
- Public page: https://skillstore.pages.dev/skills/googleworkspace-gws-forms
- Manifest: https://skillstore.pages.dev/api/skills/googleworkspace-gws-forms/manifest

## Capabilities

- Create an empty Google Form with a title and optional document title.
- Retrieve an existing Google Form.
- Apply multiple form changes through batchUpdate.
- Update supported form publishing settings.
- Work with form response and watch resources.
- Inspect available methods, parameters, types, and defaults before making API calls.

## Use Cases

- Create a standard form: Create an empty form, then add approved questions and settings through a separate batch update.
- Automate form maintenance: Inspect method schemas and apply repeatable updates to existing forms with validated parameters.
- Manage response workflows: Discover response and watch operations for recurring collection and monitoring tasks.

## Prompt Templates

### Explore Forms commands

```
Show the available Google Forms resources and explain how to inspect a method before using it.
```

### Create an empty form

```
Create a Google Form titled [title] with the optional document title [document title]. Confirm the planned action first.
```

### Plan a batch update

```
Inspect the batchUpdate schema for form [form ID], then plan changes for [questions or settings]. Validate every required parameter.
```

### Design a monitored response workflow

```
Inspect response and watch methods for form [form ID]. Propose a workflow for [goal], including required parameters and operational limits.
```

## Limitations

- The gws CLI and its authentication setup must already be available.
- Form creation copies only the title and optional document title.
- Items, descriptions, and settings require a later update operation.
- Legacy forms do not support publish settings through this API.

## Best Practices

- Inspect each method schema before building parameters or request data.
- Create the empty form first, then add items and settings through an update.
- Confirm form identifiers and publishing changes before modifying remote resources.

## Anti Patterns

- Do not include questions or settings in the initial create request.
- Do not guess parameter names, types, or defaults without inspecting the method schema.
- Do not apply publish settings to legacy forms that lack the required field.

## Security Audit

- Audited at: 2026-08-05T11:00:52.177\+00:00
- Summary: All 12 external-command alerts are false positives caused by Markdown backticks and fenced CLI examples, not executable Ruby or shell substitution. The path reference is fixed documentation for a sibling skill, with no user-controlled traversal or malicious intent.

## Stats

- Views: 56
- Downloads: 7
- Favorites: 0
- Popularity score: 0