configuration-users

caddy-security local user account Caddyfile configuration. Use when creating, reviewing, or modifying local identity store user entries, usernames, display names, email addresses, plaintext or bcrypt passwords, overwrite behavior, roles, static API key prefixes and payloads, and secret-backed user attributes.

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.

A dense, code-backed config skill with concrete examples and an explicit review checklist, but it lacks a stated validation feedback loop for the config operations it governs. Otherwise strong on actionability and organization.

Suggestions

Add an explicit validation feedback loop after the Review Checklist, e.g. 'If any check fails, fix the entry and re-run the checklist before emitting the Caddyfile.'

Framing the Review Checklist as numbered steps (generate entry -> run checklist -> fix failures -> re-check) would convert it from a constraint list into a true workflow with checkpoints.

Consider a short 'Verify against fixtures' step that names the exact caddyfile_identity_store_test.go command or adapt run to execute, turning the Fixtures section into an actionable verification step.

Dimension	Reasoning	Score
Conciseness	Lean and code-backed; it documents authcrunch/caddy-security internals Claude would not know without explaining generic concepts. Minor cross-section repetition of the 24-char key constraint is intentional reinforcement for a config skill rather than padding.	3 / 3
Actionability	Provides executable Caddyfile examples in the Shape and Secrets blocks plus exact subdirective syntax and concrete constraints (24-character key id, username length 3-50, password length 8-128), giving copy-paste-ready guidance.	3 / 3
Workflow Clarity	The Review Checklist supplies validation constraints, but there is no explicit generate -> validate -> fix -> re-validate feedback loop, which the rubric scoring notes expect for config/identity-store operations and thus caps this dimension at 2.	2 / 3
Progressive Disclosure	A single well-organized SKILL.md with clearly labeled sections (Purpose, Shape, Fields, Secrets, Review Checklist, Fixtures) and one-level, clearly signaled references to authoritative source files; no nested reference chains and no bundle files needed.	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 precise, third-person description that cleanly states both the capability and explicit use-when triggers scoped to caddy-security local user configuration. It is comprehensive yet concise with no padding or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating, reviewing, or modifying") and enumerates specific fields (usernames, display names, email addresses, plaintext or bcrypt passwords, overwrite behavior, roles, static API key prefixes and payloads, secret-backed user attributes).	3 / 3
Completeness	Explicitly answers what ("caddy-security local user account Caddyfile configuration") and when ("Use when creating, reviewing, or modifying local identity store user entries...") with an explicit Use-when trigger clause.	3 / 3
Trigger Term Quality	Covers the natural terms a user of this domain would say (local identity store user entries, usernames, bcrypt passwords, roles, static API key prefixes, secret-backed user attributes), matching the skill's niche vocabulary.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to caddy-security local user Caddyfile entries, making it unlikely to trigger for unrelated skills; uses third-person voice with no conflict-prone generic language.	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: 1 missing, 1 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: greenpau/caddy-security
Path: .codex/skills/configuration-users/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.