← Back to Skills Marketplace
googleworkspace-bot

Gws Forms

by googleworkspace-bot · GitHub ↗ · v1.0.12 · MIT-0
cross-platform ⚠ suspicious
506
Downloads
0
Stars
13
Active Installs
13
Versions
Install in OpenClaw
/install gws-forms
Description
Read and write Google Forms.
README (SKILL.md)

forms (v1)

PREREQUISITE: Read ../gws-shared/SKILL.md for auth, global flags, and security rules. If missing, run gws generate-skills to create it.

gws forms \x3Cresource> \x3Cmethod> [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:

# Browse resources and methods
gws forms --help

# Inspect a method's required params, types, and defaults
gws schema forms.\x3Cresource>.\x3Cmethod>

Use gws schema output to build your --params and --json flags.

Usage Guidance
This skill looks like a thin wrapper around a 'gws' CLI for Google Forms, but its SKILL.md tells the agent to read an external ../gws-shared/SKILL.md for authentication and rules while the registry lists no credentials or config paths. Before installing, verify: 1) where and how the 'gws' CLI gets authenticated (local OAuth cache, service account files, or env vars), 2) whether a ../gws-shared/SKILL.md exists in your environment and what secrets it contains, and 3) the provenance and trustworthiness of the 'gws' binary (who built it and where it came from). If you can't confirm those, run the skill in a sandboxed environment and avoid providing broad Google credentials. Ask the publisher to declare required env vars/config paths or to bundle clear auth instructions so you can audit exactly which credentials the skill will use.
Capability Analysis
Type: OpenClaw Skill Name: gws-forms Version: 1.0.12 The gws-forms skill is a standard wrapper for interacting with the Google Forms API via a 'gws' CLI tool. The SKILL.md file provides legitimate instructions for resource management (create, get, batchUpdate) and discovery commands (gws schema) without any evidence of malicious intent, data exfiltration, or prompt injection.
Capability Assessment
Purpose & Capability
Name/description (Google Forms read/write) align with requiring the 'gws' CLI; asking for a gws binary is reasonable. However, the skill manifest declares no credentials or config paths while the SKILL.md explicitly instructs the agent to read a sibling file (../gws-shared/SKILL.md) for auth and security rules, which is not declared in the registry metadata.
Instruction Scope
Runtime instructions tell the agent to run 'gws forms ...' and to inspect schemas — appropriate for a CLI-backed Forms skill. But they also instruct the agent to read ../gws-shared/SKILL.md for authentication and security rules; that directive requires accessing a file outside the skill and potentially exposes or depends on credentials/config the registry does not list.
Install Mechanism
Instruction-only skill with no install spec and no code files means nothing is downloaded or written by the skill itself — low install risk. The security surface is the external 'gws' binary and whatever it does.
Credentials
The skill declares no required environment variables or primary credential, yet the SKILL.md defers authentication to an external shared SKILL.md. That omission means the registry metadata doesn't tell you what secrets or local config will actually be used (OAuth tokens, service account keys, or stored CLI credentials).
Persistence & Privilege
always:false and no install steps are normal. Still, instructions explicitly reference another skill's file path (../gws-shared/SKILL.md), which implies read access to sibling skill configuration; the manifest did not declare any cross-skill config access, creating a privilege/visibility gap.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install gws-forms
  3. After installation, invoke the skill by name or use /gws-forms
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.12
- Updated skill metadata version from 0.22.4 to 0.22.5 in SKILL.md.
v1.0.11
- Updated skill version from 0.22.3 to 0.22.4 in metadata.
v1.0.10
- Updated metadata version from 0.22.2 to 0.22.3 in SKILL.md.
v1.0.9
- Updated metadata version from 0.22.1 to 0.22.2 in SKILL.md.
v1.0.8
- Updated version metadata from 0.22.0 to 0.22.1 in SKILL.md. - No changes to functionality or documentation content.
v1.0.7
- Updated version number in SKILL.md from 0.21.2 to 0.22.0. - No functional or documentation changes; version metadata only.
v1.0.6
- Updated SKILL.md metadata version from 0.21.1 to 0.21.2. - No functional or documentation changes to usage or API details.
v1.0.5
- Updated version in SKILL.md from 0.20.1 to 0.21.1. - Documentation only update; no changes to commands or functionality.
v1.0.4
- Updated version number in SKILL.md from 0.20.0 to 0.20.1. - No functional or documentation changes; version metadata updated only.
v1.0.3
- Bumped metadata version from 0.19.0 to 0.20.0 in SKILL.md. - No other content or functional changes.
v1.0.2
- Updated the SKILL.md metadata to set the version under the metadata block and removed the top-level version field. - No functional or user-facing changes to commands or API documentation.
v1.0.1
- Fix YAML list formatting under metadata.requires.bins in SKILL.md. - No changes to logic or functionality; documentation formatting only.
v1.0.0
Initial release of gws-forms - Provides commands to read and write Google Forms from the CLI. - Supports creating, updating, and retrieving forms and responses. - Includes operations for batch updates, publish settings, and resource watches. - Integrated help and schema inspection for command discovery and usage.
Metadata
Slug gws-forms
Version 1.0.12
License MIT-0
All-time Installs 13
Active Installs 13
Total Versions 13
Frequently Asked Questions

What is Gws Forms?

Read and write Google Forms. It is an AI Agent Skill for Claude Code / OpenClaw, with 506 downloads so far.

How do I install Gws Forms?

Run "/install gws-forms" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Gws Forms free?

Yes, Gws Forms is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Gws Forms support?

Gws Forms is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Gws Forms?

It is built and maintained by googleworkspace-bot (@googleworkspace-bot); the current version is v1.0.12.

💬 Comments