Name: webiny-api-mailer-catalog
Rating: 52 (1 reviews)
Author: webiny

Blog Docs Log in Get started

webiny-api-mailer-catalog

api/mailer — 11 abstractions.

Quality

57%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/user-skills/generated/api/mailer/SKILL.md

Quality

Content

82%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 an efficient, well-structured abstraction catalog with copy-paste imports and exact source paths, plus a concise usage workflow. Its only weakness is that it points Claude to read source files for interfaces rather than surfacing the key signatures inline.

Dimension	Reasoning	Score
Conciseness	The body is a lean catalog: each entry is just Name/Import/Source with no padding and no explanation of concepts Claude already knows, so every token earns its place.	5 / 5
Actionability	Each abstraction ships a copy-paste-ready import line and a precise source path, but step 2 defers exact interfaces/types to 'read the source file' rather than providing them inline, leaving a minor gap.	4 / 5
Workflow Clarity	The 'How to Use' section gives a clear 4-step sequence (find -> read source -> import -> consult pattern skills); no validation checkpoints are needed since the skill is a non-destructive catalog, but the steps lack explicit verification of the chosen abstraction.	4 / 5
Progressive Disclosure	Content is well-organized into a How-to-Use overview plus a uniformly-structured Abstractions section with one-level references to source files and related pattern skills; no bundle files are needed for this self-contained catalog, but all 11 entries are inlined rather than split.	4 / 5
	Total	17 / 20 Passed

Description

32%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 concise and pins a specific package niche, but it states only a domain and a count with no concrete actions and no trigger guidance, so it fails to tell Claude when to invoke it. It reads as a label rather than an activation phrase.

Suggestions

Add a 'Use when ...' clause naming concrete trigger situations, e.g. 'Use when extending or calling the api/mailer package — sending mail, reading/saving mailer settings, or hooking mailer events.'

Replace the bare count ('11 abstractions') with 2-3 concrete capabilities (e.g. 'send mail, manage mailer settings, and handle before/after send events').

Drop the jargon word 'abstractions' in favor of user-natural terms like 'repositories, use cases, and event handlers'.

Dimension	Reasoning	Score
Specificity	The description 'api/mailer — 11 abstractions.' names the domain and gives a count but lists no concrete actions or capabilities, matching the anchor 'Names the domain but actions are minimal or generic'.	2 / 5
Completeness	It offers only a vague 'what' (a count of abstractions for a package) and entirely omits any 'when to use' guidance; the missing 'Use when...' clause also caps completeness at 3, and this sits below that at 2.	2 / 5
Trigger Term Quality	It contains one concrete identifier ('api/mailer') a developer might reference, but 'abstractions' is technical jargon and no natural user-facing phrases are present, falling between the pure-jargon anchor (1) and the generic-keyword anchor (2).	2 / 5
Distinctiveness Conflict Risk	The specific package name 'api/mailer' carves a clear niche with minimal conflict risk beyond closely related webiny catalog skills, matching 'Mostly distinct; minor overlap risk'.	4 / 5
	Total	10 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: webiny/webiny-js
Path: skills/user-skills/generated/api/mailer/SKILL.md
Commit: d98a4e8

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.