configuration-credentials

caddy-security reusable generic credentials Caddyfile configuration. Use when creating, reviewing, or modifying security credentials blocks for reusable username/password credentials, optional domains, SMTP or email messaging authentication, registration email provider credentials, environment placeholders, or secret-backed credential values.

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, highly actionable, and well-organized with appropriate one-level references to fixture examples. Its main gap is the absence of an explicit validation/verification step for the conditional configuration decisions it describes.

Suggestions

Add a short 'Verify' step after the Shape example, e.g. reload/adapt the Caddyfile and confirm no parse error on unsupported inner keys, so a failed parse can be caught and corrected before proceeding.

Sequence the Guidance rules into a compact decision checklist (choose credentials vs secrets -> set required username/password -> add domain only if a consumer expects it -> coordinate with messaging provider), turning implicit conditional logic into an ordered workflow.

Note explicitly that `name`/`kind` must be omitted and that the block label becomes the credential name, paired with a quick validation cue that confirms the label matches the downstream consumer's reference.

Dimension	Reasoning	Score
Conciseness	The body is lean and adds only domain-specific knowledge Claude lacks (authcrunch credential parsing, credentials-vs-secrets semantics) without restating basics; not level 2 because there is little explanatory padding and every section earns its tokens.	3 / 3
Actionability	Provides copy-paste-ready Caddyfile blocks, an enumerated list of accepted directives, and exact lookup syntaxes ("{env.SMTP_PASSWORD}", "secrets:<secret_id>:<key>"); not level 2 because the examples are fully executable rather than pseudocode or incomplete.	3 / 3
Workflow Clarity	Guidance rules are clear but present as conditional decisions (credentials vs secrets, when to add domain, coordination with messaging) rather than a sequenced workflow, and there is no explicit validate-after-writing checkpoint despite parsing failing on unsupported keys; not level 1 because the rules are individually unambiguous, but not level 3 because no validation/feedback loop is given.	2 / 3
Progressive Disclosure	Content is organized into clearly labeled sections (Purpose, Credentials vs Secrets, Shape, Guidance, Fixtures) with the Fixtures section acting as a one-level-deep, clearly signaled pointer to example files, avoiding a monolithic wall or nested references; not level 2 because the structure and signaling are clean rather than improvised.	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, well-scoped description that pairs a precise what statement with an explicit and broad Use-when trigger clause. It is specific, distinctive, and complete without padding.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — "creating, reviewing, or modifying security credentials blocks" — plus the specific credential tuple (username/password, optional domain), matching the anchor for listing several specific concrete actions; it is not at level 2 because the actions are explicit and comprehensive rather than partial.	3 / 3
Completeness	Explicitly states what it does ("caddy-security reusable generic credentials Caddyfile configuration") and when to use it via a clear "Use when..." clause, satisfying both what and when; not level 2 because the when is explicit rather than implied.	3 / 3
Trigger Term Quality	Covers natural trigger variations a caddy-security user would say — "username/password credentials", "optional domains", "SMTP or email messaging authentication", "registration email provider credentials", "environment placeholders", "secret-backed credential values" — giving broad coverage; not level 2 because it lists many real phrasings instead of a few.	3 / 3
Distinctiveness Conflict Risk	The niche is tightly scoped to caddy-security reusable credentials blocks with distinct technical triggers, making accidental triggering of unrelated skills unlikely; not level 2 because the scope is unmistakably specific rather than merely "somewhat specific".	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

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