recipe-create-gmail-filter
Create a Gmail filter to automatically label, star, or categorize incoming messages.
Install with Tessl CLI
npx tessl i github:googleworkspace/cli --skill recipe-create-gmail-filter88
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/skillEvaluation — 100%
↑ 1.51xAgent success when using this skill
Validation for skill structure
Discovery
82%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description excels at specificity and trigger term quality, clearly naming Gmail filters and concrete actions like labeling and starring. The main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The description is distinctive enough to avoid conflicts with other skills.
Suggestions
Add a 'Use when...' clause with trigger phrases like 'Use when the user wants to organize Gmail, set up email rules, auto-label messages, or mentions Gmail filters'
Consider adding file type or context triggers such as 'email automation' or 'inbox management' to capture more user intent variations
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'label', 'star', 'categorize incoming messages'. These are clear, actionable capabilities within the Gmail filter domain. | 3 / 3 |
Completeness | Clearly answers 'what' (create Gmail filters with specific actions) but lacks an explicit 'Use when...' clause. The when is only implied by the action description. | 2 / 3 |
Trigger Term Quality | Contains natural keywords users would say: 'Gmail', 'filter', 'label', 'star', 'categorize', 'incoming messages'. These are terms users naturally use when discussing email organization. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Gmail filters with distinct triggers like 'Gmail', 'filter', 'label'. Unlikely to conflict with general email skills or other document processing skills. | 3 / 3 |
Total | 11 / 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 well-crafted, concise skill that provides actionable commands for creating Gmail filters. The main weakness is the workflow gap around the LABEL_ID placeholder - users need to extract this from step 2's output but no guidance is provided. Otherwise, the skill is efficient and practical.
Suggestions
Add a note after step 2 explaining how to extract the LABEL_ID from the create response (e.g., 'Note the `id` field from the response for use in step 3')
Consider adding error handling guidance for common failures (e.g., label already exists, invalid filter criteria)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is lean and efficient, providing only the necessary commands without explaining what Gmail filters are or how they work. Every line serves a purpose. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready commands with concrete examples including specific JSON payloads and parameter structures. | 3 / 3 |
Workflow Clarity | Steps are clearly sequenced (list labels → create label → create filter → verify), but lacks explicit validation/error handling between steps. The LABEL_ID placeholder requires manual substitution without guidance on how to obtain it from step 2's output. | 2 / 3 |
Progressive Disclosure | For this simple, single-purpose skill under 50 lines, the structure is appropriate. The prerequisite skill reference is clear and one level deep. | 3 / 3 |
Total | 11 / 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 | |
- 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.