google-forms

Google Forms via gws: create forms, add items, read responses.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/google/google-forms/SKILL.md

Quality

Content

72%Weight 40%Scale 1-3

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

The content is highly actionable with executable commands and clear section organization. Its weak spots are mild duplication of scope/workflow facts across sections and the absence of an explicit validation feedback loop for the batch batchUpdate operation.

Suggestions

De-duplicate the scope guidance: state the forms.get-requires-body-scope rule once and reference it, rather than repeating it in Prerequisites, Read responses, and Rules.

Add an explicit validate-after step for batchUpdate (e.g. re-run forms.get to confirm items landed and report any errors before proceeding), since it is an atomic batch operation.

Tighten the Prerequisites onboarding prose so the multi-bullet setup flow is more concise without losing the decision branches.

Dimension	Reasoning	Score
Conciseness	The body is dense and fluff-free, but the same facts are restated across sections (the forms.get-rejects-responses-only-scope note appears in Prerequisites, Read responses, and Rule #5; the two-step create is repeated in Rule #1), so it could be tightened; not 3 because of this duplication.	2 / 3
Actionability	Every workflow is shown as fully executable gws commands with complete JSON payloads, real flags (--page-all, --params, --json), and copy-paste-ready params; not 2 because nothing is pseudocode or missing key details.	3 / 3
Workflow Clarity	Multi-step flows are clearly sequenced (two-step create with a "Capture the formId" checkpoint, decision-branched onboarding), but batchUpdate is a batch operation with no explicit validate-after/feedback step, and the rubric caps batch-operation workflows at 2 when validation is missing; not 1 because sequencing and checkpoints are present.	2 / 3
Progressive Disclosure	The skill is a single-domain, self-contained document with clean, well-signaled sections (Prerequisites, When to Use, Quick Reference, Rules) and no nested or broken external references, fitting the simple-skill allowance for well-organized self-contained content; not 2 because nothing is poorly signaled or inappropriately inline.	3 / 3
	Total	10 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 specific and distinctive, naming concrete actions on a clearly bounded domain. Its main weakness is the missing explicit "Use when..." trigger guidance, which caps completeness and leaves trigger-term coverage partial.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user asks to create a Google Form (survey, signup, feedback, RSVP) or read its responses."

Broaden natural trigger terms to include common variations users say, such as "survey", "questionnaire", "signup", or "RSVP".

Dimension	Reasoning	Score
Specificity	"create forms, add items, read responses" lists three concrete actions on a named domain (Google Forms via gws), matching the multiple-specific-actions anchor; not 2 because the actions are concrete and comprehensive rather than partial.	3 / 3
Completeness	The description clearly answers "what" but has no "Use when..." clause or explicit trigger guidance; per the rubric a missing explicit-when clause caps completeness at 2, so it is not 3.	2 / 3
Trigger Term Quality	"Google Forms" and "forms" are natural terms a user would say, but common variations like "survey", "signup", "feedback", or "RSVP" are missing (they appear in the body, not the description), so coverage is partial rather than full.	2 / 3
Distinctiveness Conflict Risk	"Google Forms via gws" is a clear, narrow niche distinct from sibling skills (Sheets, Docs, Slides), so it is unlikely to trigger for the wrong skill; not 2 because it does not meaningfully overlap with similar skills.	3 / 3
	Total	10 / 12 Passed

Validation

87%

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 — 14 / 16 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

	Total	14 / 16 Passed

Repository: Open-Curiosity/gini-agent
Path: skills/google/google-forms/SKILL.md
Commit: 6c5d85e

Reviewed: 12 days 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.