CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentmail-cli

Operate AgentMail from a shell with the official CLI. Use when the user wants commands for listing or creating inboxes, reading or searching mail, sending or replying, managing drafts, or scripting JSON/YAML output; do not use for SDK code, MCP setup, or framework adapters.

72

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, executable CLI reference that respects the reader's competence and includes validation guidance for its one destructive command. Its main gaps are the absence of error-recovery feedback loops and slightly inline-heavy administrative sections.

Suggestions

Add a short error-recovery note (e.g., on failure, rerun with --debug and parse the --format-error output) to complete the feedback loop for failed commands.

Move exhaustive per-resource flag listings or the domains/webhooks administrative detail into a references/ file and link to it, keeping SKILL.md as the overview.

Show one concrete --format json / --transform example since scripting structured output is called out in the description but never demonstrated.

DimensionReasoningScore

Conciseness

The body is lean and command-first: prose lines like 'Pods group inboxes together.' and comments like '# HTML body instead of plain text' each earn their place, and nothing explains concepts Claude already knows.

5 / 5

Actionability

Every section gives copy-paste-ready commands with placeholders (e.g. 'agentmail inboxes messages send --inbox-id <inbox_id> --to "recipient@example.com" ...'), plus a concrete global-flags table and enumerated '--format' values covering the common cases.

5 / 5

Workflow Clarity

Explicit checkpoints exist for risky operations ('Confirm the exact inbox before running the destructive delete command', 'Fetch the full message before relying on body content'), avoiding the destructive-operation cap, but no error-recovery feedback loops (e.g., how to inspect failures via '--format-error' or '--debug' and retry).

4 / 5

Progressive Disclosure

Well-organized per-resource sections with bulk flag detail delegated to 'agentmail <resource> --help' and a closing 'Run agentmail --help ... before using an administrative command not covered here', but the ~110-line body sits beyond a pure overview with no separate reference files for administrative/webhook/domain detail.

4 / 5

Total

18

/

20

Passed

Description

87%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 strong third-person description with explicit what/when guidance and effective negative boundaries. Its only weaknesses are incomplete coverage of the CLI's resources and a missing common synonym.

Suggestions

Mention the remaining resources (pods, webhooks, domains) to close the coverage gap with the body, e.g. '...managing pods, webhooks, and domains'.

Add 'email' as a synonym alongside 'mail' so users who say 'send an email' trigger the skill.

DimensionReasoningScore

Specificity

'listing or creating inboxes, reading or searching mail, sending or replying, managing drafts, or scripting JSON/YAML output' lists several specific concrete actions, but pods, webhooks, and domains management — all covered in the body — are absent, leaving minor gaps that keep it below the comprehensive anchor 5.

4 / 5

Completeness

It clearly answers both: what ('Operate AgentMail from a shell with the official CLI' with enumerated capabilities) and when ('Use when the user wants commands for...') with concrete trigger phrases, plus explicit negative triggers.

5 / 5

Trigger Term Quality

Natural phrases like 'inboxes', 'reading or searching mail', 'sending or replying', 'drafts', and 'commands' are present, but the common synonym 'email' (vs. only 'mail') is missing, matching the 'a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

A named-product niche with distinct triggers and an explicit boundary ('do not use for SDK code, MCP setup, or framework adapters') gives minimal conflict risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

stevenknowswhy/ProfessionalBuyer

Path

.claude/skills/agentmail-cli/SKILL.md

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.