CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-authentication

Configure authentication portals, backend selection, redirect trust, refresh, Documents storage, and portal wiring. Delegates cookies, UI, transforms, crypto, and OIDC provider details to focused skills.

Quality

76%

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/configuration-authentication/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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.

The body is a dense, project-specific configuration reference with a complete runnable example, concrete directive syntax, explicit ordering rules, and test-anchored verification — all without padding or generic explanations. Its progressive disclosure is exemplary, delegating detail to real, well-signaled reference files and sibling skills; the residual weaknesses are a few trimmable prose passages and the lack of an ordered end-to-end configuration procedure with validation loops.

DimensionReasoningScore

Conciseness

No tokens are spent on concepts Claude already knows; nearly every line carries project-specific facts ("`enable identity provider <name>` references `oauth identity provider <name>` or `saml identity provider <name>` blocks"; "The match type is optional and defaults to `exact`"). A few passages — the long "Read these files when details matter" clauses and the dense login-destination prose — could be trimmed, matching the 4 anchor of minor over-explanation rather than the fully lean 5.

4 / 5

Actionability

The Shape block is a complete, runnable portal-plus-route Caddyfile, and wiring, crypto, redirect trust, and admin API each get concrete directive syntax anchored to named tests and fixtures. Some guidance remains abstract ("search debug logs for configured portal access-list rules") and many topics resolve to delegation pointers, so it sits at "mostly executable with minor gaps" rather than fully copy-paste-ready.

4 / 5

Workflow Clarity

Sequencing is explicit where it matters ("Define those stores, identity providers, or SSO app providers with the matching domain skills before enabling them") and validation checkpoints exist via the Fixtures section ("must fail adaptation with a parser error, not a panic") and Acceptance criteria. However, there is no ordered end-to-end procedure for authoring and verifying a new portal configuration, leaving minor sequencing/validation gaps.

4 / 5

Progressive Disclosure

The body is a genuine overview that pushes deep detail to four real, one-level-deep `references/` files (token-refresh.md, refresh-storage.md, documents.md, login-destinations.md — all present in the bundle), each link accompanied by a summary of what it covers, plus clearly scoped delegation to sibling skills. Content is appropriately split and navigation is easy, matching the 5 anchor; it is not the 4 anchor because no inline section clearly belongs in a separate file.

5 / 5

Total

17

/

20

Passed

Description

66%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.

The description is specific and well-scoped, clearly stating what the skill configures and proactively disambiguating sibling skills through explicit delegation. Its main weakness is the absence of any "Use when..." trigger guidance, which both caps completeness and limits natural trigger-phrase coverage.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring authentication portal blocks, `authenticate with` handlers, or portal backend/redirect/refresh settings in Caddyfile security blocks."

Include natural user phrasings such as "login portal", "sign-in", or "JWT/token authentication" to broaden trigger-term coverage.

Convert noun-phrase capabilities into verb-led actions (e.g. "refreshes tokens", "wires portal routes") so every listed capability reads as a concrete action.

DimensionReasoningScore

Specificity

"Configure authentication portals, backend selection, redirect trust, refresh, Documents storage, and portal wiring" lists six concrete capability areas plus delegated scopes ("cookies, UI, transforms, crypto, and OIDC provider details"), but several items are verb-less noun phrases ("refresh", "portal wiring") leaving minor coverage gaps versus the fully action-verb 5 anchor.

4 / 5

Completeness

The "what" is clear and multi-part, but there is no "Use when..." clause or equivalent trigger guidance; the second sentence describes scope delegation, not usage timing, so per the rubric this caps completeness at 3.

3 / 5

Trigger Term Quality

Domain terms like "authentication portals", "redirect trust", "OIDC provider", "cookies", and "crypto" match what users of this plugin would naturally say, but common variations such as "login", "sign-in", "JWT", or "Caddyfile" are absent — good coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

"Configure authentication portals ... and portal wiring" carves a clear niche and "Delegates cookies, UI, transforms, crypto, and OIDC provider details to focused skills" explicitly routes overlaps away, but this ecosystem has many closely related sibling skills and terms like "crypto" and "cookies" still appear here, leaving minor overlap risk.

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, 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

.codex/skills/configuration-authentication/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.