recipe-create-feedback-form

Create a Google Form for feedback and share it via Gmail.

Quality

52%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-create-feedback-form/SKILL.md

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 concise and names specific Google products, giving it moderate specificity and some natural trigger terms. However, it lacks an explicit 'Use when...' clause, misses common synonym trigger terms like 'survey' or 'questionnaire', and the capability list is too brief to fully distinguish it from related skills.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a survey, questionnaire, or feedback form and distribute it via email.'

Include additional trigger terms and synonyms such as 'survey', 'questionnaire', 'form link', 'send email', and 'collect responses'.

Expand the capability list with more specific actions, e.g., 'Creates Google Forms with custom questions, configures response settings, and sends the form link via Gmail to specified recipients.'

Dimension	Reasoning	Score
Specificity	Names the domain (Google Forms, Gmail) and two actions (create, share), but does not list more granular capabilities like question types, response collection, or email customization.	2 / 3
Completeness	Describes what the skill does but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is also thin, so it lands at 1.	1 / 3
Trigger Term Quality	Includes natural keywords like 'Google Form', 'feedback', and 'Gmail', but misses common variations such as 'survey', 'questionnaire', 'send email', or 'form link'.	2 / 3
Distinctiveness Conflict Risk	Mentioning both Google Forms and Gmail together provides some distinctiveness, but it could overlap with a general Gmail skill or a general Google Forms skill since the boundary isn't clearly drawn.	2 / 3
	Total	7 / 12 Passed

Implementation

72%

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

This is a concise, well-structured skill that provides a clear 3-step workflow for creating and sharing a Google Form. Its main weaknesses are the lack of explicit guidance on extracting the form URL from the API response and the absence of any validation/error-checking steps between API calls.

Suggestions

Show explicitly how to extract the responderUri from the form creation response (e.g., using jq or referencing the JSON path) rather than leaving it as a vague instruction.

Add a brief validation checkpoint after form creation (e.g., verify the response contains a valid formId/responderUri before proceeding to send the email).

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. No unnecessary explanations of what Google Forms or Gmail are. Every line serves a purpose, and the prerequisite is stated concisely.	3 / 3
Actionability	Provides concrete CLI commands which is good, but step 2 is vague ('Get the form URL from the response') without showing how to extract the responderUri field, and step 3 uses a placeholder FORM_URL without showing how to substitute it programmatically.	2 / 3
Workflow Clarity	Steps are clearly sequenced, but there are no validation checkpoints — no verification that the form was created successfully before proceeding, and no confirmation that the email was sent. For a multi-step workflow involving external API calls, this is a gap.	2 / 3
Progressive Disclosure	For a simple, short skill under 50 lines, the structure is appropriate. It references prerequisite skills clearly and keeps the content focused without needing external files.	3 / 3
	Total	10 / 12 Passed

Validation

90%

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 — 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

Repository: googleworkspace/cli
Commit: a3768d0

Reviewed: about 1 month 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.