CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

agentmail-mcp

Configure or troubleshoot the hosted AgentMail MCP server for Codex, Claude Code, Cursor, Claude.ai, ChatGPT, or another Streamable HTTP MCP client. Use for installation, OAuth, API-key headers, connection failures, or MCP tool discovery. Do not use when the connection already works and the user just wants to send, check, or manage mail — use the sibling action skills for that.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 configuration guide: exact commands, config snippets, per-client paths, and a verify-then-troubleshoot loop with real validation steps. The only deductions are minor redundancy in auth guidance and catalog detail inlined in the body rather than split into a reference file.

Suggestions

Remove one of the two statements discouraging query-string credentials — the Auth options bullet and the closing 'Avoid query-string credentials when header authentication is available' line say the same thing.

Merge the two consecutive Tool Discovery sentences about the live hosted catalog and the published manifest into one statement to trim redundancy.

Add a one-line install/config example for the stdio fallback (e.g., the npx or pip command and the corresponding stdio mcpServers entry) so the Stdio Compatibility section is as executable as the hosted path.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence (no MCP or OAuth tutorials), but query-string credential guidance is stated twice ("supported but not recommended; prefer a header so the key doesn't end up in logs or history" and later "Avoid query-string credentials when header authentication is available"), and the Tool Discovery opener makes the live-catalog point in two consecutive sentences. Minor trims are available, so this is anchor 4 rather than 5.

4 / 5

Actionability

Copy-paste-ready JSON configs for OAuth and API-key auth, the exact CLI command (`claude mcp add --transport http agentmail https://mcp.agentmail.to/mcp`), per-client config file paths, and exact UI navigation sequences for Claude.ai and ChatGPT. The stdio fallback lacks an install command, but anchor 5 only requires the common cases to be fully executable, which they are.

5 / 5

Workflow Clarity

"Verify" is a numbered sequence with an explicit read-only smoke test ("Call `list_inboxes` as a read-only smoke test. Call `list_apps` to confirm the AgentID tools are exposed") plus annotation approval checks, and "Troubleshoot" maps errors to concrete fixes (404 → missing `/mcp`; 401 → key or OAuth recovery), providing validation checkpoints and error-recovery feedback loops per anchor 5. No destructive or batch operations, so the validation cap does not apply.

5 / 5

Progressive Disclosure

The body is well-sectioned and navigable with no nested references, matching anchor 4's "good structure; most content is appropriately placed." It falls short of anchor 5 because the Tool Discovery section inlines catalog-group detail (tool names and workflow descriptions) that could live in a reference file, the sibling skills are named rather than linked, and at ~105 lines the skill exceeds the under-50-line self-contained case the guidelines exempt.

4 / 5

Total

18

/

20

Passed

Description

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

An excellent description: concrete capabilities, comprehensive natural trigger terms including all major client names, explicit use and do-not-use boundaries, and an explicit hand-off to sibling skills. Third-person voice throughout with no padding.

DimensionReasoningScore

Specificity

The description names the domain ("Configure or troubleshoot the hosted AgentMail MCP server") and multiple concrete actions — "installation, OAuth, API-key headers, connection failures, or MCP tool discovery" — covering the skill's scope comprehensively. It exceeds anchor 4 because there are no coverage gaps for what this setup/troubleshooting skill does.

5 / 5

Completeness

It explicitly answers both what ("Configure or troubleshoot the hosted AgentMail MCP server for [clients]") and when ("Use for installation, OAuth, API-key headers, connection failures, or MCP tool discovery") with concrete trigger phrases, and adds an explicit negative boundary ("Do not use when the connection already works..."). Clear anchor 5.

5 / 5

Trigger Term Quality

It includes the natural terms users would actually say: client names ("Codex, Claude Code, Cursor, Claude.ai, ChatGPT"), "installation", "connection failures", "OAuth", "API-key headers", and "MCP tool discovery". This matches anchor 5 rather than 4 because client-name synonyms and failure-mode phrasing are covered with nothing commonly missing.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (AgentMail MCP server setup only) and the "Do not use when the connection already works and the user just wants to send, check, or manage mail — use the sibling action skills" clause actively routes away from overlapping mail-action skills, giving minimal conflict risk per anchor 5.

5 / 5

Total

20

/

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-mcp/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.