CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-ticket-providers

Configure SQLite or Consul single-use ticket login issued by a trusted application, browser binding, storage and recovery. OAuth/SAML providers have separate owners.

Quality

74%

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-ticket-providers/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 dense, expert-level specification with an executable example, explicit constraints and defaults, and genuine validation/acceptance criteria including error-recovery guidance. It stays uniformly strong across dimensions but stops short of excellent due to prose-heavy sequencing, command-less diagnostics recovery, and inline detail that could live in reference files.

Suggestions

Present the deployment procedure as an explicitly ordered list (declare provider → enable in portal → attach local store → wire policy → run acceptance tests) so the sequence does not have to be inferred from prose.

Move the root-lifecycle and test-inventory detail (descriptor derivation, borrowed-instance rules, the full test-name listing) into a reference file, keeping SKILL.md as a leaner overview.

Give the storage-failure recovery path a concrete diagnostic step (e.g. a command or check to run when a commit is uncertain) instead of direction-only prose.

DimensionReasoningScore

Conciseness

The body is dense constraint prose with essentially no padding or explanation of concepts Claude already knows, and the example avoids hand-holding. Minor trimmable instances remain (the log-filter block appears verbatim twice, connected-accounts.md is cited twice, and several run-on rule sentences could be restructured), keeping it below the lean-everywhere anchor 5.

4 / 5

Actionability

A complete, copy-paste-ready Caddyfile with concrete values, explicit field defaults and limits ("timeout to 1s within 1ms–30s", "base_path defaults to /auth"), and actionable directives ("Add `attach to local identity store <name>` once") make the guidance mostly executable. The diagnostics/recovery section ("Drain and reopen quarantined handles, reconcile the outcome") gives direction without commands, leaving minor gaps versus anchor 5.

4 / 5

Workflow Clarity

The declare → select-in-portal → attach-store → validate flow is discernible, and validation is strong: the Acceptance section names concrete tests and E2E requirements ("TestCaddySQLiteTicketE2E must qualify actual TLS Caddy...") and there is an explicit error-recovery loop ("Do not retry blindly or restore consumed cookies as recovery"). Steps are never explicitly sequenced as an ordered procedure, so it falls short of anchor 5.

4 / 5

Progressive Disclosure

Section headers are clear, and the one-level-deep reference references/trusted-issuer.md exists and is signaled with its purpose ("Read [trusted application integration]... when implementing the application's public Go API consumer"). However, substantial internal-behavior detail (root lifecycle, descriptor derivation, test inventory) is inlined in a 234-line SKILL.md rather than split out, and two cross-bundle references (consul-companions.md, connected-accounts.md) could not be verified in this bundle, which are minor organization gaps versus anchor 5.

4 / 5

Total

16

/

20

Passed

Description

62%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 identifies a distinct, well-bounded niche with several concrete capability areas and an explicit boundary against OAuth/SAML. Its main weaknesses are the absent "Use when..." trigger clause and limited natural-language trigger vocabulary, which leave a user unsure when to invoke it.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring single-use ticket login for a trusted application, or when the user mentions ticket identity providers, browser-binding cookies, or ticket storage/recovery."

Include natural synonyms and plain-language phrasings users would actually say (e.g. "one-time login tickets", "trusted app login") alongside the technical terms.

Make "storage and recovery" concrete by naming the actual actions (e.g. "configure ticket database paths and file permissions, recover pending tickets across restarts").

DimensionReasoningScore

Specificity

Phrases like "Configure SQLite or Consul single-use ticket login issued by a trusted application, browser binding, storage and recovery" name several concrete capability areas (ticket login issuance, browser binding, storage, recovery), but "storage and recovery" stays generic, so coverage has minor gaps rather than being comprehensive.

4 / 5

Completeness

The "what" is clear (configure single-use ticket login with browser binding, storage and recovery), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 2 because the "what" is concrete, not vague.

3 / 5

Trigger Term Quality

Domain keywords such as "SQLite", "Consul", "single-use ticket", "login", and "OAuth/SAML" are present and would be said by users in this niche, but the description offers no natural variations, synonyms, or plain-language trigger phrases. It is above anchor 2 (which requires only generic keywords) but below anchor 4's good coverage with natural terms.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche (SQLite/Consul single-use ticket identity providers) and explicitly disambiguates adjacent territory with "OAuth/SAML providers have separate owners", giving minimal conflict risk with other skills.

5 / 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

relative_links

Relative link issues: 3 suspicious

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

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