gws-gmail-reply

Gmail: Reply to a message (handles threading automatically).

Quality

76%

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-reply/SKILL.md

Quality

Content

100%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 content is a tight, fully executable reference for a single-purpose CLI skill: every flag is documented, examples cover the common cases, and tips capture genuinely non-obvious behavior. No substantive weaknesses; the body exemplifies token-efficient skill writing.

Dimension	Reasoning	Score
Conciseness	The body is lean: a one-line usage, a flags table, six examples, and short tips — no concept padding or filler, and the tips convey non-obvious detail (In-Reply-To, gmail_quote classes, cid: references). Every token earns its place.	5 / 5
Actionability	The `gws gmail +reply` commands are fully executable and copy-paste ready, with all flags documented and examples covering cc, to, html, attach, and draft cases.	5 / 5
Workflow Clarity	This is a simple single-task skill whose single action is unambiguous, and a --dry-run flag is available for verification, so workflow clarity scores 5 under the simple-skill exception.	5 / 5
Progressive Disclosure	Under 50 lines with no bundle files needed; sections (Usage, Flags, Examples, Tips, See Also) are well organized, and cross-skill references to ../gws-shared and ../gws-gmail are one level deep and clearly signaled (with a fallback if missing).	5 / 5
	Total	20 / 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 clear and on-domain but thin: it states what the skill does without explicit trigger guidance or synonyms. Adding a 'Use when...' clause and terms like 'email'/'respond' would lift completeness and trigger quality.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user asks to reply to an email or Gmail message.'

Include natural synonyms such as 'email' and 'respond' alongside 'message' and 'reply' to broaden trigger matching.

Mention the --draft/--dry-run options briefly in the description to distinguish from +reply-all and signal safe usage.

Dimension	Reasoning	Score
Specificity	"Reply to a message" names the Gmail domain and one concrete action, with a second capability noted parenthetically ("handles threading automatically"), but coverage is not comprehensive. It fits the anchor 'names domain and 1-2 concrete actions' and is not broad enough for 4.	3 / 5
Completeness	A clear 'what' is present (reply to a Gmail message) but there is no 'Use when...' trigger clause, which per the guidelines caps completeness at 3.	3 / 5
Trigger Term Quality	"Reply" and "message" are natural terms a user would say, but common synonyms like "email" and "respond" are absent, matching the anchor 'some relevant keywords but missing common variations or synonyms'.	3 / 5
Distinctiveness Conflict Risk	"Gmail: Reply to a message" carves a clear niche with minimal overlap risk; the only nearby sibling is +reply-all, so it is 'mostly distinct; minor overlap risk with closely related 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-reply/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.