Name: google-forms
Rating: 59.2 (1 reviews)
Author: membranedev

google-forms

Google Forms integration. Manage data, records, and automate workflows. Use when the user wants to interact with Google Forms data.

Quality

68%

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-forms/SKILL.md

Quality

Content

75%Weight 40%Scale 1-5

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

The body is highly actionable with executable CLI commands and a clear connection-state workflow, but it opens with unnecessary background on what Google Forms is and has a small section-numbering inconsistency that weakens navigation.

Suggestions

Remove or condense the opening "Google Forms is a survey administration app..." paragraph and the "Use action names and parameters as needed" line, since Claude already knows what Google Forms is.

Fix the step numbering: label the connection steps consistently (e.g., "Step 1: Connect", "Step 2: Search/run actions") so the "skip to Step 2" references resolve.

Dimension	Reasoning	Score
Conciseness	The body opens with an encyclopedia-style paragraph about what Google Forms is ("Google Forms is a survey administration app that is part of the Google Workspace suite...") and includes filler like "Use action names and parameters as needed," concepts Claude already knows, matching the mostly-efficient-but-includes-unnecessary-explanation anchor.	3 / 5
Actionability	Provides copy-paste-ready commands throughout (membrane login, connection ensure, action list/run, request) plus a concrete options table, fully covering the common connect-discover-execute cases.	5 / 5
Workflow Clarity	The connect→poll→READY/CLIENT_ACTION_REQUIRED flow is well sequenced with state-based checkpoints and a re-poll feedback loop, but a labeling gap ("#### 1b" with no labeled Step 1/Step 2, references to an undefined "Step 2") leaves minor navigation gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the content is a single well-sectioned SKILL.md with no nested references; structure is good though slightly long for a single-file overview that could split the connection-state reference table.	4 / 5
	Total	16 / 20 Passed

Description

62%Weight 40%Scale 1-5

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 answers both what and when and is clearly niche-bound to Google Forms, but the capability language ("Manage data, records, and automate workflows") is generic and the trigger terms omit natural synonyms like surveys and responses.

Suggestions

Replace generic verbs with concrete Google Forms actions, e.g. "Create forms and surveys, collect and read responses, and manage form questions."

Expand the trigger clause with natural user phrases: "Use when the user wants to create surveys or quizzes, collect or read form responses, or manage Google Forms data."

Dimension	Reasoning	Score
Specificity	"Manage data, records, and automate workflows" names the Google Forms domain and a couple of actions, but the actions are generic rather than concrete (no "create surveys", "collect responses", "view form results").	3 / 5
Completeness	Has a clear "what" ("Google Forms integration. Manage data, records, and automate workflows") and an explicit "when" ("Use when the user wants to interact with Google Forms data"), but the "when" trigger could be more specific (e.g., mention surveys/responses).	4 / 5
Trigger Term Quality	Contains "Google Forms" and "Google Forms data" but omits natural synonyms users would say like "surveys", "quizzes", "forms", "responses", matching the "some relevant keywords but missing common variations" anchor.	3 / 5
Distinctiveness Conflict Risk	"Google Forms integration" with "Use when the user wants to interact with Google Forms data" carves a clear niche with minimal conflict risk, with only minor overlap potential against general Google Workspace data skills.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/google-forms/SKILL.md
Commit: f484c82

Reviewed: 5 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.