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
Correct gws gmail +send command syntax
Correct send command
0%
100%
--to flag present
100%
100%
--subject flag present
100%
100%
--body flag present
100%
100%
No manual base64 encoding
100%
100%
No manual RFC 2822 formatting
100%
100%
Confirmation before send
0%
0%
Recipient is parameterized
100%
100%
Subject is parameterized
100%
100%
No unsupported +send flags
100%
100%
Without context: $0.1972 · 43s · 13 turns · 59 in / 2,311 out tokens
With context: $0.3344 · 1m 3s · 23 turns · 277 in / 3,334 out tokens
Raw API fallback for HTML, CC/BCC, and attachments
Uses raw API command
0%
100%
--json flag used
0%
100%
Does NOT use +send for HTML
100%
100%
HTML content in payload
0%
80%
CC recipient in payload
50%
70%
No manual base64 in script logic
100%
0%
To field in payload
60%
80%
Subject in payload
60%
80%
Without context: $0.1882 · 45s · 14 turns · 20 in / 2,453 out tokens
With context: $0.2958 · 1m 13s · 19 turns · 182 in / 4,069 out tokens
User confirmation before write command execution
Confirmation before send
100%
0%
Correct send command
0%
100%
--to flag present
100%
100%
--subject flag present
100%
100%
--body flag present
100%
100%
Recipient shown before confirm
100%
0%
Abort on refusal
100%
0%
No auto-confirm bypass
100%
100%
Without context: $0.1725 · 54s · 14 turns · 59 in / 3,011 out tokens
With context: $0.2635 · 44s · 17 turns · 54 in / 2,218 out tokens
Table of Contents
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.