agentmail

Email infrastructure for AI agents. Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.

Quality

76%

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

The canonical home for this skill is agentmail in sickn33/agentic-awesome-skills

Quality

Content

78%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.

A strong, highly actionable API skill with concrete curl and TypeScript examples and well-sequenced polling workflows. Its main weakness is structure: substantial reference material is inlined in one file with no progressive disclosure to separate reference files.

Suggestions

Move the full API reference table, TypeScript type definitions, and detailed karma-event table into a separate references/ file (e.g. REFERENCE.md) and link to it from a concise overview, keeping only the Quick start and key patterns inline in SKILL.md.

Add an explicit error-recovery checkpoint in the Common patterns workflows (e.g. on HTTP 402 INSUFFICIENT_KARMA, surface the karma balance and stop rather than silently retrying).

De-duplicate the create/send/read examples between the curl Quick start and the TypeScript SDK section so each medium is shown once and cross-referenced.

Dimension	Reasoning	Score
Conciseness	The body is efficient and assumes Claude's competence (no preamble on what email/APIs are), but the curl Quick start and the TypeScript SDK section both demonstrate create/send/read, creating minor redundancy that could be trimmed.	4 / 5
Actionability	Fully executable copy-paste curl commands and complete TypeScript examples, plus the Common patterns section covers the common cases (signup + verification polling, send + wait-for-reply polling).	5 / 5
Workflow Clarity	The Common patterns offer clearly sequenced polling loops that act as checkpoints (find verification -> get detail -> break), and the karma guidance says to check balance before cost-incurring operations; minor gap is no explicit error-recovery flow tied into those workflows.	4 / 5
Progressive Disclosure	Well-organized into clear sections, but at ~240 lines it is a monolithic single file with bulk reference material (full API table, TypeScript types, detailed karma system) inlined rather than split into one-level-deep reference files; no external references exist.	3 / 5
	Total	16 / 20 Passed

Description

75%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.

A specific, distinctive description that names concrete capabilities and a clear niche, but it omits any explicit 'Use when...' trigger guidance, which caps its completeness.

Suggestions

Append an explicit trigger clause, e.g. 'Use when an agent needs a real email address to send/receive mail, sign up for services and read verification codes, or manage inbound webhooks via the AgentMail API.'

Add natural synonyms users would say — 'inbox', 'verification email/code', 'sign up for services' — to broaden trigger-term coverage.

Keep the existing concrete action list and third-person voice; only the missing 'when' guidance and a few synonyms need adding.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Create accounts, send/receive emails, manage webhooks, and check karma balance' — giving comprehensive coverage of the API's capabilities.	5 / 5
Completeness	The 'what' is clear and concrete, but there is no 'when'/'Use when' clause or equivalent explicit trigger guidance; per the judging guidelines a missing Use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('email', 'emails', 'webhooks', 'accounts'), but missing common variations a user might say such as 'inbox', 'verification code', or 'sign up for services'.	4 / 5
Distinctiveness Conflict Risk	'Email infrastructure for AI agents' scoped to the AgentMail API with a karma-balance mechanic carves out a clear, distinct niche with minimal overlap risk against generic email skills.	5 / 5
	Total	17 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/agentmail/SKILL.md
Commit: 900c504

Reviewed: 15 minutes 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.