recipe-forward-labeled-emails
Find Gmail messages with a specific label and forward them to another address.
68
61%
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
50%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 specific about its Gmail label-and-forward functionality and occupies a clear niche, but it lacks an explicit 'Use when...' clause and misses common trigger term variations like 'email' or 'filter'. Adding trigger guidance and broader keyword coverage would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause, e.g., 'Use when the user wants to forward labeled Gmail messages, auto-forward emails, or filter and redirect mail.'
Include common trigger term variations such as 'email', 'filter', 'tagged', 'redirect', and 'auto-forward' to improve matching against natural user language.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists specific concrete actions: finding Gmail messages by label and forwarding them to another address. These are clear, actionable operations. | 3 / 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 'when' is entirely missing/only implied, placing it at 1-2. Given the rubric guideline that a missing 'Use when' clause caps at 2, and the when is only implied, this scores a low 2 at best — but since there is zero explicit trigger guidance, scoring at 1. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Gmail', 'messages', 'label', and 'forward', but misses common variations like 'email', 'tagged', 'send to', 'filter', or 'auto-forward'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of Gmail, labels, and forwarding creates a very specific niche that is unlikely to conflict with other skills. It targets a narrow, well-defined workflow. | 3 / 3 |
Total | 9 / 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 clearly communicates the high-level workflow for forwarding labeled Gmail messages. However, it falls short on actionability because the placeholders between steps aren't connected (no extraction/piping of message data), and the workflow lacks validation steps and iteration logic for handling multiple messages.
Suggestions
Show how to extract the message ID, subject, and body from the output of steps 1 and 2 so the values can be used in step 3 (e.g., using jq or variable assignment).
Add a loop construct or note for handling multiple messages returned by the label query in step 1.
Add a validation step after sending (e.g., check the send response or verify in the Sent folder) to confirm the forward succeeded.
| 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 steps 2 and 3 use placeholders (MSG_ID, [Original Subject], [Original Message Body]) without showing how to extract and pipe those values from the previous step's output, making the workflow not fully copy-paste executable. | 2 / 3 |
Workflow Clarity | The three 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), the lack of a loop and validation caps this at 2. | 2 / 3 |
Progressive Disclosure | For a simple, short skill under 50 lines, the structure is appropriate: a clear prerequisite callout, a brief description, and numbered steps. The reference to the gws-gmail skill is one level deep and clearly signaled. | 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 | |
- 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.