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.

57

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/agentmail/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

64%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a solid API reference skill with excellent actionability — concrete curl commands, SDK examples, and real-world patterns are all copy-paste ready. The main weaknesses are moderate verbosity (redundant coverage across curl/SDK/table formats) and lack of explicit validation checkpoints in workflows (e.g., checking karma before sending, verifying account creation succeeded before using it). The content would benefit from splitting detailed reference material into separate files.

Suggestions

Add explicit karma-check validation steps before operations that cost karma in the workflow patterns (e.g., check balance → send → handle 402)

Move the full API reference table, TypeScript types, and SDK examples into separate referenced files (e.g., API_REFERENCE.md, SDK.md) to keep SKILL.md lean

Add error recovery guidance to the common patterns — e.g., what to do if polling times out or if account creation fails due to insufficient karma

DimensionReasoningScore

Conciseness

The skill is fairly efficient but includes some redundancy — the full API reference table duplicates information already shown in the quick start examples, and the TypeScript SDK section largely restates the same operations shown via curl. The types section and some explanatory text could be trimmed.

2 / 3

Actionability

Excellent actionability with fully executable curl commands and TypeScript SDK examples that are copy-paste ready. Includes concrete request/response formats, specific headers, and real patterns like polling for verification emails and webhook signature verification.

3 / 3

Workflow Clarity

The common patterns section shows clear multi-step workflows (sign up + poll for verification, send + wait for reply), but there are no explicit validation checkpoints. Notably, the skill mentions checking karma balance before operations but doesn't integrate this as a validation step in the workflows. No error recovery loops beyond basic polling.

2 / 3

Progressive Disclosure

The content is well-structured with clear section headers and a logical progression from quick start to advanced patterns. However, for a skill of this length (~200 lines), the types, full API reference, and common patterns could be split into separate referenced files rather than being inline, making the main skill leaner.

2 / 3

Total

9

/

12

Passed

Description

67%Scale 1-3

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 strong in specificity and distinctiveness, clearly naming the AgentMail API and listing concrete actions like creating accounts, sending/receiving emails, and managing webhooks. However, it lacks an explicit 'Use when...' clause, which limits its completeness score, and could benefit from additional natural trigger terms users might employ when needing this skill.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user needs to send or receive emails programmatically, set up email accounts for AI agents, or interact with the AgentMail API.'

Include additional natural trigger terms like 'inbox', 'mail', 'email automation', 'programmatic email', or 'agent email' to improve keyword coverage.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Create accounts, send/receive emails, manage webhooks, and check karma balance via the AgentMail API.' These are clear, actionable capabilities.

3 / 3

Completeness

Clearly answers 'what does this do' with specific actions, but lacks an explicit 'Use when...' clause or equivalent trigger guidance. The 'when' is only implied by the capability listing, which caps this at 2 per the rubric guidelines.

2 / 3

Trigger Term Quality

Includes relevant terms like 'email', 'send/receive emails', 'webhooks', 'AgentMail API', and 'accounts', but misses common user variations like 'inbox', 'mail', 'SMTP', or 'email automation'. The term 'karma balance' is domain-specific and may not be naturally used by most users.

2 / 3

Distinctiveness Conflict Risk

The description is clearly scoped to the AgentMail API specifically, with a distinct niche of 'email infrastructure for AI agents.' The mention of AgentMail, karma balance, and webhooks makes it highly unlikely to conflict with generic email or communication skills.

3 / 3

Total

10

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-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.