Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →ancoleman/securing-authentication
Authentication, authorization, and API security implementation.
Passed 20 of 22 test cases with the skill, and 11 of 22 without it.
and 7 more in the full report
9 fixed11 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We are building an OIDC client application that needs to perform dynamic discovery of an Identity Provider's endpoints and features. What exact standard URL path specified in RFC 8414 must be queried, and which specific JSON key in the response contains the authorization endpoint URL?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the URL path `/.well-known/openid-configuration`. | Missed | Passed |
| Identifies `authorization_endpoint` as the JSON response key for the authorization endpoint. | Passed | Passed |
The instructions your model reads when the skill loads.
Implement modern authentication, authorization, and API security across Python, Rust, Go, and TypeScript.
Use this skill when:
┌─────────────────────────────────────────────────────────────┐
│ OAuth 2.1 MANDATORY REQUIREMENTS │
│ (RFC 9798 - 2025) │
├─────────────────────────────────────────────────────────────┤
│ │
│ ✅ REQUIRED (Breaking Changes from OAuth 2.0) │
│ ├─ PKCE (Proof Key for Code Exchange) MANDATORY │
│ │ └─ S256 method (SHA-256), minimum entropy 43 chars │
│ ├─ Exact redirect URI matching │
│ │ └─ No wildcard matching, no substring matching │
│ ├─ Authorization code flow ONLY for public clients │
│ │ └─ All other flows require confidential client │
│ └─ TLS 1.2+ required for all endpoints │
│ │
│ ❌ REMOVED (No Longer Supported) │
│ ├─ Implicit grant (security vulnerabilities) │
│ ├─ Resource Owner Password Credentials grant │
│ │ └─ Use OAuth 2.0 Device Flow (RFC 8628) instead │
│ └─ Bearer token in query parameters │
│ └─ Must use Authorization header or POST body │
│ │
└─────────────────────────────────────────────────────────────┘
test cases passed, vs 11 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.