configuration-messaging

Configure email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring. Use to distinguish parsed settings from actual delivery behavior.

Quality

88%

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

Quality

Content

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

An exemplarily dense, non-obvious configuration reference: executable examples, exact upstream directive names, and candid limitations (bcc header behavior, missing template loading, no E2E coverage). The only room for improvement is converting the prose verification guidance into a numbered workflow and splitting the long inline detail into reference files.

Suggestions

Restructure the verification guidance (file-provider local check and the SMTP loopback-server procedure) as numbered steps with an explicit validation checkpoint before declaring a sender change accepted.

Move the validated-template-ID default-file mapping and the detailed upstream bcc/sender limitations into a reference file (e.g. references/templates.md) and link to it, keeping SKILL.md as a tighter overview.

Dimension	Reasoning	Score
Conciseness	Lean, dense reference material with no padding: every line carries non-obvious facts (STARTTLS unsupported on smtp, bcc written as a header not RCPT TO, the email_templates asset-loader path stripping, absence of any registration SMTP E2E). Version pins ('In v1.3.4...') flag upstream behavior rather than branching instructions by date, so they earn their place.	5 / 5
Actionability	Two complete, copy-paste-ready Caddyfile blocks plus exact directive names ('use `root_dir`, not `rootdir`'), required-field lists per provider kind, and a concrete acceptance procedure for both file and SMTP verification.	5 / 5
Workflow Clarity	Verification guidance is genuinely present (disposable root_dir file-provider check, loopback SMTP server inspecting envelope recipients, named test fixtures), but it is delivered as prose rather than a numbered sequence with explicit checkpoints — matching the 4 anchor, not 5's explicit validate-fix-retry steps.	4 / 5
Progressive Disclosure	Well-organized sections with clearly signaled one-level-deep links to sibling skills (configuration-credentials, configuration-registrations) and no nested references. However, at ~155 lines with all detail inlined (template default-file mapping, bcc behavior specifics) and no bundle files to split it into, it sits at 4 rather than 5.	4 / 5
	Total	18 / 20 Passed

Description

83%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 specific, well-scoped description that names concrete capabilities and stays in third person with an explicit use clause. Its weakest points are the missing natural trigger synonyms and a 'when' clause that describes purpose rather than user-facing triggers.

Suggestions

Rewrite the use clause as concrete user triggers, e.g. 'Use when the user mentions email/SMTP setup, registration confirmation emails, password recovery messages, or MFA OTP delivery.'

Add the natural terms users would say for this domain — 'notifications', 'password recovery', 'MFA OTP' — so the description matches how requests are actually phrased.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete configuration actions covering the skill's full scope — 'email and file messaging providers, SMTP transport, sender/authentication, templates, and registration delivery wiring' — with no coverage gaps.	5 / 5
Completeness	A clear 'what' is paired with an explicit 'Use to distinguish parsed settings from actual delivery behavior' clause, but that clause states purpose rather than concrete user trigger phrases, so it stops short of the 5 anchor.	4 / 5
Trigger Term Quality	Good natural keyword coverage ('email', 'SMTP', 'messaging', 'sender', 'templates', 'registration delivery') but omits common user phrasings like 'notifications', 'password recovery', or 'MFA/OTP' that the skill actually handles.	4 / 5
Distinctiveness Conflict Risk	Clear niche — messaging provider configuration in the Caddy/authcrunch domain — with distinct triggers like 'SMTP transport' and 'registration delivery wiring', giving minimal overlap risk with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

Repository: greenpau/caddy-security
Path: .codex/skills/configuration-messaging/SKILL.md
Commit: a48553d

Reviewed: 9 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.