configuration-crypto

caddy-security crypto directive configuration for authentication portals and authorization policies. Use when creating, reviewing, or debugging crypto Caddyfile lines, JWT signing or verification keys, token names and lifetimes, key IDs, HMAC/RSA/ECDSA key loading, auto-generated keys, env or secrets-backed crypto values, System API crypto keys for remote Basic/API-key authentication, and authenticate/authorize key compatibility.

Quality

82%

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

65%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 thorough, highly actionable reference for the crypto directive with concrete examples and debugging guidance, but it is longer than necessary with redundant example blocks and lacks progressive disclosure or explicit validation feedback loops for its crypto-config workflow.

Suggestions

Consolidate the duplicated env/secret and portal-policy pairing examples that recur across 'Supported Forms', 'Env And Secrets', 'System API Keys', and 'Token Discovery' to tighten the body and reduce repetition.

Add an explicit validation feedback loop (e.g., 'run caddy validate/adapt, fix the crypto line, re-validate') in the Failure Patterns or Mental Model section to raise workflow clarity for this validation-sensitive config.

Move the exhaustive 'Supported Forms' grammar and detailed Key Material rules into a references/ file referenced one level deep from SKILL.md to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence (no explanation of JWT/HMAC/PEM), but at ~300 lines it repeats guidance across sections (env patterns in both 'Supported Forms' and 'Env And Secrets'; portal/policy pairing in 'Common Pairing', 'System API Keys', and 'Token Discovery'), fitting the score-2 'mostly efficient but could be tightened' anchor rather than the lean score-3.	2 / 3
Actionability	Provides copy-paste-ready Caddyfile snippets, concrete defaults (token name 'access_token', lifetime 900, ES512), an exhaustive supported-forms grammar, and specific debugging steps, matching the score-3 'fully executable code/commands; copy-paste ready' anchor.	3 / 3
Workflow Clarity	It describes a resolution-to-provisioning sequence and diagnostic failure patterns, but for validation-sensitive crypto config there are no explicit 'validate then proceed' feedback-loop checkpoints, fitting the score-2 'steps present but checkpoints missing or implicit' anchor.	2 / 3
Progressive Disclosure	No bundle files exist; all detail (full form grammar, key material, System API section) is inline in one well-sectioned but monolithic SKILL.md, matching the score-2 'content that should be separate is inline' anchor rather than score-3's one-level-deep reference structure.	2 / 3
	Total	9 / 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, highly specific description that clearly states both the capability and explicit use-when triggers for a well-scoped niche. It uses third-person voice and avoids vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names the concrete domain ('crypto directive configuration for authentication portals and authorization policies') and lists many specific items (JWT signing/verification keys, token names and lifetimes, key IDs, HMAC/RSA/ECDSA key loading, System API crypto keys), matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicitly answers both what (crypto directive configuration for portals and policies) and when via an explicit 'Use when creating, reviewing, or debugging...' trigger clause, matching the score-3 anchor.	3 / 3
Trigger Term Quality	Covers the natural terms a caddy-security user would say ('crypto Caddyfile lines', 'JWT signing', 'HMAC/RSA/ECDSA', 'System API crypto keys') across the main variations, exceeding the score-2 'some relevant keywords but missing common variations' anchor.	3 / 3
Distinctiveness Conflict Risk	The niche is highly specific ('caddy-security crypto directive', 'System API crypto keys for remote Basic/API-key authentication') with distinct triggers unlikely to conflict with other skills, matching the score-3 anchor.	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-crypto/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.