CtrlK
BlogDocsLog inGet started
Tessl Logo

add-resend

Add Resend (email) channel integration via Chat SDK.

62

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/add-resend/SKILL.md
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.

The body is highly actionable with a clear validated workflow and lean prose; the only slack is minor wording that could tighten conciseness and the option to split reference-like sections into files. Strong content overall.

Suggestions

Trim a few explanatory asides (e.g. the build-guards sentence) to tighten conciseness toward 5.

Consider moving Channel Info and Troubleshooting into references/ files linked from the body to push progressive disclosure to 5.

DimensionReasoningScore

Conciseness

Largely efficient and assumes competence, with only minor over-explanation of directive semantics and build rationale that could be trimmed slightly.

4 / 5

Actionability

Provides fully executable, copy-paste-ready nc: directives and real shell commands (pnpm run build, ncl users create, env-set block) covering the common cases.

5 / 5

Workflow Clarity

Clear numbered Apply sequence with explicit build/test validation checkpoints and a drift-detecting test that forms an error-recovery feedback loop.

5 / 5

Progressive Disclosure

Single well-sectioned SKILL.md with no nested references; good organization, though Channel Info and Troubleshooting could optionally live in separate files.

4 / 5

Total

18

/

20

Passed

Description

57%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 and distinctive but omits explicit usage-trigger guidance and lists only one action, so it caps on completeness and trigger-term breadth. Adding a "Use when..." clause and synonyms would lift it.

Suggestions

Append a "Use when adding email via Resend, wiring a Resend channel, or the user mentions Resend/email outreach." trigger clause.

Add a couple of synonym terms (e.g. "mail", "messaging", "inbox") to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (Resend, email, channel integration) and one concrete action ("Add ... integration"), but lists only a single action rather than several specific actions.

3 / 5

Completeness

States a clear "what" (add Resend email channel integration) but lacks any explicit "Use when..." trigger clause, which caps completeness at 3 per the guideline.

3 / 5

Trigger Term Quality

Contains relevant natural terms ("Resend", "email", "channel") but misses common variations and synonyms (no "mail", "messaging", "inbox", or file extensions).

3 / 5

Distinctiveness Conflict Risk

"Add Resend (email) channel integration" targets a clear vendor-specific niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

14

/

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
nanocoai/nanoclaw
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.