CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-messaging

Configure email, file and SQLite messaging providers, bounded delivery workers, SMTP transport, sender credentials and registration notifications.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/configuration-messaging/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 highly actionable, project-specific reference with complete config examples and honest coverage of upstream limitations (bcc/STARTTLS, template rendering gaps, delivery duplication). It would benefit from moving the SQLite outbox operational semantics into a reference file and tightening that section's dense prose.

Suggestions

Move the SQLite outbox worker/cleanup semantics (leases, acknowledgement budgets, crash-duplication caveats) into a dedicated reference file under references/ and link to it from a short overview in SKILL.md.

Convert the scattered verification guidance (file-provider smoke check, loopback SMTP evidence, RCPT TO inspection) into a short ordered checklist with explicit validation checkpoints.

Tighten the SQLite section's run-on sentences into short directive statements or a table of limits (lease 1m, ack 5s, SMTP cap 15s, poll 1s, timeout default 1s, range 1ms-30s).

DimensionReasoningScore

Conciseness

There is no general-concept padding, but the SQLite outbox section is dense run-on operational prose ("Transactions obtain exclusive access before mutation; ordinary reader/writer contention waits within the database deadline before admission") that is accurate yet noticeably verbose and could be tightened.

3 / 5

Actionability

Complete, copy-paste-ready Caddyfile blocks for email, file and SQLite providers plus registration wiring, with exact instruction names ("file providers use root_dir, not rootdir"), required directives, defaults and limits, and named validation surfaces.

5 / 5

Workflow Clarity

Verification guidance is present (disposable root_dir checks, loopback SMTP server, "inspect RCPT TO separately from headers", named test files) but it is scattered across sections rather than presented as a sequenced workflow with explicit checkpoints, leaving minor validation-flow gaps.

4 / 5

Progressive Disclosure

Sections are well organized and sibling-skill links are clearly signaled, but no bundle files exist and roughly 70 lines of SQLite worker lease/cleanup semantics are inlined in SKILL.md where they belong in a one-level-deep reference file.

3 / 5

Total

15

/

20

Passed

Description

66%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, third-person description that enumerates concrete configuration targets with good domain keyword coverage. Its main weakness is the absence of any "Use when..." trigger guidance, which both caps completeness and slightly weakens trigger discoverability.

Suggestions

Append an explicit trigger clause such as "Use when configuring messaging or notification providers in Caddyfile security blocks, or when registration, password recovery or MFA OTP email delivery is involved."

Add common user-facing synonyms (e.g., "mail server", "outbox", "password reset notifications") to improve trigger term coverage.

Consider splitting the single "Configure" verb into a couple of distinct actions (e.g., "Configure... and wire registration flows to named providers") to sharpen the capability list.

DimensionReasoningScore

Specificity

Names many concrete configuration targets ("email, file and SQLite messaging providers, bounded delivery workers, SMTP transport, sender credentials"), but a single verb "Configure" governs a list of objects rather than multiple distinct actions, leaving minor gaps versus the comprehensive anchor.

4 / 5

Completeness

The "what" is clearly stated (configure providers, workers, transport, credentials, notifications) but there is no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 3.

3 / 5

Trigger Term Quality

Natural domain terms like "email", "SMTP", "messaging", "registration notifications" and "credentials" are present, but common variations such as "mail server", "outbox" or "password reset" are missing, so it falls short of comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description is anchored to this app's specific messaging vocabulary ("SQLite messaging providers", "bounded delivery workers", "SMTP transport"), giving it a clear niche with only minor overlap risk against a sibling credentials skill.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 2 suspicious

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/configuration-messaging/SKILL.md

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.