CtrlK
BlogDocsLog inGet started
Tessl Logo

recipe-collect-form-responses

Retrieve and review responses from a Google Form.

67

Quality

60%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

SecuritybySnyk

Advisory

Suggest reviewing before use

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-collect-form-responses/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

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 underspecified. While it correctly identifies the domain (Google Forms) and a basic action (retrieve and review responses), it lacks a 'Use when...' clause, detailed capability listing, and sufficient trigger terms to reliably distinguish it from other skills in a large skill library.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'Google Forms', 'form responses', 'survey results', 'form submissions', 'form data'.

Expand the capability list with specific actions such as 'summarize response data, filter by question, export results, analyze trends in form submissions'.

Include common user phrasing variations like 'check my form answers', 'pull survey responses', or 'view Google Form results' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Google Form) and two actions (retrieve and review responses), but lacks detail on what 'review' entails—no mention of specific capabilities like summarizing, filtering, exporting, or analyzing response data.

2 / 3

Completeness

Describes what the skill does (retrieve and review responses) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per rubric guidelines, a missing 'Use when...' clause caps completeness at 2, and the 'what' portion is also thin, warranting a score of 1.

1 / 3

Trigger Term Quality

Includes 'Google Form' and 'responses' which are natural terms, but misses common variations like 'Google Forms', 'form responses', 'survey results', 'form submissions', or 'form data'.

2 / 3

Distinctiveness Conflict Risk

Specifying 'Google Form' provides some distinctiveness from generic document or data skills, but could overlap with broader Google Workspace skills or survey/form processing skills without clearer scoping.

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 with full actionability. The only minor weakness is the lack of error handling guidance or notes on interpreting the output, though for a read-only operation this is a minor concern.

DimensionReasoningScore

Conciseness

Very lean and efficient. No unnecessary explanations of what Google Forms are or how APIs work. Every line serves a purpose.

3 / 3

Actionability

Provides specific, copy-paste ready CLI commands with exact flags and parameter formats. Each step has a concrete executable command.

3 / 3

Workflow Clarity

Steps are clearly sequenced and logical (find form ID → get details → get responses), but this is a read-only operation so validation isn't critical. However, there's no guidance on what to do if a step fails (e.g., no forms found, invalid form ID) which would improve the workflow.

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.

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

10

/

11

Passed

Repository
googleworkspace/cli
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.