Name: gmail
Rating: 49.6 (1 reviews)
Author: membranedev

gmail

Gmail integration. Manage communication data, records, and workflows. Use when the user wants to interact with Gmail data.

Quality

53%

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

Quality

Content

57%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 actionable and gives Claude a usable end-to-end Membrane workflow, but it is padded with general knowledge about Gmail, inlines a sizable action catalog that belongs in a reference, and lacks validation/confirmation guards for its destructive operations. Tightening the prose and splitting out the action reference would meaningfully improve it.

Suggestions

Remove the introductory "Gmail is a free email service..." sentence and other general-knowledge padding; assume Claude knows what Gmail is.

Add an explicit validation/confirmation checkpoint before destructive actions (e.g. "Confirm the message/thread ID before running delete-message; deletes are permanent and cannot be undone").

Move the full "Popular actions" catalog to a separate ACTIONS.md reference and keep only the most common entries inline, linking out with clear one-level-deep references.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with concrete commands, but it includes unnecessary padding Claude does not need, such as "Gmail is a free email service provided by Google... widely used by individuals and businesses" and restated explanations of flags already shown in tables.	3 / 5
Actionability	It provides concrete, executable `membrane` commands for install, auth, connection, action search/run, and proxying, with copy-paste-ready syntax; minor gaps remain around resolving the CONNECTION_ID placeholder and example payloads.	4 / 5
Workflow Clarity	The connection setup is well-sequenced with state polling and checkpoints, but the skill surfaces destructive operations (delete-message, delete-thread, delete-draft, delete-label) without validation or confirmation steps, which caps workflow clarity per the destructive-operation rule.	3 / 5
Progressive Disclosure	The SKILL.md is a single file with reasonable section organization, but the large inline "Popular actions" table is content that could live in a separate reference file, and there are no one-level-deep references to offload detail.	3 / 5
	Total	13 / 20 Passed

Description

50%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 correctly pairs a what with a when and is clearly Gmail-scoped, but it relies on generic verbs ("manage") and a thin trigger phrase rather than concrete actions and natural keywords. Adding specific operations and common user phrasings would lift it from adequate to strong.

Suggestions

Replace generic verbs with concrete Gmail actions, e.g. "Send and read emails, manage drafts, labels, and threads."

Expand the trigger clause with natural user phrasings: "Use when the user wants to send, search, read, or organize Gmail messages, drafts, labels, or threads."

Consider naming the data types users actually mention (messages, attachments, conversations) instead of the abstract "communication data, records, and workflows."

Dimension	Reasoning	Score
Specificity	Names the domain ("Gmail integration") but the actions are minimal and generic — "Manage communication data, records, and workflows" describes no concrete Gmail-specific operations like sending, reading, or labeling messages.	2 / 5
Completeness	It states both a what ("Manage communication data, records, and workflows") and a when ("Use when the user wants to interact with Gmail data"), but the when-clause is generic rather than specifying concrete triggers, matching the both-present-but-could-be-more-explicit anchor.	4 / 5
Trigger Term Quality	Only a single generic keyword ("Gmail data") appears; it omits natural phrases users say such as "send email", "read messages", "drafts", "labels", or "threads", fitting the one-or-two-generic-keywords anchor.	2 / 5
Distinctiveness Conflict Risk	The Gmail-specific scope and "Use when the user wants to interact with Gmail data" trigger give it a clear niche with only minor overlap risk against other email/messaging skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/gmail/SKILL.md
Commit: f484c82

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