gws-forms

Read and write Google Forms.

Quality

45%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/gws-forms/SKILL.md

Quality

Discovery

32%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is extremely terse, identifying only the domain (Google Forms) and two broad actions (read, write). It lacks a 'Use when...' clause, specific capability details, and natural trigger term variations, making it insufficient for reliable skill selection among many options.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about creating, editing, or reading Google Forms, surveys, or questionnaires.'

List more specific concrete actions such as 'create forms, add questions, read responses, update form settings, share forms'.

Include natural keyword variations like 'survey', 'questionnaire', 'form responses', 'Google Form' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Forms) and two actions (read and write), but does not list more specific concrete actions like creating questions, analyzing responses, editing form settings, etc.	2 / 3
Completeness	It answers 'what' at a basic level (read and write Google Forms) but completely lacks any 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also quite thin, placing this at 1.	1 / 3
Trigger Term Quality	'Google Forms' is a strong natural keyword users would say, but the description lacks common variations or related terms like 'survey', 'questionnaire', 'form responses', or 'Google Form'.	2 / 3
Distinctiveness Conflict Risk	'Google Forms' is fairly specific and distinguishable from other skills, but the generic 'read and write' phrasing could overlap with other Google Workspace or form-related skills without clearer scoping.	2 / 3
	Total	7 / 12 Passed

Implementation

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides a reasonable overview of the Google Forms CLI interface with good progressive disclosure via the shared skill reference and self-discovery commands. However, it lacks concrete executable examples of common operations (creating a form, adding items via batchUpdate) and the two-step create workflow is described in prose rather than as a clear actionable sequence.

Suggestions

Add a concrete example showing the two-step form creation workflow: a `gws forms forms create` command followed by a `gws forms forms batchUpdate` command with actual --params/--json values.

Present the create-then-update workflow as a numbered sequence with explicit steps rather than embedding it in the API description prose.

Trim the 'Important' note in the create method to just the essential constraint: 'Only title/document_title are set on create; use batchUpdate to add items and settings.'

Dimension	Reasoning	Score
Conciseness	Mostly efficient, but the long explanation about forms.create (copied from API docs about which fields are copied and the two-step process) is somewhat verbose. The 'Important' note could be tightened.	2 / 3
Actionability	Provides the CLI pattern and discovery commands, but lacks concrete executable examples of actual form creation or batchUpdate calls with --params/--json flags. The user knows how to discover commands but not how to execute common tasks.	2 / 3
Workflow Clarity	The create method description mentions a two-step workflow (create then update to add items), but it's buried in prose rather than presented as a clear numbered sequence. No validation steps are mentioned for verifying form creation succeeded.	2 / 3
Progressive Disclosure	Appropriately structured as a concise overview that references the shared skill file for auth/security, uses gws schema for self-discovery, and keeps content brief. The prerequisite reference is one level deep and clearly signaled.	3 / 3
	Total	9 / 12 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	10 / 11 Passed

Repository: googleworkspace/cli
Commit: c7c6646

Reviewed: about 10 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.