CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-identity-stores

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

Quality

78%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.codex/skills/configuration-identity-stores/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

82%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 content is a strong configuration skill: fully executable Caddyfile examples for every store type, explicit Caddyfile-to-authcrunch alias warnings, and named test fixtures with a verification checklist for risky LDAP changes. Minor room remains in tightening runtime-behavior narration and keeping reference chains strictly one level deep.

DimensionReasoningScore

Conciseness

The body is dense with project-specific detail (parser aliases, bootstrap env vars, test names) and explains no generic concepts, matching the efficient anchor with minor trimmable passages. It is not 5 because sections like the LDAP runtime flow ("Connections are closed after each operation; identification and password verification do not share a long-lived connection") and the attachment runtime paragraph narrate internal behavior that could be tightened.

4 / 5

Actionability

Complete, copy-paste-ready Caddyfile blocks cover the common cases: full local store, local shortcut, inline user, a full LDAP store with filters/attributes/groups, and portal wiring, plus named env vars (AUTHP_ADMIN_USER/EMAIL/SECRET) and a concrete `openssl s_client -showcerts` trust-collection procedure. This matches the fully executable, copy-paste-ready anchor.

5 / 5

Workflow Clarity

The define-store-then-wire-portal sequence is present ("After defining a store, enable it from an authentication portal") with validation checkpoints via named fixture tests and an explicit pre-claim verification checklist ("verify exactly-one-user selection, explicit and automatic mapping, unmapped-user rejection or fallback, wrong-password rejection and trust failures"). It is not 5 because the overall sequence is implicit across store-type sections rather than stated as steps, and no explicit test invocation command is given.

4 / 5

Progressive Disclosure

The body is a clear overview with three real, one-level reference files (references/local-identity.md, references/sqlite-integration.md, references/connected-accounts.md), each introduced with a purpose sentence stating what it covers, and cross-skill links are explicit. It is not 5 because reference files chain onward into other skills' references (e.g. connected-accounts.md links to ../../authentication-portal-api/references/connected-accounts.md), a 2-level hop, and some runtime detail is inlined that could be delegated.

4 / 5

Total

17

/

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 distinctive, naming four store types and concrete configuration areas (realms, binds, TLS trust, group mappings) with an explicit delegation boundary. Its main weakness is the absence of any "Use when..." trigger guidance, which caps completeness and limits natural trigger coverage.

Suggestions

Add an explicit trigger clause such as "Use when configuring `local identity store` or `ldap identity store` blocks in a Caddyfile" so the 'when' is stated, not implied.

Include a few more natural trigger terms users would say, e.g. "users.json", "authentication portal", or "identity store wiring", to broaden keyword coverage.

Mention portal wiring ("enable identity store" in an authentication portal) to round out the capability list beyond store definition.

DimensionReasoningScore

Specificity

"Configure local, LDAP, SQLite or Consul password identity stores, trusted SQLite administration, realms, databases, binds, TLS trust and group mappings" names several concrete configuration targets across four store types, matching the anchor for several specific actions with minor gaps. It is not 5 because a single verb ("Configure") covers the list and capabilities like portal wiring and recovery options are unmentioned, and not 3 because coverage well exceeds 1-2 actions.

4 / 5

Completeness

The "what" is clear (configure identity stores with realms, binds, TLS trust, group mappings), but there is no "Use when..." clause or equivalent explicit trigger guidance; "Delegates static local entries to configuration-users" states a boundary, not when to use the skill. Per the judging guidelines this caps completeness at 3.

3 / 5

Trigger Term Quality

Natural domain terms are present ("identity store", "LDAP", "SQLite", "Consul", "binds", "TLS trust", "group mappings") that a user configuring this plugin would say, matching good coverage with a few natural terms missing. It falls short of 5 because common variations like "users.json", "authentication portal", or "directory" are absent.

4 / 5

Distinctiveness Conflict Risk

"local, LDAP, SQLite or Consul password identity stores" carves a specific niche with mostly distinct triggers, and the delegation sentence reduces overlap with the closely related configuration-users skill. It is not 5 because "local... identity stores" and "password" still carry minor overlap risk with that sibling skill.

4 / 5

Total

15

/

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

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (assets/config/users.json), 1 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.