email

Send emails, buy forwarding inboxes, manage custom subdomains, and read messages programmatically via x402. USE FOR: - Sending emails (one-off or from custom addresses) - Buying a forwarding inbox (username@stableemail.dev) - Purchasing custom email subdomains (you@yourname.stableemail.dev) - Reading and managing inbox messages programmatically - Setting up catch-all forwarding for subdomains - Managing authorized signers for shared subdomains TRIGGERS: - "send email", "email this to", "notify by email" - "buy inbox", "forwarding address", "email inbox" - "custom domain", "subdomain", "email subdomain" - "read emails", "check inbox", "list messages" - "email address", "disposable email", "temporary email" ALWAYS use `npx agentcash@latest fetch` for stableemail.dev endpoints. IMPORTANT: Use exact endpoint paths from the Quick Reference table below.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Medium

Suggest reviewing before use

Quality

Content

72%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 content is highly actionable with executable commands but is hurt by missing validation checkpoints in destructive/paid workflows and a dangling reference to a non-existent getting-started file. Consolidating the duplicate cost tables and adding verification steps would lift the weakest dimensions.

Suggestions

Add validation/verification checkpoints to the Workflows checklists (e.g. 'confirm DNS verification complete before sending from subdomain', 'verify messageId returned before declaring delivery success', 'confirm refund transaction on cancel').

Fix or remove the dangling reference to rules/getting-started.md — either create the file or replace the link with the actual installation/wallet-setup steps inline.

Consolidate the Quick Reference price column and the separate Cost Estimation table to remove duplicated pricing information.

Dimension	Reasoning	Score
Conciseness	Mostly lean with endpoint tables and copy-paste commands, but the Quick Reference and Cost Estimation tables duplicate pricing and could be consolidated; minor trimming possible without concept over-explanation.	4 / 5
Actionability	Every task is covered with executable `npx agentcash@latest fetch` commands including full JSON bodies, documented parameters, and examples spanning send, inbox, subdomain, and attachment cases.	5 / 5
Workflow Clarity	The Workflows checklists list steps but lack validation checkpoints for destructive/paid operations (buy, cancel/refund, delete messages), e.g. no 'confirm DNS verified before sending' or 'verify delivery via messageId', which caps the score at 3.	3 / 5
Progressive Disclosure	The body is a single inlined file and references [rules/getting-started.md] which does not exist in the bundle (dangling reference); structure exists but the reference is unsignaled/missing and content is not split out.	3 / 5
	Total	15 / 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.

The description is strong across the board: concrete actions, comprehensive trigger phrases, and clear what/when guidance with low conflict risk. No significant weaknesses to address.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Send emails, buy forwarding inboxes, manage custom subdomains, and read messages programmatically' — giving comprehensive coverage of the skill's domain.	5 / 5
Completeness	Explicitly answers both 'what' (opening sentence of capabilities) and 'when' (USE FOR + TRIGGERS clauses with concrete trigger phrases).	5 / 5
Trigger Term Quality	A dedicated TRIGGERS section provides comprehensive natural phrases and synonyms users would say ('send email', 'email this to', 'buy inbox', 'custom domain', 'read emails', 'check inbox', 'disposable email', 'temporary email').	5 / 5
Distinctiveness Conflict Risk	The x402-paid StableEmail niche with distinct triggers is clearly bounded and unlikely to fire for the wrong skill.	5 / 5
	Total	20 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning
relative_links	Relative link issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: Merit-Systems/agentcash-skills
Path: skills/email/SKILL.md
Commit: 3d657b7

Reviewed: 1 day 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.