CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

configuration-saml-providers

Configure external SAML login providers, ACS/IdP URLs, metadata, signing certificates, realms, and claims. Use for Azure or generic IdPs; portal SAML SSO app providers belong to configuration-sso-app.

Quality

86%

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

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

An information-dense, highly actionable reference skill that respects the reader's intelligence and documents genuinely non-obvious behavior (claim suffixes, NameID rules, cookie binding, driver constraints). Its only structural weaknesses are the absence of an explicit configuration workflow sequence and deep detail that could be split into a references file.

DimensionReasoningScore

Conciseness

The body is packed with non-obvious, high-value specifics ("attributes whose names end in `identity/claims/emailaddress`", "Transient NameIDs are rejected", "it does not fetch certificate URLs") and contains no padding or explanation of concepts Claude already knows. Every section earns its tokens.

5 / 5

Actionability

Two complete, copy-paste-ready Caddyfile blocks with exact field names, a runnable resolution command ("go list -m -json github.com/greenpau/go-authcrunch"), named regression tests, and concrete diagnostics ("check clock synchronization ... before changing IdP metadata or certificates").

5 / 5

Workflow Clarity

The Review Checklist supplies explicit verification checkpoints and error-recovery guidance exists, but the configuration flow (choose driver, configure provider fields, enable in portal, map claims/roles) is never laid out as an explicit sequence. Not a 3: checkpoints are present, not merely implied.

4 / 5

Progressive Disclosure

References to fixture files ("caddyfile_identity_provider.go", "pkg/idp/saml") and two cross-skill links are clearly signaled and one level deep, and sections are well organized. However, deep detail such as the attachment-clause syntax and fixture coverage notes is inlined in the single SKILL.md where a references file could carry it.

4 / 5

Total

18

/

20

Passed

Description

78%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.

A strong description with a concrete, multi-object capability list, explicit trigger guidance, and excellent boundary marking against a sibling SSO skill. The main room for improvement is a richer set of distinct action verbs and broader trigger phrasing.

DimensionReasoningScore

Specificity

"Configure external SAML login providers, ACS/IdP URLs, metadata, signing certificates, realms, and claims" lists six concrete configuration objects, but all hang off the single verb "Configure" rather than multiple distinct actions as in the anchor-5 example. It is well above anchor 3's "1-2 concrete actions" coverage.

4 / 5

Completeness

Both parts are explicit: the "what" ("Configure external SAML login providers, ACS/IdP URLs, metadata, signing certificates, realms, and claims") and the "when" ("Use for Azure or generic IdPs"). The when-clause is concrete but narrower than anchor 5, which spells out the user scenarios that should trigger the skill.

4 / 5

Trigger Term Quality

Natural keywords a user would say are present: "SAML", "Azure", "IdP", "login", "SSO", "claims", "certificates". A few natural terms are missing (e.g., "single sign-on", "JumpCloud"), keeping it just below comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

"portal SAML SSO app providers belong to configuration-sso-app" explicitly fences off the nearest sibling skill, giving a clear niche with distinct triggers and minimal conflict risk.

5 / 5

Total

17

/

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

Warning

Total

15

/

16

Passed

Repository

greenpau/caddy-security

Path

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