CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-oauth-providers

Configure external OAuth/OIDC login providers, credentials, scopes, issuer/audience trust, JWKS, PKCE, portal enablement, and named pending-login storage. Named relying-party registrations and portal OPs belong to OAuth applications.

Quality

80%

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-oauth-providers/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 body is an excellent, dense configuration reference: executable examples, exact syntax inventories, per-driver defaults, and a validation checklist, with well-signaled one-level-deep references. Its only weaknesses are mild verbosity in the provider-notes sections and reliance on fixture paths outside the skill bundle.

DimensionReasoningScore

Conciseness

The body is dense and code-backed with no padding or explanation of concepts Claude already knows — every section carries repo-specific constraints (e.g. driver-specific defaults, "authcrunch defaults `domain_name` to `gitlab.com`"). A few sections such as Provider Notes and Provider-Side Claim Notes run long and could be trimmed slightly.

4 / 5

Actionability

Fully executable guidance throughout: copy-paste-ready Caddyfile blocks (the Shape example, shortcut form, id-token-cookie variants), exact accepted field inventories, per-driver scope defaults, and concrete fixture paths ("assets/config/home.Caddyfile", "testdata/caddyfile_adapt/testcase_authenticate_with_oauth.Caddyfile") covering the common cases.

5 / 5

Workflow Clarity

As a configuration-reference skill it is well sequenced (purpose → shape → drivers → options → review checklist → fixtures) and the "Review Checklist" section provides explicit code-backed validation checkpoints for generated entries. There is no multi-step feedback loop, but none is required for non-destructive config authoring.

4 / 5

Progressive Disclosure

The three references (shared-parser.md, shared-login-storage.md, consul-login-storage.md) are real bundle files, one level deep, each linked with a clear purpose statement. Minor gaps: several cited paths (assets/config/home.Caddyfile, testdata fixtures, ../configuration cross-skill links) resolve outside this bundle, and some detailed provider notes sit inline where a reference could carry them.

4 / 5

Total

17

/

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 technically dense with a clear niche and explicit boundary routing, but it lacks any explicit "when to use this" trigger clause. Adding a "Use when..." sentence with natural trigger phrases would materially improve it.

Suggestions

Add an explicit trigger clause, e.g. "Use when configuring oauth identity provider blocks, external OAuth/OIDC login, or social login (Azure, GitHub, Google, etc.) in a Caddyfile."

Include common user-facing synonyms such as "identity provider" or "social login" alongside OAuth/OIDC to broaden natural trigger coverage.

Optionally state the exclusion explicitly ("Not for sso provider or SAML identity provider blocks") to reduce overlap with sibling SSO/SAML skills.

DimensionReasoningScore

Specificity

The description enumerates multiple concrete capabilities — "Configure external OAuth/OIDC login providers, credentials, scopes, issuer/audience trust, JWKS, PKCE, portal enablement, and named pending-login storage" — giving comprehensive, specific coverage of the skill's scope rather than generic actions.

5 / 5

Completeness

The "what" is clearly and concretely stated, but there is no "Use when..." clause or equivalent explicit trigger guidance; the closing sentence "Named relying-party registrations and portal OPs belong to OAuth applications" is boundary routing rather than a usage trigger, which caps completeness at 3.

3 / 5

Trigger Term Quality

Strong natural keywords ("OAuth", "OIDC", "login providers", "credentials", "scopes", "PKCE", "portal") that users would say when needing this skill, but common variations like "identity provider", "social login", or "sign-in" are missing.

4 / 5

Distinctiveness Conflict Risk

The OAuth/OIDC login-provider niche is clear and the routing sentence distinguishes it from sibling skills, but closely adjacent SSO/SAML configuration skills are not explicitly excluded in the description itself, leaving minor overlap risk.

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

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (assets/config/home.Caddyfile), 1 deeper-than-1-level

Warning

Total

14

/

16

Passed

Repository

greenpau/caddy-security

Path

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