Find Gmail messages with a specific label and forward them to another address.
77
72%
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-forward-labeled-emails/SKILL.mdQuality
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 recipe that provides a clear 3-step workflow for forwarding labeled Gmail messages. However, it falls short on actionability because the placeholder substitution between steps is not automated or explained, and it lacks validation steps for what is effectively a batch operation across multiple messages.
Suggestions
Show how to extract message ID, subject, and body from the step 2 response to use in step 3, making the pipeline more executable end-to-end.
Add a loop or iteration pattern for handling multiple messages returned in step 1, with a verification check after each forward.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient. The prerequisite note is necessary, and every line serves a purpose. No unnecessary explanations of what Gmail or labels are. | 3 / 3 |
Actionability | The commands are concrete and specific, but the workflow relies on manual placeholder substitution (MSG_ID, Original Subject, Original Message Body) without showing how to extract those values from step 2's output. The forward step is not fully executable as-is. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no validation or error handling—no check for empty results in step 1, no verification that the forward was sent successfully, and no guidance on iterating over multiple messages. For a batch-like operation (forwarding multiple labeled messages), missing feedback loops cap this at 2. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate. It references the prerequisite skill clearly and keeps content well-organized in a single file with no need for external references. | 3 / 3 |
Total | 10 / 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.