gws CLI: Google Forms
Read and write Google Forms via the gws CLI, with publish and response APIs
- What
- Read and write Google Forms via the gws CLI, with publish and response APIs
- Cost
- Free
- Needs
- the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — the Google Forms v1 API reference for the `gws` CLI: forms resource (create, get, batchUpdate, setPublishSettings) plus responses and watches operations, with the `gws schema` discovery workflow for building correct flags. Note the real API constraint the skill documents: `create` copies only the title and document title — items, description and settings must be added afterwards via `update`. Read the sibling `googleworkspace-cli-gws-shared` fiche first (auth, global flags, security rules). Distinct from the lot 31 googleworkspace workflow fiches (raw API reference, not a persona workflow). By @googleworkspace, listed here with credit to its creator. Honest caveats: legacy forms aren't supported for publish settings; write operations need the shared confirm-before-executing rule; browser OAuth is free, service accounts need a Google Cloud project. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: the `gws` binary on the PATH; a Google account with browser OAuth (`gws auth login`) or a service account; install the googleworkspace-cli-gws-shared skill first Install "gws CLI: Google Forms" for me. Give my agent the Google Forms API reference for the gws CLI — read and write forms, publish settings, responses Repository: https://github.com/googleworkspace/cli/blob/main/skills/gws-forms/SKILL.md 1. Fetch the SKILL.md file for the googleworkspace-cli-gws-forms skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "googleworkspace-cli-gws-forms". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. `gws auth login`). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.