recipe-collect-form-responses
Retrieve and review responses from a Google Form.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-collect-form-responses65
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 brief and lacks explicit trigger guidance, which is critical for skill selection. While it identifies the domain (Google Forms) and basic actions, it fails to provide comprehensive capabilities or a 'Use when...' clause that would help Claude choose this skill appropriately.
Suggestions
Add a 'Use when...' clause with trigger terms like 'form responses', 'survey results', 'Google Forms submissions', 'form data'
Expand the capabilities list to include specific actions like 'export to spreadsheet', 'analyze response patterns', 'summarize submissions', or 'filter by date'
Include file type or format mentions if applicable (e.g., 'Google Sheets export', 'CSV download')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Form) and two actions (retrieve, review responses), but lacks comprehensive detail about what 'review' entails or other capabilities like exporting, analyzing, or summarizing. | 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. | 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 data', or 'form answers'. | 2 / 3 |
Distinctiveness Conflict Risk | Mentions 'Google Form' specifically which helps distinguish it, but could overlap with general Google Workspace skills or other form/survey tools without clearer boundaries. | 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 checking Google Form responses. The content is appropriately minimal for the task scope, though it could benefit from brief guidance on handling edge cases like empty responses or invalid form IDs.
Suggestions
Add a brief note on expected output or what to do if no responses are returned
Consider adding error handling guidance for invalid form IDs
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what forms are or how they work. Every line serves a purpose with clear, copy-paste ready commands. | 3 / 3 |
Actionability | Provides fully executable CLI commands with proper syntax including parameter formatting. Commands are copy-paste ready with clear placeholders (FORM_ID) that are self-explanatory. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced and numbered, but this is a read-only operation that could benefit from noting what to do if no responses exist or if the form ID is invalid. No validation/error handling mentioned. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. Clear prerequisite callout, concise steps, and no need for external references given the scope. | 3 / 3 |
Total | 11 / 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.