CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

resend-cli

Operate the Resend platform from the terminal — send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the `resend` CLI. Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates. Always load this skill before running `resend` commands — it contains the non-interactive flag contract and gotchas that prevent silent failures.

Quality

93%

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

93%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 well-structured CLI skill body: dense, executable, and organized around a non-interactive flag contract plus a gotchas table that captures real failure modes Claude could not infer. The only notable gap is that a few Common Patterns lack explicit post-operation verification steps, which keeps workflow clarity just below the top anchor.

DimensionReasoningScore

Conciseness

The body is lean and dense — tables for command groups and gotchas, no explanations of concepts Claude already knows, and every line carries CLI-specific contract ('The CLI will NOT prompt when stdin is not a TTY', 'Error JSON goes to stderr'). Only the installation section repeats `resend --version` and could be trimmed slightly, which keeps it from drifting below the top anchor's fit.

5 / 5

Actionability

Commands are fully executable and copy-paste ready: `resend emails send --from "you@domain.com" --to user@example.com --subject "Hello" --text "Body"`, install commands, and `resend doctor -q`. The Common Mistakes table gives exact fixes with concrete flag names (`--column-map`, `;filename=`, `--yes`) rather than vague direction, covering the common cases.

5 / 5

Workflow Clarity

The domain setup flow is clearly sequenced with validation checkpoints (`domains create` → configure DNS → `domains verify` → `domains get` to check status), destructive operations are gated by `--yes`, and `--dry-run` payload validation is documented for send/batch/create. It is not a 5 because some patterns (e.g., the broadcast `--send` flow) omit an explicit post-send verification step; it is above 3 because validation is present in the key flows rather than absent.

4 / 5

Progressive Disclosure

SKILL.md is a genuine overview with a task-to-reference map ('When to Load References') covering all 18 bundle files, every referenced path exists on disk, and the references are one level deep (no reference file points to another). Detailed flag specifications are correctly deferred to the reference files, and navigation is easy.

5 / 5

Total

19

/

20

Passed

Description

92%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 specific, explicit about both capabilities and triggers, and firmly scoped to the Resend CLI niche. Trigger-term coverage is strong but misses a few natural synonyms a user might say, which is the only dimension below the top anchor.

DimensionReasoningScore

Specificity

It lists multiple concrete actions with comprehensive coverage of the platform: 'send emails (including React Email .tsx templates via --react-email), manage domains, contacts, broadcasts, templates, webhooks, API keys, logs, automations, and events via the `resend` CLI'. Not 4 — the action list spans the full command surface with a specific flag, leaving only minor gaps.

5 / 5

Completeness

It explicitly answers both questions: what ('Operate the Resend platform from the terminal — send emails... manage domains, contacts, broadcasts...') and when ('Use when the user wants to run Resend commands in the shell, scripts, or CI/CD pipelines, or send/preview React Email templates'). The 'when' clause uses concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'send emails', 'Resend commands', 'shell, scripts, or CI/CD pipelines', 'send/preview React Email templates', plus resource nouns users would say (domains, contacts, broadcasts, webhooks). Not 5 — a few natural synonyms are missing ('transactional email', 'email API', 'DNS/domain verification' as a trigger phrase).

4 / 5

Distinctiveness Conflict Risk

It occupies a clear niche — the Resend platform operated 'via the `resend` CLI' from the terminal — with distinct triggers (Resend commands, React Email templates) and minimal conflict risk; no other generic skill would capture these phrases.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

resend/resend-skills

Path

skills/resend-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.