gws-gmail-read

Gmail: Read a message and extract its body or headers.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/gws-gmail-read/SKILL.md

Quality

Content

92%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a well-structured, token-efficient reference for a simple single-command skill, with fully executable examples and clean navigation. The only minor weakness is a small redundancy where the description is restated under the heading.

Dimension	Reasoning	Score
Conciseness	The body is lean with a compact flag table, executable examples, and no over-explanation of concepts Claude already knows; the only minor redundancy is the description line restated under the H1.	4 / 5
Actionability	Provides copy-paste ready commands (`gws gmail +read --id <ID>`), a complete flag table with required/default columns, and three examples covering basic, header, and JSON output cases.	5 / 5
Workflow Clarity	This is a simple single-action skill where the single command is unambiguous; reading email is non-destructive, so no validation checkpoint is required and the simple-skill exception applies.	5 / 5
Progressive Disclosure	Under 50 lines with well-organized sections (Usage, Flags, Examples, Tips, See Also) and only one-level-deep, clearly signaled references to sibling skills; no bundle files are needed or present.	5 / 5
	Total	19 / 20 Passed

Description

53%Weight 40%Scale 1-5

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 names concrete actions but omits any explicit 'when to use' trigger guidance, which limits its completeness and trigger-term coverage. It is reasonably distinct within the Gmail skill family.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers (e.g., 'Use when the user wants to read, view, or inspect a Gmail message or its headers/body').

Include common synonyms like 'email' or 'inbox' alongside 'Gmail' and 'message' to broaden trigger-term coverage.

Optionally name one more concrete action (e.g., 'with optional HTML body or JSON output') to lift specificity toward comprehensive coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Gmail) and two concrete actions ('Read a message', 'extract its body or headers'), but coverage is limited to read/extract with no fuller action list.	3 / 5
Completeness	The 'what' is clear ('Read a message and extract its body or headers') but there is no 'Use when...' trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms like 'Gmail', 'message', 'body', and 'headers', but misses common variations/synonyms such as 'email' or 'inbox'.	3 / 5
Distinctiveness Conflict Risk	Scoped to Gmail read operations with a clear niche, with only minor overlap risk against sibling Gmail send/manage skills.	4 / 5
	Total	13 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 2 suspicious	Warning

	Total	14 / 16 Passed

Repository: googleworkspace/cli
Path: skills/gws-gmail-read/SKILL.md
Commit: a3768d0

Reviewed: 2 days 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.