CtrlK
BlogDocsLog inGet started
Tessl Logo

agentmail

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

65

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/agentmail/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 executable examples and clear workflows for the main use cases; the main gap is the absence of external reference files for the API table and type definitions, which keeps progressive disclosure at 4 rather than 5.

Suggestions

Move the full API reference table and TypeScript type definitions into a separate reference file (e.g. reference/API.md) and link from the body to slim the main skill.

Add an explicit validation/verification checkpoint before destructive operations (account deletion) to lift workflow clarity.

Trim restated karma-cost details that duplicate the inline examples to improve token efficiency.

DimensionReasoningScore

Conciseness

Largely lean with executable curl and TypeScript snippets and minimal preamble, though the full API table and Karma table restate information already shown in examples and could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready curl commands and TypeScript SDK snippets covering create, send, read, attachments, webhooks, karma, and error handling — fully executable across common cases.

5 / 5

Workflow Clarity

Common-patterns sections give clear poll-loop sequences for signup verification and reply-waiting with explicit sleep intervals, and error handling shows status/code checks; destructive account deletion lacks an explicit validation checkpoint, keeping it just short of 5.

4 / 5

Progressive Disclosure

Well-organized sections (Quick start, Full API reference, Karma system, SDK, Common patterns, Types, Limitations) with no nested references, but all content is inlined in SKILL.md with no external reference files for the bulky API table and type definitions.

4 / 5

Total

17

/

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.

The description is specific and distinctive with comprehensive action coverage, but omits any 'Use when...' trigger guidance, which caps completeness at 3 and slightly limits natural trigger-term coverage.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when an agent needs a real inbox for signups, verification emails, or transactional messaging via AgentMail.'

Surface natural user phrases like 'inbox', 'verification email', or 'sign up for a service' that the skill actually supports.

Keep the third-person voice (currently correct) and avoid adding padding.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'Create accounts, send/receive emails, manage webhooks, and check karma balance' — comprehensive coverage of the API's capabilities.

5 / 5

Completeness

Clearly states 'what' (the four API capabilities) but provides no 'Use when...' clause or explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Includes natural terms like 'accounts', 'emails', 'webhooks', and 'karma balance', but lacks synonyms a user might say (e.g. 'inbox', 'verification email', 'sign up') that the body actually covers.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche — AgentMail API for AI-agent email at a specific domain — with triggers unlikely to overlap with general email or file skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/agentic-awesome-skills
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.