gmail-automation

Lightweight Gmail integration with standalone OAuth authentication. No MCP server required.

Quality

64%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/gmail-automation/SKILL.md

The canonical home for this skill is gmail in sanjay3290/ai-skills

Quality

Content

72%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 highly actionable with executable commands throughout and is well-organized by section, but it lacks validation checkpoints for destructive operations and does not split reference material into bundle files. Adding verification steps and factoring the query/label tables into references would raise both capped dimensions.

Suggestions

Add verification checkpoints to destructive/batch operations, e.g. confirm a message exists before sending a draft, or re-read a message after modifying its labels.

Provide the referenced bundle files (scripts/auth.py, scripts/gmail.py) or move the query-syntax and common-label-ID tables into a references/ file and link to it from SKILL.md.

Remove the verbatim restatement of the description at the top of the body to trim redundant tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable commands and tables with no over-explanation of concepts Claude knows, though the description is restated verbatim at the top and the token-management section has minor padding.	4 / 5
Actionability	It provides copy-paste-ready bash commands with concrete flags covering search, get, send, draft, modify, and list-labels, plus example values for each common case.	5 / 5
Workflow Clarity	First-Time Setup is a clear sequence, but destructive/batch operations (send, modify labels, send-draft) have no validation or verification checkpoints, capping workflow clarity at 3 per the rubric.	3 / 5
Progressive Disclosure	Sections are clearly headed, but all content is inlined in a ~170-line SKILL.md with no bundle files present (the referenced scripts/auth.py and scripts/gmail.py do not exist) and no separation into reference files for the query-syntax and label-ID tables.	3 / 5
	Total	15 / 20 Passed

Description

57%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 specific to Gmail and well-differentiated, but it omits any explicit trigger guidance and lists no concrete email operations. Adding a 'Use when...' clause naming actions like send, search, and read would lift it substantially.

Suggestions

Add a 'Use when...' clause with concrete trigger phrases, e.g. 'Use when sending, searching, or reading Gmail messages.'

Name the concrete operations the skill performs (search, get, send, draft, modify labels) rather than only describing the integration.

Drop 'Lightweight' or keep it but pair it with action verbs so the description reads as capabilities, not a feature blurb.

Dimension	Reasoning	Score
Specificity	The description names the domain ('Lightweight Gmail integration') and one concrete capability ('standalone OAuth authentication'), but lists no email actions like search, send, or read, so it is not comprehensive.	3 / 5
Completeness	It clearly states what the skill is ('Lightweight Gmail integration with standalone OAuth authentication') but has no 'Use when...' clause or explicit trigger guidance, which caps completeness at 3.	3 / 5
Trigger Term Quality	It includes the natural term 'Gmail' plus 'OAuth authentication' and 'MCP server', but is missing the common action phrases users would actually say (send email, search inbox, read mail).	3 / 5
Distinctiveness Conflict Risk	It carves a clear Gmail-only niche and the 'No MCP server required' phrasing explicitly distinguishes it from MCP-based Gmail skills, giving minimal conflict risk.	5 / 5
	Total	14 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 28 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/gmail-automation/SKILL.md
Commit: 57c135b

Reviewed: 4 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.