Tessl • The management layer for AI agent skills

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/configuration-authentication/SKILL.md

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.

The body is a strong, information-dense configuration skill: executable caddyfile examples, explicit ordering constraints, acceptance criteria, and excellent one-level-deep reference navigation with verified files. The only real gaps are minor redundancy in examples and the lack of an explicit validation feedback loop.

Suggestions

Deduplicate the crypto example (it appears verbatim in both Shape and Common Portal Options).

Add a short validate-and-iterate step, e.g. run the named adaptation tests (`TestParseCaddyfileRedirectTrust*`) after editing a portal block and fix before proceeding.

Trim the portal-naming style paragraph in Shape or compress it to one line to save tokens.

Dimension	Reasoning	Score
Conciseness	The body is dense with non-derivable, repo-specific facts ("a portal must have at least one identity store or identity provider", test names, parser behavior) and assumes competence throughout. Not 5 because of minor trims available: the crypto lines are repeated in both Shape and Common Portal Options, and the portal-naming style paragraph is advisory padding.	4 / 5
Actionability	Copy-paste-ready caddyfile blocks cover the common cases (portal block, backend enabling, crypto keys, redirect trust, admin api), with inline executable syntax ("enable user registration <name>", match-type lists) and named fixtures/tests to reuse. Coverage is concrete end to end.	5 / 5
Workflow Clarity	Sequencing is explicit ("Define those stores... before enabling them", route wiring delegated to configuration-http-integrations) and validation is present via the Acceptance criteria section and named tests. Not 5 because there is no explicit run-test/fix/retry feedback loop for adapting or troubleshooting configurations.	4 / 5
Progressive Disclosure	Clear overview body with well-signaled, one-level-deep references — all four cited files (token-refresh.md, refresh-storage.md, documents.md, login-destinations.md) exist and each citation states what it covers; detail is pushed to references and Go source files. Cross-links inside references point laterally to sibling skills, not to deeper chains.	5 / 5
	Total	18 / 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, naming concrete capabilities and explicitly fencing off adjacent topics to reduce skill-selection conflicts. Its main weakness is the complete absence of "when to use" trigger guidance, which caps completeness and limits natural trigger terms.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring an authentication portal block or the route-level authenticate with <portal> handler."

Include natural user phrasing such as "login", "portal", and "Caddyfile authentication" alongside the current capability nouns.

Name the product/ecosystem (e.g. Caddy/authcrunch) so the skill is distinguishable from unrelated authentication skills.

Dimension	Reasoning	Score
Specificity	Phrases like "Configure authentication portals, backend selection, redirect trust, refresh, Documents storage, and portal wiring" list several concrete, domain-specific capabilities. Not 5 because "refresh" and "portal wiring" are terse rather than fully specified actions, leaving minor coverage gaps.	4 / 5
Completeness	The "what" is clear (configure portals, backend selection, redirect trust, refresh, Documents storage), but there is no "Use when..." clause or equivalent explicit trigger guidance; the delegation sentence only weakly implies when. Per the guideline, missing trigger guidance caps this at 3.	3 / 5
Trigger Term Quality	Terms a user configuring this stack would naturally say are present ("authentication portals", "redirect trust", "refresh", "Documents storage"), with the delegation sentence adding "OIDC". Not 5 because common variations such as "login", "SSO", "OAuth", or the product name are missing.	4 / 5
Distinctiveness Conflict Risk	"Delegates cookies, UI, transforms, crypto, and OIDC provider details to focused skills" carves out a clear niche and explicitly disambiguates from closely related sibling skills. Not 5 because the ecosystem/product is not named and minor overlap remains with the very similar neighboring skills it delegates to.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Criteria	Description	Result
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
Revision: 4372fa7

Reviewed: 7 days ago

Discovery Implementation Validation

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.

configuration-authentication

Table of Contents

Is this your skill?