CtrlK
BlogDocsLog inGet started
Tessl Logo

resend-email

Resend transactional email patterns, React Email templates, domain configuration, and webhook handling. Use when sending emails, building email templates, or configuring email delivery.

70

Quality

85%

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

85%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 concise, actionable, and well-organized with a clear validated domain-setup workflow and sharp gotchas that capture non-obvious failure modes. Its main gap is the absence of an executable send/template code snippet to complement the install and dev-preview commands.

Suggestions

Add a minimal copy-paste send example (e.g. `resend.emails.send({ from, to, react: <Template/>, subject })`) so the core action is fully executable, not just described.

Promote the webhook signature verification into a short numbered checklist or code block (verify raw body -> return 400 on failure / 200 on success) to make that validation step explicit and reproducible.

Note the event names (email.delivered/bounced/complained) are already present; consider grouping them under a Webhooks section header to keep the Gotchas list scannable.

DimensionReasoningScore

Conciseness

Lean and efficient; it assumes Claude's competence, presents only non-obvious gotchas and concrete commands, and every token earns its place without explaining basic concepts.

5 / 5

Actionability

Provides concrete, executable guidance (verify call, dig command, curl smoke test, npm install, npx email dev) but lacks a copy-paste-ready send/verify code example for the core send path.

4 / 5

Workflow Clarity

The Domain setup section is a clear numbered sequence with verification checkpoints (dig, header pass check, webhook 200 smoke test), though webhook signature verification is described in prose rather than as a sequenced validation step.

4 / 5

Progressive Disclosure

A compact single-file skill under 50 lines with no need for external references; it is well-organized into clear sections (Gotchas, Domain setup, Templates), qualifying for the simple-skill exception.

5 / 5

Total

18

/

20

Passed

Description

85%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 well-formed: it names a clear Resend-specific niche, lists concrete capabilities, and includes an explicit 'Use when' trigger clause. It is concise, third person, and avoids vague fluff.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('transactional email patterns', 'React Email templates', 'domain configuration', 'webhook handling') with minor coverage gaps (e.g., no mention of send API or tracking events).

4 / 5

Completeness

Clearly states both what it does (the four Resend capabilities) and when to use it ('Use when sending emails, building email templates, or configuring email delivery') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger terms like 'sending emails', 'building email templates', 'configuring email delivery' are present, though it lacks synonyms or file/extension variants.

4 / 5

Distinctiveness Conflict Risk

The Resend-specific niche (transactional email, React Email templates, webhooks) is distinct with minimal overlap risk against generic email or 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.