CtrlK
BlogDocsLog inGet started
Tessl Logo

configuration-authorization

caddy-security authorization policy Caddyfile configuration. Use when creating, reviewing, or modifying security authorization policy blocks, route-level authorize directives, ACL rules, allow or deny shortcuts, bypass rules, crypto verification keys, auth redirects, bearer token validation, basic or API key auth proxy settings, user identity fields, and injected claim headers.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content is a well-structured, executable reference that respects the context budget, provides copy-paste-ready Caddyfile examples, and clearly signals where to read source files for deeper detail. It scores at the top of every dimension.

DimensionReasoningScore

Conciseness

The body is dense and lean — 'Defaults applied by `PolicyConfig.Validate()` and `Gatekeeper.configure()`:' followed by tight bullets — assuming Claude's competence with no padding or explanation of basic Caddy concepts, matching the 'every token earns its place' anchor.

3 / 3

Actionability

It provides fully executable Caddyfile blocks ('security { authorization policy app_policy { ... }}', 'allow roles authp/admin authp/user', 'bypass uri exact /healthz') and concrete curl commands, matching the 'copy-paste ready' anchor rather than the pseudocode score-2.

3 / 3

Workflow Clarity

As a single-purpose configuration reference organized into clear sections (Purpose, Shape, Runtime Defaults, ACLs, Policy Options, Fixtures) with unambiguous behavioral rules, it meets the simple-skill allowance for a top score, and no batch/destructive operations trigger the validation-loop cap.

3 / 3

Progressive Disclosure

It signals one-level-deep source references clearly ('Read these files when details matter', 'Use these examples') and keeps the overview inline while pointing outward, matching the 'clear overview with well-signaled one-level-deep references' anchor; no bundle files exist to verify against.

3 / 3

Total

12

/

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.

The description is a strong, concise statement of both capability and trigger conditions, with concrete actions and natural terminology that align tightly with the caddy-security authorization domain. It cleanly satisfies all four dimensions at the top of the scale.

DimensionReasoningScore

Specificity

The description lists many concrete actions — 'creating, reviewing, or modifying security authorization policy blocks, route-level authorize directives, ACL rules, allow or deny shortcuts, bypass rules, crypto verification keys' — matching the 'lists multiple specific concrete actions' anchor rather than the partial score-2.

3 / 3

Completeness

It states what the skill does ('caddy-security authorization policy Caddyfile configuration') and provides an explicit 'Use when...' clause enumerating trigger scenarios, matching the 'clearly answers both what AND when' anchor.

3 / 3

Trigger Term Quality

Natural user-facing terms like 'authorization policy', 'ACL rules', 'allow or deny shortcuts', 'bypass rules', 'bearer token validation', and 'basic or API key auth' provide good coverage, matching the score-3 anchor for natural keyword coverage.

3 / 3

Distinctiveness Conflict Risk

The caddy-security authorization policy niche with its specific Caddyfile triggers is clearly distinguishable and unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' anchor.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
greenpau/caddy-security
Reviewed

Table of Contents

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.