gws-forms
Read and write Google Forms.
59
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 too minimal, providing only basic domain identification without sufficient detail on capabilities or usage triggers. While 'Google Forms' is a clear identifier, the lack of specific actions and missing 'Use when' guidance significantly limits Claude's ability to appropriately select this skill from a larger skill set.
Suggestions
Add a 'Use when...' clause with trigger terms like 'survey', 'questionnaire', 'Google form', 'form responses', 'collect feedback'
Expand specific capabilities beyond 'read and write' to include actions like 'create questions', 'analyze responses', 'share forms', 'edit form settings'
Include file/format indicators if applicable, such as mentioning integration with Google Sheets for responses
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Forms) and two actions (read and write), but lacks comprehensive detail about specific capabilities like creating questions, analyzing responses, or managing form settings. | 2 / 3 |
Completeness | Answers 'what' minimally but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | 'Google Forms' is a natural keyword users would say, but missing common variations like 'survey', 'questionnaire', 'form responses', or 'Google form'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Google Forms' is fairly specific and distinguishable from generic document skills, but could potentially overlap with other Google Workspace skills or general form-handling skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that effectively leverages the shared GWS skill pattern. Its main weakness is the lack of concrete executable examples for common operations like creating a form with items or batch updating, which would significantly improve actionability. The implicit multi-step workflow for form creation could be made more explicit.
Suggestions
Add a concrete example showing the two-step form creation workflow: create empty form, then batchUpdate to add items with actual --params/--json syntax
Include at least one complete batchUpdate example showing how to add a question or modify form settings
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean content that assumes Claude's competence. No unnecessary explanations of what Google Forms is or how APIs work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete CLI commands and method names, but lacks executable examples showing actual usage with --params or --json flags. The batchUpdate and create methods would benefit from concrete examples. | 2 / 3 |
Workflow Clarity | The create method documentation hints at a multi-step workflow (create then update to add items) but doesn't provide explicit sequenced steps or validation checkpoints. The discovery section is clear but the actual form manipulation workflow is implicit. | 2 / 3 |
Progressive Disclosure | Excellent structure with clear prerequisite reference to shared skill, well-organized sections, and appropriate use of --help and gws schema for deeper discovery. One-level-deep reference to gws-shared/SKILL.md is properly signaled. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Reviewed
Table of Contents
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.