configuration-oauth-providers

caddy-security OAuth and OIDC identity provider Caddyfile configuration. Use when creating, reviewing, or modifying oauth identity provider blocks, Azure, GitHub, Google, LinkedIn, Discord, Facebook, Okta, Cognito, GitLab, Nextcloud, or generic OAuth providers, client IDs and secrets, scopes, id token cookies, icons, PKCE toggles, user group filters, JWKS keys, and portal enablement.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

100%Weight 40%Scale 1-3

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 lean, authoritative configuration reference: executable Caddyfile examples, precise per-provider requirements and defaults, and a review checklist for validation. References to source files are clearly signaled and one level deep.

Dimension	Reasoning	Score
Conciseness	The body is dense with code-backed config facts and assumes Claude's knowledge of Caddy/OAuth without explaining basic concepts; it is not verbose enough to warrant the 'could be tightened' level 2 anchor.	3 / 3
Actionability	Provides complete, executable Caddyfile blocks with exact field names, per-provider required fields, default scopes, and accepted toggles, all copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Includes a 'Review Checklist' with explicit code-backed validation constraints and a 'Fixtures' section pointing to verification examples, giving clear checkpoints for generated config.	3 / 3
Progressive Disclosure	Well-organized into clear sections with a 'Fixtures' section that clearly signals one-level-deep references to authoritative source files (e.g. caddyfile_identity_provider.go, go-authcrunch/pkg/idp/oauth/config.go) rather than duplicating them inline.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

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 concise yet specific, naming concrete actions, many natural provider trigger terms, and an explicit 'Use when' clause. It clearly distinguishes its niche and answers both what and when.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("creating, reviewing, or modifying oauth identity provider blocks") plus specific config items (client IDs and secrets, scopes, id token cookies, PKCE toggles, JWKS keys), matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly states what it does ("caddy-security OAuth and OIDC identity provider Caddyfile configuration") and when to use it ("Use when creating, reviewing, or modifying..."), clearly answering both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	Covers natural provider names users would say (Azure, GitHub, Google, LinkedIn, Discord, Facebook, Okta, Cognito, GitLab, Nextcloud) alongside common config terms, giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	A clear niche (caddy-security OAuth/OIDC identity provider Caddyfile config) with named providers and portal enablement, making it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 3 missing, 3 deeper-than-1-level	Warning

	Total	15 / 16 Passed

Repository: greenpau/caddy-security
Path: .codex/skills/configuration-oauth-providers/SKILL.md
Commit: b96087f

Reviewed: 23 days ago

Table of Contents

Discovery Implementation Validation

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.