CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

62

Quality

78%

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

Quality

Content

75%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 dense, expertly targeted reference skill: concrete Caddyfile and template examples, explicit parser limits, honest qualification limits, and clear pointers to source files and fixtures. It uniformly lands at 4 rather than 5 due to a version pin, no runnable verification command for the fixture, and inline detail that could be split into bundled reference files.

Suggestions

Add the command(s) to run the adaptation fixture (e.g., the caddy adapt or go test invocation) so the verification guidance in "Acceptance and qualification limits" is executable.

Move the v1.3.3 version reference and the refresh-template/session-template fragments into a bundled reference file under references/ so SKILL.md stays a stable overview.

Trim the overlap between "Published UI contract" and the later Custom Assets / Languages sections so each fact appears once.

DimensionReasoningScore

Conciseness

Lean, repo-specific guidance that assumes competence and explains only non-obvious constraints (global template/asset registries, parser limitations); minor trimming opportunities remain, such as overlap between the "Published UI contract" section and later sections, and a version pin ("The v1.3.3 embedded portal") that will age.

4 / 5

Actionability

Provides a copy-paste-ready Caddyfile ui block, concrete static_asset and custom css/js paths, executable gotemplate fragments (explicitly labeled as fragments), a fixture path, and a pointed reading list. The minor gap keeping it from 5 is the absence of any command for actually running the fixture/adaptation test it leans on.

4 / 5

Workflow Clarity

Organized per task area with an explicit validation section ("verify served paths/content types, intended page inclusion, missing-input failure, and behavior across two portals and reload"), giving most checkpoints; the gap is that no ordered sequence or fix-and-retry feedback loop is laid out.

4 / 5

Progressive Disclosure

Well-sectioned body with a clearly signaled one-level-deep "Read these files when details matter" list and cross-links to sibling skills; however, the skill ships no bundle files, all pointers are external to the skill, and refresh-template internals sit inline where a dedicated reference file could carry them.

4 / 5

Total

16

/

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 strong description with a concrete, comprehensive enumeration of what it configures, an explicit Use-for clause, and deliberate boundary marking against a sibling skill. It sits just below the top anchors because the when-clause covers only branding and refresh-aware templates, and a few natural trigger terms (logo, sign-in page, Caddyfile) are missing.

Suggestions

Broaden the Use-for clause to cover the full configuration surface, e.g. "Use for branding, portal theming, sign-in page customization, or refresh-aware template work".

Add the natural terms users are likely to say, such as "logo", "sign-in/login page", and "Caddyfile ui block", to the trigger coverage.

DimensionReasoningScore

Specificity

Enumerates six-plus concrete configurable elements ("portal UI templates, static assets, themes, languages, links, and custom CSS/JS/HTML") plus a scope boundary, but relies on a single action verb rather than multiple distinct actions, so it falls just short of the comprehensive multi-action anchor.

4 / 5

Completeness

Both answered: the "what" is a full enumeration of configurable UI elements and the "when" is explicit ("Use for branding and refresh-aware templates"). Not a 5 because the "when" clause covers only part of the "what" surface and lacks concrete user-mention phrasing.

4 / 5

Trigger Term Quality

Good natural keywords users would say ("branding", "templates", "themes", "custom CSS/JS/HTML", "static assets"), but common variations such as "logo", "sign-in/login page", or "Caddyfile" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche (portal UI customization) with an explicit disambiguation clause ("transform-generated links belong to user transforms") that actively prevents mis-triggering to the sibling transforms skill; minor overlap remains with the parent authentication-configuration and cross-device skills.

4 / 5

Total

16

/

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