configuration-secrets

caddy-security secrets manager Caddyfile configuration. Use when creating, reviewing, or modifying security secrets blocks, external security.secrets modules, static secrets manager examples, AWS secrets manager examples, secret IDs, secret-backed user data, authdbctl-generated password or API key hashes, secret-backed crypto keys, and integration with runtime replacement.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

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 focused, actionable configuration skill with executable examples and clean section organization. The main gap is workflow clarity: the generate-store-reference flow lacks explicit validation checkpoints despite involving secret values that fail provisioning on misuse.

Suggestions

Add an explicit ordered workflow (e.g., 1. generate hash with authdbctl, 2. store only the value in the secrets block, 3. reference via secrets:<id>:<key>, 4. verify the lookup resolves to a string) with a validation step before considering the config complete.

Surface the strict-resolution failure modes (three-field split, non-string value error, secret_id match) as an inline checklist alongside the workflow rather than only as explanatory notes.

Clarify when to use static_secrets_manager vs aws_secrets_manager up front (e.g., a one-line decision rule) so the reader picks the right path without scanning both sections.

Dimension	Reasoning	Score
Conciseness	The body is lean and domain-specific, assuming Claude's competence — it does not explain what bcrypt, Caddy, or secrets managers are, and every section earns its place with concrete Caddyfile snippets and commands.	3 / 3
Actionability	It provides copy-paste-ready Caddyfile blocks and executable `authdbctl generate password hash` / `authdbctl generate api key` commands with concrete flag examples, fully actionable rather than descriptive.	3 / 3
Workflow Clarity	Sequences are present (generate hash -> store in secrets block -> reference via secrets:<id>:<key>) and a Validation Notes section describes expected errors, but there are no explicit validate-then-proceed checkpoints or feedback loops tying the steps together, so it stops at 2 rather than 3.	2 / 3
Progressive Disclosure	The skill is a single well-organized SKILL.md with clearly labeled sections and one-level-deep references to specific repo paths (authdbctl README, testdata fixture, caddyfile_resolve_test.go) collected in a Fixtures section, with no nested reference chains.	3 / 3
	Total	11 / 12 Passed

Description

85%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, third-person description that clearly states its purpose and gives an explicit "Use when" trigger with concrete actions. Its main weakness is trigger-term naturalness: the keyword list is jargon-heavy and would benefit from plainer user-facing phrasing.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — "creating, reviewing, or modifying security secrets blocks", "secret-backed user data", "authdbctl-generated password or API key hashes" — matching the anchor for multiple specific concrete actions.	3 / 3
Completeness	It explicitly states what the skill does ("caddy-security secrets manager Caddyfile configuration") and provides an explicit "Use when..." trigger clause covering many scenarios, satisfying both what and when.	3 / 3
Trigger Term Quality	It includes relevant domain keywords ("secrets manager", "AWS secrets manager", "secret IDs", "bcrypt") but leans heavily on internal jargon ("security.secrets modules", "authdbctl-generated") and lacks the common natural phrasings a user would say, so it is not a full 3.	2 / 3
Distinctiveness Conflict Risk	The niche is narrow and specific to caddy-security secrets configuration, with distinct triggers unlikely to conflict with other skills.	3 / 3
	Total	11 / 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-secrets/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.