CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-state

Configure durable AuthCrunch runtime state, exclusive storage ownership, stop/start persistence, reload rejection, and recovery. Use for root state blocks and process-level restart guarantees.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

An exceptionally dense, contract-style skill body: fully executable configuration and test commands, explicit ownership boundaries, and real one-level-deep references with clear read conditions. The main gaps are trimmable inline test-coverage detail and the absence of an explicit failure-handling loop in the validation workflow.

Suggestions

Move the long TestCaddyRuntimeStateE2E and SQLite E2E coverage enumerations into the already-linked testing-and-ci test map, keeping a one-line summary plus the test names in SKILL.md.

Add an explicit feedback loop to the Validation section (e.g., if the focused go test run fails, fix the contract or implementation and re-run before any full regression) to strengthen workflow clarity.

Consider one complete minimal example (state block plus a portal or policy) instead of only the fragment, since the fragment currently requires assembling pieces from sibling skills.

DimensionReasoningScore

Conciseness

The body is dense contract prose with no padding and no explanations of concepts Claude already knows — every sentence carries ownership, lifecycle, or validation constraints. Minor trimming is possible: the ~20-line enumeration of TestCaddyRuntimeStateE2E coverage duplicates scope already delegated to the linked test-surfaces map, which keeps it at anchor 4 rather than 5.

4 / 5

Actionability

Fully concrete guidance throughout: a Caddyfile block, the exact JSON path and shape ("state":{"directory":"/var/lib/authcrunch/runtime"}), an explicit list of error conditions, named owning files and functions (caddyfile_state.go, NewStateConfigFromDirectives), and a copy-paste-ready command (go test -mod=readonly -race -count=1 -timeout=8m -run 'TestCaddyRuntimeStateE2E|TestPersistentApp' .). The common cases — enabling persistence, validating the contract, running focused tests — are all covered with executable specifics; the config snippet is deliberately a fragment and says why.

5 / 5

Workflow Clarity

A clear sequence with explicit checkpoints is present: check the module's public state and managed refresh APIs before changing the contract, run the exact focused test command, retain existing coverage, and route full regression through testing-and-ci. It falls short of anchor 5 because there is no failure-feedback loop (what to do when the focused tests fail) and the workflow is prose rather than a sequenced checklist.

4 / 5

Progressive Disclosure

Both bundle references (references/operations.md, references/consul-companions.md) exist, are one level deep, and are conditionally signaled ("Read [operator guidance](references/operations.md) when enabling persistence, planning deployment/recovery, or explaining its guarantees"). The body is well-sectioned, but the inline E2E coverage enumeration belongs in the already-linked test-surfaces map and the body carries substantial contract detail that could be split out, matching anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

75%Weight 40%Scale 1-5

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 specific, third-person description with an explicit trigger clause and a well-defined niche. It scores solidly across all dimensions but stops short of top marks: trigger coverage lacks natural synonyms, and the "when" clause names topics rather than concrete phrases users would say.

Suggestions

Add natural trigger variations users would actually say, such as "persist sessions across restarts" or "keep login state between reloads", to lift trigger term coverage toward synonyms-level.

Make the "Use for" clause more concrete and behavioral, e.g., "Use when configuring a `security { state { ... } }` block or when restart/reload must preserve sessions".

Name the Caddyfile surface (the `state` directive inside the security app) in the description to sharpen distinctiveness against sibling configuration skills.

DimensionReasoningScore

Specificity

"Configure durable AuthCrunch runtime state, exclusive storage ownership, stop/start persistence, reload rejection, and recovery" lists several specific capabilities. It falls short of anchor 5 because the actions are abstract noun phrases without a comprehensive concrete inventory (e.g., no mention of the state block's actual settings or directory handling), but clearly exceeds the 1-2 actions of anchor 3.

4 / 5

Completeness

Both a clear "what" (configure state, ownership, persistence, reload rejection, recovery) and an explicit "Use for..." trigger clause are present, so it is not capped at 3. The "when" ("root state blocks and process-level restart guarantees") is topic-shaped rather than the concrete trigger phrases of the anchor-5 example, matching anchor 4.

4 / 5

Trigger Term Quality

Natural domain terms are present ("root state blocks", "process-level restart guarantees", "persistence", "reload"), giving good keyword coverage. Common phrasings a user would naturally say are missing (e.g., "persist sessions across restarts", "keep state between reloads"), so it does not reach anchor 5's synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

"AuthCrunch runtime state", "exclusive storage ownership" and "reload rejection" carve a clear niche with low generic conflict risk. However, sibling skills in the same family (cross-device lifecycle, refresh storage, authorization) also discuss state and restart behavior — refresh-storage explicitly requires this root state block — so minor overlap with closely related skills keeps it at anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/configuration-state/SKILL.md

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.