gmail-automation

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

Quality

62%

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/skills/gmail-automation/SKILL.md

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

Quality

Content

76%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 highly actionable with well-organized, executable command examples and useful dense reference tables. Its main weakness is the absence of validation/verification steps for destructive operations like sending email or modifying labels in batch.

Suggestions

Add a verification step after send/send-draft (e.g. confirm via a search for the sent message) and a confirmation/dry-run checkpoint before batch label modifications.

Trim the repeated one-line description under the '# Gmail' heading that duplicates the frontmatter description.

Consider moving the query-syntax and common-label-ID tables into a short reference file to keep SKILL.md as a lean overview.

Dimension	Reasoning	Score
Conciseness	Tight, copy-pasteable command blocks with no padding about what Gmail or OAuth is; a few redundant inline comments and the duplicate intro line could be trimmed.	4 / 5
Actionability	Every section provides fully executable commands with real flags and worked examples covering the common cases (search, get, send, draft, modify, list-labels).	5 / 5
Workflow Clarity	Setup is sequenced and operations are grouped, but destructive/batch actions (send, send-draft, modify labels) lack any validation or verification checkpoints, which caps this dimension at 3.	3 / 5
Progressive Disclosure	Clear section organization with no nested references and no monolithic wall of text; the dense query-syntax and label-ID tables could optionally be split into reference files but are reasonably placed inline.	4 / 5
	Total	16 / 20 Passed

Description

48%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 clearly states what the skill is and differentiates it from MCP-based alternatives, but it omits concrete actions and any 'when to use' trigger guidance. Adding a 'Use when...' clause and a few specific verbs would lift completeness and trigger coverage.

Suggestions

Add a 'Use when ...' clause naming concrete trigger phrases (e.g. 'Use when the user asks to search, read, send, or label Gmail messages').

List 1-2 concrete actions (e.g. 'search, read, send, and label emails') instead of only the generic 'integration'.

Include synonyms users naturally say ('email', 'inbox', 'mail') alongside 'Gmail' to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain ('Gmail integration') and one architectural aspect ('standalone OAuth authentication') but lists no concrete user-facing actions like search, send, or label management.	2 / 5
Completeness	A clear 'what' is present (Gmail integration with standalone OAuth), but there is no 'Use when...' or equivalent trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	'Gmail' is a natural term users say, but the description omits common variations and synonyms ('email', 'inbox', 'send mail', 'mail').	3 / 5
Distinctiveness Conflict Risk	'Gmail integration' with 'standalone OAuth' and the explicit 'No MCP server required' carve a clear niche with minimal overlap risk against MCP-based mail skills.	4 / 5
	Total	12 / 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/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.