recipe-create-feedback-form
Create a Google Form for feedback and share it via Gmail.
67
60%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/recipe-create-feedback-form/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 identifies a specific workflow (creating a Google Form for feedback and sharing via Gmail) but is too terse to be highly effective for skill selection. It lacks an explicit 'Use when...' clause, misses common trigger term variations like 'survey' or 'questionnaire', and doesn't detail the specific capabilities involved in form creation or email sharing.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to create a feedback form, survey, or questionnaire and send it via email or Gmail.'
Include additional trigger terms like 'survey', 'questionnaire', 'send form link', 'email form', and 'collect responses' to improve keyword coverage.
Expand the capability description with more specific actions, e.g., 'Creates Google Forms with custom questions, rating scales, and multiple-choice options, then shares the form link via Gmail to specified recipients.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Google Forms, Gmail) and two actions (create, share), but lacks detail on what kind of feedback forms or what the sharing process entails. Not comprehensive enough for a 3. | 2 / 3 |
Completeness | Describes what the skill does (create a Google Form and share via Gmail) but has no explicit 'Use when...' clause or equivalent trigger guidance, which per the rubric caps completeness at 2, and the 'what' is also fairly thin, placing this at 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Google Form', 'feedback', and 'Gmail' that users might say, but misses common variations like 'survey', 'questionnaire', 'email', or 'send form link'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Google Forms and Gmail is somewhat distinctive, but 'feedback' is generic and could overlap with other feedback-related or email-related skills. The scope is narrow enough to avoid major conflicts but not sharply delineated. | 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 concise, well-structured recipe skill that provides actionable CLI commands in a clear sequence. Its main weakness is the lack of a validation step between form creation and email sending—confirming the form was created and the URL is valid before sending an irreversible email would improve robustness.
Suggestions
Add a validation checkpoint after step 1 to confirm the form was created successfully and the responderUri is present before proceeding to send the email.
Consider noting what to do if form creation fails (e.g., check error response, retry) to add a feedback loop for error recovery.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Very lean and efficient. No unnecessary explanations of what Google Forms or Gmail are. Every line serves a purpose. | 3 / 3 |
Actionability | Provides concrete, copy-paste ready CLI commands with specific JSON payloads and flags. The placeholder FORM_URL is clearly derived from step 2. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no validation checkpoint—e.g., confirming the form was created successfully before sending the email, or verifying the responderUri is valid. For a multi-step process involving sending emails (a non-reversible action), a validation step would be appropriate. | 2 / 3 |
Progressive Disclosure | For this simple, short skill (under 50 lines), the structure is appropriate. It clearly references prerequisite skills (`gws-forms`, `gws-gmail`) for deeper details without nesting references. | 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 | |
- Repository
- googleworkspace/cli
- Commit
c7c6646
- 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.