CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

coding-directives

Implement or review caddy-security Go code, Caddy modules, parsers, lifecycle, and HTTP delegation. Use for app/plugin boundaries, authcrunch integration, errors, logging, and code conventions.

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/coding-directives/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

68%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 unusually concrete, deeply project-specific rulebook: every section names real files, functions, tests, and contracts, and the bundle references are real and well-signaled one level deep. The main costs are length — the sibling-boundary and parser-syntax sections repeat themselves and could be tightened — and the absence of an explicit ordered change workflow, leaving the reader to sequence the (well-specified) validation checkpoints themselves.

Suggestions

Consolidate the Repository Scope section into one statement of the boundary plus one paragraph of the xcaddy-workspace exception; the rule is currently restated across five paragraphs.

Add a short ordered 'typical change workflow' (code → parser unit tests → caddyfile_adapt fixtures → resolved.json when runtime output changes → selected test run → skill/reference updates) so the existing checkpoints have an explicit sequence.

Move the detailed refresh/session/logout and OIDC dispatch contract specifics from HTTP Handlers into the already-linked feature references, keeping only the boundary rules in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and almost entirely free of explanations of concepts Claude already knows, but it is noticeably tighten-able: the Repository Scope section restates the sibling-write boundary across five paragraphs ('This boundary covers creating, editing, deleting, restoring, staging, and committing files...'), and the Caddyfile Parsers section runs long on caveat phrasing. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the minor-trims-only anchor 4, while being far from the padded anchor 2.

3 / 5

Actionability

For an instruction-only skill the guidance is fully executable: exact parser signature 'func parseCaddyfileSurface(d *caddyfile.Dispenser, cfg *authcrunch.Config) error', concrete APIs (d.RemainingArgs(), d.Nesting(), d.ArgErr(), d.Errf), exact fixture paths and file names ('testdata/caddyfile_adapt/', '<prefix>.Caddyfile', '<prefix>_resolved.json', 'TestResolveRuntimeAppConfig'), named tests, the xcaddy --with argument, and named interfaces to guard. Specific identifiers cover the common change cases, matching 'fully executable... specific examples cover the common cases'.

5 / 5

Workflow Clarity

The body is organized as topical directives rather than a sequenced workflow; checkpoints exist ('Before a mutating command, confirm its repository root...', 'After fixture or parser work, run the selected tests', plus an acceptance-criteria checklist) but the end-to-end sequence for a typical change — code, parser tests, adapt fixtures, resolved.json, skill updates, license decision — must be assembled by the reader across sections. That matches 'steps present but checkpoints implicit/missing' more than 'clear sequence with most checkpoints present'.

3 / 5

Progressive Disclosure

The two bundle references (references/runtime-lifecycle.md, references/host-plugins.md) exist, are one level deep, and are clearly signaled with what each owns ('read [Runtime lifecycle](references/runtime-lifecycle.md). It traces Caddy's host ordering...'). It is not 5 because the SKILL.md itself carries substantial contract detail inline (e.g., the HTTP Handlers refresh/session/logout specifics) and leans on roughly eight cross-skill links to sibling SKILL.md files, which spreads a single task's guidance across many files beyond this bundle; it is well above the buried-reference anchor 3.

4 / 5

Total

15

/

20

Passed

Description

70%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 tight, third-person description that clearly states what the skill does and includes an explicit 'Use for' clause with strong repo-specific keywords. Its main weaknesses are the thin action vocabulary (only 'implement or review') and trigger conditions phrased as abstract topics rather than natural user phrases, which leaves a few common terms like 'Caddyfile' uncovered.

Suggestions

Replace the single verb pair 'Implement or review' with several distinct concrete actions (e.g., 'Implement, review, and debug Caddy modules, Caddyfile parsers, and HTTP middleware wiring').

Use natural user trigger phrases in the 'Use for' clause — e.g., 'Use when editing Caddyfile syntax, adding a Caddy module or plugin, wiring authcrunch integration, or reviewing parser/lifecycle behavior'.

Add the high-frequency synonyms users actually say — 'Caddyfile', 'portal', 'gatekeeper' — to improve trigger coverage.

DimensionReasoningScore

Specificity

The description names a highly specific domain ("caddy-security Go code, Caddy modules, parsers, lifecycle, and HTTP delegation") but offers only two generic actions ("Implement or review"), matching the anchor 'names domain and 1-2 concrete actions'. It is not score 4 because it never lists several distinct concrete actions (compare 'Extracts text, fills forms, converts pages'), and not score 2 because the domain enumeration is far richer than 'Processes PDF files'.

3 / 5

Completeness

Both parts are present: the 'what' is explicit ("Implement or review caddy-security Go code, Caddy modules, parsers...") and the 'when' uses an explicit "Use for" clause, so the missing-trigger cap of 3 does not apply. It stays at 4 rather than 5 because the trigger conditions are abstract topic areas ("app/plugin boundaries", "code conventions") rather than concrete user-facing trigger phrases like 'when the user mentions Caddyfile syntax or authcrunch integration'.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms a contributor would say: "Caddy modules", "parsers", "lifecycle", "authcrunch", "errors", "logging", "code conventions". It misses a few natural variations users would plausibly say — notably "Caddyfile" (only implied by "parsers"), plus "portal", "gatekeeper", or "plugin" — so it falls just short of the comprehensive-synonym anchor 5 and above the sparse 'Works with PDF files' anchor 3.

4 / 5

Distinctiveness Conflict Risk

The caddy-security/Caddy-module/parser framing gives it a clear niche with minimal conflict against unrelated skills, fitting 'mostly distinct; minor overlap risk'. It is not 5 because the trailing triggers "errors, logging, and code conventions" are broad and could pull in tasks owned by sibling skills in the same suite (e.g., a configuration-logging or general conventions skill), and not 3 because the core triggers are unmistakably repo-specific.

4 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 13 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/coding-directives/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.