CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-registrations

Configure legacy signup and SQLite email-confirmed enrollment, portal selection, messaging, storage and recovery. OAuth client registration is separate.

Quality

75%

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

The content is a well-organized, information-dense configuration reference: every token carries non-obvious domain knowledge, the Caddyfile example is directly usable, and edge-case behavior is documented precisely. The main gaps are the absence of a sequenced step-by-step configuration procedure and a body long enough that some legacy-flow detail could move to reference files.

DimensionReasoningScore

Conciseness

The body is dense with non-obvious domain facts (parser injection of `kind local`, admin-email lines overwriting rather than appending, in-memory pending registrations discarded on reload, plaintext password requirement) with no padding or explanation of concepts Claude already knows. It is not 5 because the Fixtures paragraph and parts of Workflow Notes run long and could be tightened.

4 / 5

Actionability

A complete copy-paste Caddyfile block, an enumerated list of supported line patterns, concrete domain-rule matching semantics, and a specific local-validation recipe (file messaging provider with disposable `tmp/` root, inspect `.eml` output) provide mostly executable guidance. It is not 5 because a full working example requires coordinating with sibling skills for messaging and identity-store configuration that are not shown inline.

4 / 5

Workflow Clarity

The registration journey is coherently sequenced (form submission, time-limited confirmation passcode, dropbox commit, administrator notification, separate management activation) with explicit failure-mode handling (expired passcodes, notification failure after commit). It is not 5 because the setup guidance is organized by topic rather than as an ordered procedure with numbered steps.

4 / 5

Progressive Disclosure

The single bundle file `references/sqlite-workflows.md` is clearly signaled in the Purpose section with what it covers, and it is one level deep (its outbound links target sibling skills, not nested content in this bundle). It is not 5 because at 167 lines the body carries substantial legacy-flow detail that could be split out, and only the SQLite flow has a dedicated reference file.

4 / 5

Total

16

/

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 clearly states what the skill configures and carves out a distinct niche with an explicit OAuth boundary, but it omits any 'when to use' trigger guidance, which caps its completeness. Trigger terms are good though missing common synonyms, and the single generic verb 'Configure' leaves the specificity of each area underspecified.

Suggestions

Add an explicit trigger clause, e.g. 'Use when setting up user signup or registration flows in Caddyfile configuration, or when the user mentions enrollment, signup forms, or registration portals.'

Include natural synonyms such as 'account creation', 'user onboarding', or 'sign up' so the description matches how users actually phrase the request.

Briefly specify what 'messaging, storage and recovery' configuration entails (e.g. 'wire email providers, dropbox storage paths, and pending-registration recovery') to sharpen the generic 'Configure' verb.

DimensionReasoningScore

Specificity

"Configure legacy signup and SQLite email-confirmed enrollment, portal selection, messaging, storage and recovery" names the domain plus several concrete configuration areas, matching the 'several specific actions; minor gaps' anchor. It is not 5 because a single generic verb ('Configure') covers all areas and 'recovery' is unspecified, and not 3 because more than 1-2 concrete capabilities are listed.

4 / 5

Completeness

The 'what' is clear (configure legacy signup, SQLite enrollment, portal selection, messaging, storage, recovery), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guidelines. The closing sentence "OAuth client registration is separate" is a boundary note, not a trigger.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "signup", "enrollment", "registration", "portal", "messaging", matching good keyword coverage with a few natural terms missing. It falls short of 5 because common synonyms like "account creation", "onboarding", or "sign up" are absent and "SQLite email-confirmed enrollment" is technical jargon.

4 / 5

Distinctiveness Conflict Risk

Explicit disambiguation ("OAuth client registration is separate") plus niche terms like "legacy signup" and "SQLite email-confirmed enrollment" establish a mostly distinct trigger profile with only minor overlap risk. It is not 5 because the broad tail terms "messaging, storage and recovery" overlap with sibling configuration skills.

4 / 5

Total

15

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 possibly missing (assets/config/registrations_local.json, assets/config/users.json), 2 deeper-than-1-level

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

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