CtrlK
BlogDocsLog inGet started
Tessl Logo

webiny-mailer-smtp

Use when configuring SMTP email/mailer settings in a Webiny project. Triggers on: "configure email", "set up SMTP", "mailer config", "sending emails", "email not working", "configure mailer", "SMTP password", "Api.Mailer.Smtp".

69

Quality

84%

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

78%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 tight, actionable, well-structured config skill that assumes Claude's competence and avoids concept explanations. The main weaknesses are a redundant second code example and a malformed .env snippet, plus an implicit rather than explicit validation checkpoint in the workflow.

Suggestions

Fix the .env example to valid syntax, e.g. `SMTP_PASSWORD=your-smtp-password-here` (no spaces, dashes-as-separators, or trailing semicolon).

Collapse the Core Pattern and Full Example code blocks or differentiate them more sharply (e.g., make Core Pattern the minimal snippet and Full Example show only the surrounding webiny.config.tsx wiring) to remove the duplicated props.

Make the build/verify step an explicit numbered checkpoint (edit -> set env var -> `yarn webiny build api` -> confirm settings applied) so the validation flow is unambiguous.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows (no "what is SMTP" prose), but the Full Example largely re-covers the same props already shown in Core Pattern, a minor redundancy that could be trimmed rather than a fully token-optimal layout.

4 / 5

Actionability

It provides copy-paste-ready JSX, a complete props table, build commands, and a Common Mistakes table with fixes, but the .env snippet ("SMTP_PASSWORD = your - smtp - password - here;") is malformed env syntax, a minor gap in an otherwise executable skill.

4 / 5

Workflow Clarity

The edit-config -> set-env-var -> build -> deploy sequence is clear from the TL;DR and Quick Reference, and the Common Mistakes table supplies error-recovery guidance; this is a simple single-purpose config skill, so it qualifies for a high score, though checkpoints are implicit rather than an explicitly numbered validated workflow.

4 / 5

Progressive Disclosure

The skill is self-contained with no bundle files, and uses a TL;DR overview followed by well-organized sections (Core Pattern, Props Reference, Full Example, Common Mistakes, Quick Reference, Related Skills) with clear headers and easy navigation, which is appropriate disclosure for a skill of this modest size.

5 / 5

Total

17

/

20

Passed

Description

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

A well-crafted description with an explicit Use-when clause, a rich set of natural trigger phrases, and a sharply scoped Webiny/SMTP niche. Its only limitation is that it names a single configuring action rather than enumerating multiple concrete capabilities.

DimensionReasoningScore

Specificity

The description names the domain ("configuring SMTP email/mailer settings in a Webiny project") but essentially describes a single action — configuring the mailer — rather than listing multiple concrete actions, matching the anchor that names the domain with 1-2 actions but is not comprehensive.

3 / 5

Completeness

It opens with an explicit "Use when..." clause stating what the skill does, then follows with a concrete "Triggers on:" list, clearly and explicitly answering both what AND when with concrete trigger phrases.

5 / 5

Trigger Term Quality

It lists eight explicit triggers covering natural synonyms users would say ("configure email", "set up SMTP", "mailer config", "sending emails", "email not working") plus the code identifier "Api.Mailer.Smtp", giving comprehensive coverage including synonym variations.

5 / 5

Distinctiveness Conflict Risk

The niche is narrow and specific (Webiny project + SMTP mailer + the Api.Mailer.Smtp identifier), giving clear distinct triggers with minimal risk of firing for an unrelated skill.

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
webiny/webiny-js
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.