CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-identity-stores

Configure local, LDAP or SQLite password identity stores, trusted SQLite administration, realms, databases, binds, TLS trust and group mappings. Delegates static local entries to configuration-users.

Quality

81%

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.

The body is an exceptionally well-executed configuration skill: executable examples, exact directive aliases and defaults, explicit failure modes, and a verification checklist tied to named test fixtures. Structure and reference splitting are exemplary; the only real room for improvement is trimming reference-level detail (runtime flow, E2E commentary) out of the main file.

DimensionReasoningScore

Conciseness

The body is dense with repo-specific facts (Caddyfile-to-authcrunch aliases, defaults, bootstrap env vars, policy limits) and never explains concepts Claude already knows, but the runtime LDAP authentication flow and E2E test commentary are detail that could be trimmed or pushed to a reference file.

4 / 5

Actionability

Complete, copy-paste-ready Caddyfile blocks for a local store, the local shortcut, a full LDAP store with realistic values, and portal wiring, plus exact option/alias lists, environment variable names, and an openssl command for collecting trust chains cover the common cases fully.

5 / 5

Workflow Clarity

The define-store-then-wire-portal sequence is clear and validation is strong ("verify exactly-one-user selection, explicit and automatic mapping, unmapped-user rejection or fallback, wrong-password rejection and trust failures against a disposable directory before claiming login compatibility"), but validation is distributed rather than a structured end-to-end sequence with reload/feedback loops.

4 / 5

Progressive Disclosure

The SKILL.md is an overview with three topical one-level-deep references (local-identity.md, sqlite-integration.md, connected-accounts.md — all present in the bundle), each clearly signaled at the point of relevance with a stated scope, and cross-links delegate to the skills that own those contracts.

5 / 5

Total

18

/

20

Passed

Description

71%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 comprehensive about capabilities with strong third-person, jargon-accurate trigger terms for the Caddy identity-store niche. Its main weakness is the complete absence of an explicit "Use when..." trigger clause, which caps completeness at 3 despite otherwise strong content.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring local, LDAP, or SQLite identity stores in Caddyfile security blocks, or when the user mentions realms, bind credentials, LDAPS trust, or LDAP group mappings."

Include natural synonyms users might say such as "authentication backend", "login", or "directory" to broaden trigger matching.

Keep the delegation sentence to configuration-users — it is the strongest distinctiveness signal — and mirror it with a one-line scope boundary for the authentication portal skill.

DimensionReasoningScore

Specificity

"Configure local, LDAP or SQLite password identity stores, trusted SQLite administration, realms, databases, binds, TLS trust and group mappings" lists multiple specific concrete actions that comprehensively cover the skill's domain, matching the body's actual scope; it uses third-person voice with no generic filler.

5 / 5

Completeness

The description clearly answers "what" (configure local/LDAP/SQLite identity stores with realms, binds, TLS trust, group mappings) but contains no "Use when..." clause or equivalent explicit trigger guidance, capping completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Natural domain phrasings like "identity stores", "LDAP", "SQLite", "binds", "TLS trust", and "group mappings" are present and would be said by a user configuring these stores, but common synonyms such as "authentication", "login", or "directory" are missing.

4 / 5

Distinctiveness Conflict Risk

"Delegates static local entries to configuration-users" is an explicit boundary that reduces conflict with the sibling skill, but password/realm/user-account territory still creates minor overlap risk with closely related 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: 2 suspicious

Warning

referenced_paths_exist

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

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

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