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 would help Claude know exactly when to select this skill. Adding trigger guidance and a few more natural keyword variations would make this a strong description.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user wants to set up Gmail filters, auto-sort emails, organize their inbox, or create email rules.'

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' (create a Gmail filter to label/star/categorize messages) but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric.	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 for message organization. The combination of 'Gmail filter' with specific actions like labeling and starring makes it clearly distinguishable from general email or productivity skills.	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 workflow gap around the LABEL_ID placeholder—users need to know to substitute the actual label ID from step 2's output into step 3's command, and there's no error handling guidance.

Suggestions

Add a brief note after step 2 indicating that the LABEL_ID returned should be substituted into step 3's command (e.g., 'Use the `id` from the response in the next step').

Add a brief error recovery note: what to do if filter creation fails or if the verification step shows unexpected results.

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 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 include a verification step (step 4). However, there's no guidance on what to do if verification fails, no mention of replacing the placeholder 'LABEL_ID' with the actual ID from step 2's output, and no error recovery feedback loop.	2 / 3
Progressive Disclosure	For a simple, single-purpose skill under 50 lines, the content is well-organized with a clear prerequisite callout and numbered steps. No need for external references given the scope.	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: a3768d0

Reviewed: about 1 month 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.