CtrlK
BlogDocsLog inGet started
Tessl Logo

competition-oauth-oidc-chain

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for OAuth, OIDC, redirect flows, state or nonce handling, PKCE, token exchange, refresh logic, claim mapping, and accepted login paths. Use when the user asks to trace redirects, callback parameters, scopes, state, nonce, PKCE, refresh tokens, consent, or explain how an OAuth or OIDC chain turns into accepted identity or privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

80

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

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 body is a tight, well-organized analytical workflow that assumes Claude's competence and delegates detail to a single real one-level reference. Sequencing and the decisive-edge validation checkpoint are explicit.

DimensionReasoningScore

Conciseness

Lean body with no concept-explaining fluff; assumes Claude knows OAuth/OIDC ("Record scopes, state, nonce, PKCE material") rather than explaining what they are, matching the lean-and-efficient anchor.

3 / 3

Actionability

Concrete, specific analytical guidance ("Compress the result to the smallest sequence: entry request -> redirect -> callback -> token or claim acceptance -> resulting capability"); per scoring_notes, an instruction-only analytical skill is not penalized for lacking executable code when guidance is this actionable.

3 / 3

Workflow Clarity

Clearly sequenced Map -> Prove -> Reduce workflow with a decisive-edge proof checkpoint ("Reproduce the smallest redirect-to-acceptance flow that proves the decisive identity edge"); the feedback-loop cap for destructive/batch ops does not apply to this non-destructive analytical task.

3 / 3

Progressive Disclosure

Concise overview body with a single clearly-signaled one-level-deep reference ("Load `references/oauth-oidc-chain.md`"), verified to exist as a real bundle file, matching the clear-overview anchor.

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, specific, and well-gated, with concrete capability verbs and a strong natural-trigger 'Use when' clause. It clearly distinguishes itself from sibling skills via explicit downstream routing.

DimensionReasoningScore

Specificity

Lists many concrete actions ("trace redirects, callback parameters, scopes, state, nonce, PKCE, token exchange, refresh logic, claim mapping"), matching the multiple-specific-actions anchor rather than the named-domain-but-incomplete anchor at 2.

3 / 3

Completeness

Explicitly answers both what ("CTF-sandbox workflow for OAuth, OIDC...") and when ("Use when the user asks to trace redirects..."); the explicit 'Use when' clause exceeds the 2-cap for missing triggers.

3 / 3

Trigger Term Quality

Covers natural user-facing terms ("redirects, callback parameters, scopes, state, nonce, PKCE, refresh tokens, consent") matching the good-coverage anchor; not merely technical jargon as at 1.

3 / 3

Distinctiveness Conflict Risk

Clear niche (OAuth/OIDC chains) with distinct triggers and explicit gating ("Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions"), making wrong-skill triggering unlikely.

3 / 3

Total

12

/

12

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
zhaoxuya520/reverse-skill
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.