Find Gmail messages with a specific label and forward them to another address.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-forward-labeled-emails63
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
42%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 clearly states specific capabilities (finding labeled messages and forwarding them) but critically lacks explicit trigger guidance for when Claude should use this skill. While Gmail-specific terminology provides some distinctiveness, the absence of a 'Use when...' clause significantly limits its effectiveness for skill selection among many options.
Suggestions
Add a 'Use when...' clause with trigger terms like 'forward emails', 'Gmail labels', 'auto-forward', 'filter and forward'
Include common variations like 'email', 'tagged messages', 'categorized emails' to improve trigger term coverage
Specify the use case more explicitly, e.g., 'Use when user wants to automatically forward labeled Gmail messages or set up email forwarding rules'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists two concrete actions: 'Find Gmail messages with a specific label' and 'forward them to another address'. These are specific, actionable capabilities. | 3 / 3 |
Completeness | Describes what the skill does but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes natural keywords like 'Gmail', 'messages', 'label', and 'forward', but missing common variations like 'email', 'filter', 'send', or 'tagged messages'. | 2 / 3 |
Distinctiveness Conflict Risk | Gmail-specific focus provides some distinction, but could overlap with general email skills. The label+forward combination is somewhat unique but not explicitly differentiated. | 2 / 3 |
Total | 8 / 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 clear command examples for forwarding labeled Gmail messages. However, it lacks guidance on extracting values from intermediate steps (MSG_ID, subject, body) and has no validation or error handling for a multi-step workflow that could fail at any point.
Suggestions
Show how to extract MSG_ID, subject, and body from the step 2 response (e.g., JSON path or field names)
Add a note about handling multiple messages (loop or batch processing guidance)
Include a validation step to confirm the forward was sent successfully
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the essential commands without explaining what Gmail is or how labels work. Every line serves a purpose. | 3 / 3 |
Actionability | Commands are concrete and executable, but MSG_ID, [Original Subject], and [Original Message Body] are placeholders without guidance on how to extract/substitute them from step 2's output. | 2 / 3 |
Workflow Clarity | Steps are clearly sequenced, but there's no validation checkpoint (e.g., confirming message was found, verifying forward succeeded) and no guidance on handling multiple messages or errors. | 2 / 3 |
Progressive Disclosure | For a simple, single-purpose skill under 50 lines, the structure is appropriate with a clear prerequisite callout and well-organized steps section. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
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.