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

86%

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.

A high-quality skill body: executable code examples, explicit verification and qualification guidance, and well-structured one-level-deep references into the bundle. The only weaknesses are minor — slightly loose prose in a couple of sections and the absence of an explicit validate-retry loop.

Suggestions

Tighten the "Published UI contract" and "Client Integration Patterns" prose into scannable bullet constraints to cut tokens without losing information.

For custom asset/template changes, add an explicit ordered verification checklist (adapt → check served paths/content types → test two portals + reload → fix and re-check) to give a full feedback loop.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific constraints (parser limitations, global asset registry effects, role requirements) and contains no general-knowledge padding, but sections like "Published UI contract" and "Client Integration Patterns" are prose that could be tightened slightly. Efficient with minor trimmable instances — above the 3 anchor, short of the every-token-earns-its-place 5.

4 / 5

Actionability

Fully executable guidance throughout: a complete `ui` Caddyfile block, `static_asset`/`custom css`/`custom js` snippets, copy-paste gotemplate fragments for refresh templates, exact source-file paths to consult, and a named fixture. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Sections are clearly sequenced by task area and validation is explicit ("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 explicit validate-fix-retry feedback loop. Clear sequence with most checkpoints — not the missing-checkpoint 3 nor the full feedback-loop 5.

4 / 5

Progressive Disclosure

Both bundle references (references/cross-device.md, references/localization.md) exist, are one level deep, and are clearly signaled with a summary of their contents ("Read [localization](references/localization.md) for the supported languages, portal/OP propagation, ..."). Core operating knowledge stays inline while detail is appropriately split out, making navigation easy.

5 / 5

Total

18

/

20

Passed

Description

83%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: specific, third-person, with an explicit use clause and an explicit boundary against a neighboring skill. The trigger coverage is good but omits a few natural phrasings, and the when-clause is narrower than the capability list.

DimensionReasoningScore

Specificity

"Configure portal UI templates, static assets, themes, languages, links, and custom CSS/JS/HTML" lists multiple specific concrete actions with comprehensive coverage of the skill's domain, in third person.

5 / 5

Completeness

Both what ("Configure portal UI templates, static assets, themes, languages, links, and custom CSS/JS/HTML") and when ("Use for branding and refresh-aware templates") are explicitly present, but the when-clause covers only a subset of the listed capabilities, so it could be more specific.

4 / 5

Trigger Term Quality

Natural terms like "branding", "templates", "themes", and "static assets" are present, but common user phrasings for this domain (e.g., logo, login/sign-in page, favicon) are missing. Good coverage, a few natural terms absent — not the comprehensive synonym coverage of a 5.

4 / 5

Distinctiveness Conflict Risk

"transform-generated links belong to user transforms" explicitly draws the boundary against the sibling skill, and the portal-UI niche is distinct with clear triggers, minimizing conflict risk.

5 / 5

Total

18

/

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.