recipe-create-gmail-filter

Create a Gmail filter to automatically label, star, or categorize incoming messages.

Quality

77%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/recipe-create-gmail-filter/SKILL.md

Quality

Discovery

67%

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 concise and specific about what it does—creating Gmail filters with concrete actions like labeling, starring, and categorizing. Its main weakness is the absence of an explicit 'Use when...' clause, which limits Claude's ability to know exactly when to select this skill. Adding trigger guidance and a few more natural keyword variations would strengthen it.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about setting up Gmail filters, email rules, auto-sorting emails, or organizing their inbox.'

Include additional natural trigger terms users might say, such as 'email rules', 'inbox organization', 'auto-sort', 'email automation', or 'filter emails'.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: 'label, star, or categorize incoming messages' and specifies the context is creating a Gmail filter. These are clear, actionable capabilities.	3 / 3
Completeness	Clearly answers 'what does this do' (create Gmail filters to label/star/categorize messages), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The 'when' is only implied.	2 / 3
Trigger Term Quality	Includes good natural keywords like 'Gmail filter', 'label', 'star', 'categorize', and 'incoming messages', but misses common variations users might say such as 'email rules', 'auto-sort', 'inbox organization', 'archive', or 'email automation'.	2 / 3
Distinctiveness Conflict Risk	Very specific niche: Gmail filters specifically. Unlikely to conflict with other skills since it targets a distinct product (Gmail) and a distinct action (creating filters). Clear and distinguishable.	3 / 3
	Total	10 / 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 clear, executable commands for creating a Gmail filter. Its main weakness is the implicit step of extracting the LABEL_ID from step 2's output and substituting it into step 3, which could cause confusion. Adding a brief note about this substitution and basic error handling would make it excellent.

Suggestions

Add a note between steps 2 and 3 clarifying that LABEL_ID should be replaced with the actual label ID returned from step 2's output.

Add brief error handling guidance, e.g., 'If the label already exists, use the ID from step 1 instead of creating a new one.'

Dimension	Reasoning	Score
Conciseness	Very lean and efficient. No unnecessary explanations of what Gmail filters are or how they work. Every line is actionable. The prerequisite note is appropriately brief.	3 / 3
Actionability	Provides fully concrete, copy-paste ready CLI commands for each step with specific flags, parameters, and JSON payloads. The example uses realistic values (e.g., 'receipts@example.com', 'Receipts' label).	3 / 3
Workflow Clarity	Steps are clearly sequenced and logical (list labels → create label → create filter → verify). However, there's no error handling or feedback loop — e.g., what if the label already exists, what if the LABEL_ID placeholder isn't replaced, or what to do if filter creation fails. The LABEL_ID placeholder is used without explicit instruction to substitute it from step 2's output.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines, the structure is appropriate. It references a prerequisite skill cleanly and keeps content well-organized with a clear steps section. No need for external file references.	3 / 3
	Total	11 / 12 Passed

Validation

90%

Warnings & errors only

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: about 7 hours ago

Table of Contents

Discovery Implementation Validation

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.