gws-gmail-send
Gmail: Send an email.
70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
32%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is too minimal to effectively guide skill selection. While it correctly identifies the platform (Gmail) and a core action (send email), it lacks the depth needed for Claude to confidently choose this skill over others. The absence of a 'Use when...' clause and limited action coverage significantly weakens its utility.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user wants to send, compose, or draft emails through Gmail'
Expand the capability list to include related actions: 'Send, compose, reply to, and forward emails via Gmail'
Include natural trigger term variations: 'Gmail, Google email, send message, compose email, mail'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Gmail) and one action (send an email), but only describes a single capability rather than listing multiple concrete actions like composing, replying, forwarding, or managing drafts. | 2 / 3 |
Completeness | Only answers 'what' (send an email) with no 'Use when...' clause or explicit trigger guidance. The when is completely missing, which per rubric guidelines caps this at maximum 2, but the what is also minimal. | 1 / 3 |
Trigger Term Quality | Includes 'Gmail' and 'email' which are natural keywords users would say, but missing common variations like 'send message', 'compose', 'mail', or 'write an email'. | 2 / 3 |
Distinctiveness Conflict Risk | 'Gmail' provides some distinctiveness from generic email skills, but 'send an email' is generic enough to potentially conflict with other email-related skills (Outlook, general email composition). | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that demonstrates excellent economy of tokens while providing complete, actionable guidance. It correctly delegates shared concerns to a prerequisite file, includes appropriate safety warnings for write operations, and provides clear fallback guidance for advanced use cases.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what email is or how Gmail works. Every section serves a purpose and the content assumes Claude's competence. | 3 / 3 |
Actionability | Provides complete, copy-paste ready command with clear flag documentation. The example is fully executable and the fallback to raw API for advanced cases is specific. | 3 / 3 |
Workflow Clarity | For a simple single-action skill, the workflow is unambiguous. Includes an important validation checkpoint (confirm with user before executing) appropriate for a write operation. | 3 / 3 |
Progressive Disclosure | Clean structure with prerequisite reference, well-organized sections, and clear one-level-deep references to related skills. Content is appropriately scoped for this single command. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
72%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 8 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 8 / 11 Passed | |
- Reviewed
Table of Contents
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.