configuration-registrations

caddy-security user registration Caddyfile configuration. Use when creating, reviewing, or modifying user registration blocks, registration titles and codes, dropbox files, terms and privacy links, accepted email domains, MX checks, email provider wiring, admin notification addresses, and identity store targets.

Quality

93%

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

87%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, action-oriented, and well-structured with a complete config template and concrete validation tooling. Its main gap is the absence of an explicit ordered workflow with validation checkpoints for the configuration task.

Suggestions

Add a short numbered workflow for creating a registration block (declare identity store → write registration block → wire email/messaging provider → validate with smtp-debug-server → confirm via the portal register URL) with an explicit validation checkpoint.

Make the destructive-path guidance explicit: state that repeated 'admin email' lines overwrite rather than append, so the user should validate the effective admin address list after editing.

Note that the referenced fixture files (testdata/...Caddyfile, assets/config/registrations_local.json) are external to this bundle; flag if they are not present so Claude does not assume they exist.

Dimension	Reasoning	Score
Conciseness	Lean and dense with non-obvious domain specifics (authcrunch parser behavior, injected 'kind local', portal limitations); it does not explain Caddy or basic concepts Claude already knows, so most tokens earn their place.	3 / 3
Actionability	Provides a complete, copy-pasteable Caddyfile block, an explicit supported-lines catalog, concrete fixture paths, and a runnable smtp-debug-server command on 127.0.0.1:1025 — fully executable guidance.	3 / 3
Workflow Clarity	Guidance is clear via the Shape template and supported-lines list, but there is no explicit sequenced workflow with validation checkpoints for the user performing the configuration, so it sits below the explicit-validation anchor.	2 / 3
Progressive Disclosure	A single self-contained SKILL.md with well-organized sections (Purpose, Shape, Required and Defaulted Fields, Supported Lines, Workflow Notes, Fixtures); the only references are one-level fixture paths and sibling skills, with no nested docs and no bundle files present to misorganize.	3 / 3
	Total	11 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 strong, specific description that clearly states both capability and use-when triggers with natural domain keywords. It is concise yet comprehensive and unlikely to conflict with other skills.

Dimension	Reasoning	Score
Specificity	Lists many concrete actions and objects — 'creating, reviewing, or modifying user registration blocks, registration titles and codes, dropbox files, terms and privacy links, accepted email domains, MX checks, email provider wiring, admin notification addresses, and identity store targets' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what ('caddy-security user registration Caddyfile configuration') and when ('Use when creating, reviewing, or modifying ...'), satisfying the explicit-trigger anchor for both.	3 / 3
Trigger Term Quality	Natural domain terms a caddy-security user would actually say are well covered: 'user registration', 'registration blocks', 'terms and privacy links', 'email domains', 'MX checks', 'email provider', 'identity store'.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to caddy-security user registration Caddyfile config with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
referenced_paths_exist	Referenced path issues: 3 missing, 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: greenpau/caddy-security
Path: .codex/skills/configuration-registrations/SKILL.md
Commit: b96087f

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