competition-oauth-oidc-chain — Claude Code skill: what it does
competition-oauth-oidc-chain is a Claude Code skill for mapping OAuth/OIDC chains, redirects, and token exchanges after the CTF sandbox orchestrator establishes base assumptions.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a claude-codeWhat competition-oauth-oidc-chain does
The skill traces authentication chains step by step from entry routes and redirect parameters to token exchange and final service acceptance. The agent records parameters like state, nonce, PKCE, and scopes while distinguishing token possession from actual identity acceptance. It requires the orchestrator ctf-sandbox-orchestrator to be active beforehand.
The workflow compresses results into a minimal redirect-to-acceptance sequence and tracks token claims against app sessions. Reference checklists reside in references/oauth-oidc-chain.md. Responses default to Simplified Chinese unless English is requested.
Instructions and verification steps isolate the decisive identity edge in competition environments.
What it helps with
- map OAuth and OIDC redirect and token paths
- record state, nonce, and PKCE material
- prove token-to-identity acceptance
- reduce flow to a minimal replayable sequence
Example prompts for the agent
- Trace the OAuth and OIDC redirect chain for this entry route
- Record scopes, state, and PKCE verifier before mutating parameters
- Compress the redirect-to-acceptance flow into a minimal sequence
How to install competition-oauth-oidc-chain
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a claude-code2Manually: put the files in place
~/.claude/skills/competition-oauth-oidc-chain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-oauth-oidc-chain/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a codex2Manually: put the files in place
.agents/skills/competition-oauth-oidc-chain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a cursor2Manually: put the files in place
.cursor/skills/competition-oauth-oidc-chain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-oauth-oidc-chain/SKILL.md2Manually: put the files in place
.github/skills/competition-oauth-oidc-chain/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-oauth-oidc-chainManually: put the files in place
.devin/skills/competition-oauth-oidc-chain/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-oauth-oidc-chain
How to install competition-oauth-oidc-chain in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-oauth-oidc-chain -a claude-code, then reference ~/.claude/skills/competition-oauth-oidc-chain/SKILL.md.
What does competition-oauth-oidc-chain do?
It structures and analyzes OAuth and OIDC workflows, redirect flows, token exchange, and claim mapping inside CTF environments.
What is required to run competition-oauth-oidc-chain?
The orchestrator ctf-sandbox-orchestrator must be active and have established sandbox assumptions before invoking this skill.
Source text
SKILL.md · MIT
--- name: competition-oauth-oidc-chain description: 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. --- # Competition OAuth OIDC Chain Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the hard part is proving how an OAuth or OIDC flow is shaped, exchanged, and ultimately accepted. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Map the auth chain in order: entry route, redirect, authorize request, callback, token exchange, refresh, and final accepting service. 2. Record scopes, state, nonce, PKCE material, redirect URIs, and claim-bearing tokens before mutating anything. 3. Separate token possession from actual identity acceptance. 4. Keep browser-visible redirects and backend-visible token exchange in one compact chain. 5. Reproduce the smallest redirect-to-acceptance flow that proves the decisive identity edge. ## Workflow ### 1. Map The Redirect And Token Path - Record issuer, client ID, redirect URI, authorize parameters, callback parameters, token endpoint, and refresh path. - Note which values are user-controlled, derived, cached, or validated: `state`, `nonce`, PKCE verifier, audience, scope, or prompt. - Keep browser redirects, server-side exchanges, and resulting session state tied together. ### 2. Prove Token-To-Identity Acceptance - Show how code, ID token, access token, or refresh token turns into app session, claims mapping, tenant selection, or accepted privilege. - Record token claims, expiration, audience, subject, scopes, and the exact accepting app or backend edge. - Distinguish UI login success from backend authorization success. ### 3. Reduce To The Decisive OAuth Chain - Compress the result to the smallest sequence: entry request -> redirect -> callback -> token or claim acceptance -> resulting capability. - Keep one canonical good flow and one minimal mutated flow if a parameter change matters. - If the task broadens into generic web routing or storage behavior outside the auth chain, switch back to the broader web-runtime skill. ## Read This Reference - Load `references/oauth-oidc-chain.md` for the redirect checklist, token checklist, and evidence packaging. - If the hard part is JWT header parsing, claim normalization, key lookup, or token validation confusion after issuance, prefer `$competition-jwt-claim-confusion`. ## What To Preserve - Redirect URIs, parameters, codes, token claims, scopes, and the accepting service or callback - The exact point where claims or tokens become accepted app identity - One minimal replayable redirect-to-acceptance sequence
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill