Retrieve and review responses from a Google Form.
67
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-collect-form-responses/SKILL.mdQuality
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 minimal and lacks a 'Use when...' clause, which is critical for skill selection. While it correctly identifies the domain (Google Forms) and basic actions, it needs more specific capabilities listed and explicit trigger conditions to help Claude distinguish it from other data retrieval or survey-related skills.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Google Form responses', 'survey results', 'form submissions', 'Google Forms data'.
List more specific capabilities such as 'summarize response statistics, filter by question, export form data, analyze survey trends'.
Include file type or platform variations users might mention, such as 'Google Forms', 'form survey', or 'Google Sheets responses'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Form) and two actions (retrieve and review responses), but lacks additional specific actions like exporting data, analyzing trends, or filtering submissions. | 2 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also minimal, warranting a 1. | 1 / 3 |
Trigger Term Quality | Includes 'Google Form' and 'responses' which are natural terms, but misses common variations like 'form submissions', 'survey results', 'Google Forms', or 'form data'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifying 'Google Form' provides some distinctiveness, but 'retrieve and review responses' is generic enough that it could overlap with other survey/form tools or general data retrieval skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%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-crafted, concise skill that provides clear, actionable CLI commands for retrieving Google Form responses. Its main strength is brevity and specificity. The only minor weakness is the lack of any error handling or validation guidance (e.g., handling empty responses or invalid form IDs), though this is less critical for a read-only operation.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Forms are or how they work. Every line serves a purpose and assumes Claude's competence. | 3 / 3 |
Actionability | Provides specific, copy-paste ready CLI commands with clear parameter syntax. Each step has a concrete executable command with placeholder values that are self-explanatory. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and logically ordered (find form → get details → get responses). However, there are no validation checkpoints or error handling guidance (e.g., what if the form ID is invalid or no responses exist). | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references given the simplicity. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%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 | |
a3768d0
Table of Contents
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.