configuration-runtime-resolution

caddy-security runtime replacement guidance for Caddyfile configuration. Use when creating, reviewing, or modifying configs that rely on Caddy replacer placeholders, env placeholders, secrets manager lookups, resolved Caddyfile fixtures, runtime credential resolution, unresolved token checks, or caddyfile_resolve behavior.

Quality

86%

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 high-quality, self-contained reference skill: lean, concrete, and well-organized with executable snippets and an explicit field-resolution map. The only notable gap is workflow clarity, where the procedural guidance is branching and reference-style rather than a numbered, checkpointed sequence.

Suggestions

Add a short numbered workflow for adding a new placeholder-bearing field (check struct → decode/replace/encode → validate → add fixture → run TestResolveRuntimeAppConfig) with an explicit validation checkpoint so the sequence is unambiguous.

Call out the validation feedback loop as a step ("run TestResolveRuntimeAppConfig; it fails if any {env. token remains unresolved — fix and re-run") rather than describing the test behavior only in the Fixture Pattern section.

Dimension	Reasoning	Score
Conciseness	The body is lean and information-dense, assumes Claude's competence (no explanation of what Caddy or placeholders are), and every section earns its tokens with domain specifics Claude would not already know.	3 / 3
Actionability	Provides concrete caddyfile snippets, the exact secret-lookup syntax, specific field lists to resolve, and an explicit procedure (DecodeArgs, replace, EncodeArgs, validate) — copy-ready and specific rather than abstract.	3 / 3
Workflow Clarity	Validation feedback is mentioned (the test fails when unresolved {env. tokens remain) and a procedural branch exists for new fields, but it is presented as branching reference guidance rather than a clearly sequenced, checkpointed workflow, so checkpoints remain implicit.	2 / 3
Progressive Disclosure	No bundle files exist, so the skill is intentionally self-contained; it is well-organized into clear sections (Purpose, Replacement Forms, What Gets Resolved, Fixture Pattern, Guidance), which satisfies the well-organized-sections anchor for skills with no external reference needs.	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, specific description with an explicit Use-when trigger and a clear niche. Its main weakness is trigger-term quality: several listed terms are internal implementation/test jargon rather than phrases a user would naturally invoke.

Suggestions

Replace internal jargon triggers ("caddyfile_resolve behavior", "unresolved token checks", "resolved Caddyfile fixtures") with user-facing phrasing like "Caddyfile placeholders", "environment variable substitution", and "runtime secret resolution".

Lead with the natural verb a user would say (e.g., "Resolves runtime placeholders in Caddyfile configs...") so the most likely trigger phrase appears first.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating, reviewing, or modifying configs") tied to a specific capability (runtime replacement), matching the anchor for multiple specific concrete actions; it is not merely naming a domain.	3 / 3
Completeness	Clearly states what ("caddy-security runtime replacement guidance for Caddyfile configuration") and an explicit "Use when..." trigger clause, satisfying the both-what-and-when anchor.	3 / 3
Trigger Term Quality	Includes natural domain terms ("Caddyfile configuration", "env placeholders", "secrets manager lookups") but mixes in internal/test jargon ("caddyfile_resolve behavior", "unresolved token checks", "resolved Caddyfile fixtures") that users would not naturally say, so coverage is good but not cleanly natural.	2 / 3
Distinctiveness Conflict Risk	The caddy-security runtime-resolution niche is highly specific with distinct triggers, making conflict with other skills unlikely.	3 / 3
	Total	11 / 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-runtime-resolution/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.