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".

68

Quality

81%

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

72%

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 executable code and well-organized sections, but it carries some duplication and lacks an explicit verification step in its build/deploy workflow, capping conciseness and workflow clarity at 2.

Suggestions

Consolidate the duplicated <Api.Mailer.Smtp> example: keep one canonical block (the full webiny.config.tsx) and have Core Pattern reference it, and list the build command once.

Add an explicit verification step to the workflow (e.g., after `yarn webiny build api`, send a test email or check logs) so the sequence has a validation checkpoint.

Fix the noisy `.env` snippet (`SMTP_PASSWORD = your - smtp - password - here;`) to a clean `SMTP_PASSWORD=your-secret` form to remove formatting artifacts.

DimensionReasoningScore

Conciseness

The body is mostly lean and avoids explaining concepts Claude already knows, but duplicates the <Api.Mailer.Smtp> component across Core Pattern and Full Example and repeats the build command in both Common Mistakes and Quick Reference; not level 3 because it could be tightened.

2 / 3

Actionability

It provides fully executable, copy-paste-ready code (the complete webiny.config.tsx example with env-var password), a props table, and exact build commands, matching the 'fully executable code/commands' anchor.

3 / 3

Workflow Clarity

The edit-config / set-env / build / deploy sequence is present but scattered across TL;DR, Common Mistakes, and Quick Reference with no explicit validation or test-email verification checkpoint; not level 1 because the steps are clear, not level 3 because checkpoints are missing/implicit.

2 / 3

Progressive Disclosure

With no bundle files needed, the body is organized into clearly signaled sections (TL;DR, Core Pattern, Props Reference, Full Example, Common Mistakes, Quick Reference, Related Skills) with no nested references, matching the well-organized single-purpose skill case.

3 / 3

Total

10

/

12

Passed

Description

90%

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-constructed: explicit trigger guidance, natural phrasing, and a clear Webiny SMTP niche. Its only weakness is that it describes one action rather than multiple concrete actions, capping specificity at 2.

DimensionReasoningScore

Specificity

It names a concrete action and domain ('configuring SMTP email/mailer settings in a Webiny project') but lists a single action with synonyms rather than multiple distinct concrete actions, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

An explicit 'Use when...' clause states what the skill does, and the 'Triggers on' list states when to use it, clearly answering both what and when — not level 2 because the when is explicit rather than implied.

3 / 3

Trigger Term Quality

The 'Triggers on' list gives strong natural-phrase coverage a user would actually say ('configure email', 'set up SMTP', 'email not working', 'sending emails') plus a code hook ('Api.Mailer.Smtp'), matching the 'good coverage of natural terms' anchor.

3 / 3

Distinctiveness Conflict Risk

It is scoped to a narrow niche (Webiny project SMTP mailer) with the distinct code hook 'Api.Mailer.Smtp', making conflict with other skills unlikely and matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

11

/

12

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.