CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-authentication-ui

Configure portal UI templates, static assets, themes, languages, links, and custom CSS/JS/HTML. Use for branding and refresh-aware templates; transform-generated links belong to user transforms.

Quality

84%

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

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

High-quality reference skill content: executable syntax for every supported UI form, explicit negative guidance (what the parser does not support), and an honest acceptance-limits section that tells the reader exactly what the fixture does not qualify. The only real weakness is occasional tangled prose in the cautionary sections that could be tightened without losing information.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain knowledge (the only registered theme, unsupported directives, global registry effects, qualification limits) with no filler or explanations of concepts Claude already knows; a few cautionary passages are convolutedly worded and could be tightened (e.g., 'Do not promise independent branding for portals registering the same asset paths or repeatable header injection across adaptations').

4 / 5

Actionability

Fully executable guidance throughout: a copy-paste-ready Caddyfile `ui` block, exact `static_asset` and `custom css path` syntax, working gotemplate fragments with real variable names, exact source-file paths to consult, and a named adaptation fixture; the examples cover the common configuration cases.

5 / 5

Workflow Clarity

The content is organized per topic with explicit verification checkpoints ('verify served paths/content types, intended page inclusion, missing-input failure, and behavior across two portals and reload'; 'a custom template needs its own actual browser evidence'), but there is no sequenced workflow with feedback loops — appropriate for a configuration reference, though it keeps it just short of the top anchor.

4 / 5

Progressive Disclosure

The body serves as a well-organized overview while deeper detail is split into two real, one-level-deep references (references/cross-device.md and references/localization.md), each clearly signaled with a description of what it contains; navigation to source files and sibling skills is explicit and unambiguous.

5 / 5

Total

18

/

20

Passed

Description

78%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 strong description: it concretely enumerates the skill's capability surface, includes an explicit 'Use for' trigger, and actively disambiguates against a neighboring skill. The main gaps are a single generic verb ('Configure') carrying all actions and a 'when' clause that names use cases rather than concrete user-side trigger phrases.

Suggestions

Add one or two more concrete action verbs to the capability list (e.g., 'Set portal themes and languages, override login/session templates, register static assets and custom CSS/JS') so the 'what' reads as distinct actions rather than one verb plus a noun list.

Make the 'when' clause more trigger-like by naming user-side scenarios, e.g., 'Use when the user asks to customize the sign-in portal's appearance, branding, or login/session templates.'

Consider mentioning 'Caddy' or 'Caddyfile' explicitly, since users working in this codebase would likely phrase requests in those terms.

DimensionReasoningScore

Specificity

The description enumerates the full capability surface concretely ("portal UI templates, static assets, themes, languages, links, and custom CSS/JS/HTML"), but relies on a single action verb ('Configure') applied to a noun list rather than multiple distinct concrete actions, leaving minor gaps versus a comprehensive action-level enumeration.

4 / 5

Completeness

Both 'what' (configure portal UI templates, static assets, themes, languages, links, custom CSS/JS/HTML) and 'when' ('Use for branding and refresh-aware templates') are explicit, plus a boundary clause for transform-generated links; the 'when' could be more concrete since it lacks user-side trigger scenarios.

4 / 5

Trigger Term Quality

Good natural keyword coverage ('portal UI', 'templates', 'themes', 'branding', 'custom CSS/JS/HTML'), but a few natural terms a user would plausibly say are missing, such as 'Caddy'/'Caddyfile', 'sign-in page', or 'login page'.

4 / 5

Distinctiveness Conflict Risk

Clear niche (embedded authentication portal UI configuration) with an explicit disambiguation clause ('transform-generated links belong to user transforms') that steers routing away from a sibling skill, minimizing conflict risk.

5 / 5

Total

17

/

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: 5 suspicious

Warning

referenced_paths_exist

Referenced path issues: 4 missing, 4 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

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