competition-relay-coercion-chain — Claude Code skill: install
The competition-relay-coercion-chain Claude Code skill traces forced-authentication and relay chains in a CTF sandbox. It runs when an analysis needs to identify the service accepting relayed credentials and the resulting effect.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a claude-codeWhat competition-relay-coercion-chain does
The skill breaks a chain into its authentication trigger, captured credentials, relay destination, accepting service, and outcome. It separates credential capture from replay and actual relay acceptance, then connects the accepted identity to a privilege change or artifact.
Each hop is tracked by transport, protocol, and service identity. The evidence chain ties together the trigger, relay transcript, and response from the accepting service. A checklist and evidence-packaging notes are in references/relay-coercion-chain.md. This skill runs only after ctf-sandbox-orchestrator has set sandbox assumptions, node ownership, and evidence priorities.
What it helps with
- identify which service accepts relayed authentication
- separate forced authentication from successful relay acceptance
- trace an accepted identity to a privilege change or artifact
- reduce the evidence to the smallest coercion-to-acceptance chain
Example prompts for the agent
- Trace the path from forced authentication to the service that accepts the relayed identity.
- Separate credential capture from successful relay acceptance in this chain.
- Connect the authentication trigger to the resulting privilege and organize the evidence.
How to install competition-relay-coercion-chain
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a claude-code2Manually: put the files in place
~/.claude/skills/competition-relay-coercion-chain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-relay-coercion-chain/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a codex2Manually: put the files in place
.agents/skills/competition-relay-coercion-chain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a cursor2Manually: put the files in place
.cursor/skills/competition-relay-coercion-chain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-relay-coercion-chain/SKILL.md2Manually: put the files in place
.github/skills/competition-relay-coercion-chain/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-relay-coercion-chainManually: put the files in place
.devin/skills/competition-relay-coercion-chain/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-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-relay-coercion-chain
How do I install competition-relay-coercion-chain in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a claude-code. The skill file is at ~/.claude/skills/competition-relay-coercion-chain/SKILL.md.
What does competition-relay-coercion-chain do?
It traces forced authentication through a relay to the service that accepts the credentials, then records the resulting privilege or artifact.
What does competition-relay-coercion-chain require?
ctf-sandbox-orchestrator must first establish the sandbox assumptions, node ownership, and evidence priorities. This skill is routed in afterward.
Source text
SKILL.md · MIT
--- name: competition-relay-coercion-chain description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for forced-auth coercion, relay chains, target selection, NTLM or related acceptance paths, and coercion-to-privilege transitions. Use when the user asks to trace a coercion primitive, follow a relay path, analyze forced authentication, determine which service accepts relayed auth, or connect a coercion step to resulting privilege, enrollment, or code execution. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Relay Coercion 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 the full chain from forced authentication to a service that actually accepts the relayed identity. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect. 2. Record transport, protocol, and service identity at each hop. 3. Separate forced-auth generation from relay success and from downstream privilege. 4. Keep coercion trigger, relay transcript, and accepting service in one evidence chain. 5. Reproduce the smallest coercion-to-acceptance path that proves the decisive edge. ## Workflow ### 1. Map The Coercion Source - Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication. - Record source host, coerced principal, transport, and any environmental preconditions. - Keep one compact note of exactly what causes the auth to leave the source. ### 2. Trace The Relay Target - Record where the authentication lands, how it is forwarded, and which protocol or service consumes it. - Distinguish capture-only, replay-only, and actual relay acceptance. - Keep service name, target host, protocol, relay transcript, and acceptance response tied together. ### 3. Reduce To The Decisive Relay Chain - Compress the result to the smallest sequence: coercion trigger -> relayed auth -> accepted service -> resulting privilege or artifact. - State clearly whether the decisive weakness lives in the coercion source, the relay target, signing settings, or the accepted downstream service. - If the path ultimately becomes a certificate-enrollment issue or a pure Kerberos delegation edge, hand off to the tighter specialized skill. ## Read This Reference - Load `references/relay-coercion-chain.md` for the coercion checklist, relay checklist, and evidence packaging. ## What To Preserve - Coercion trigger details, source host, coerced identity, target host, accepting service, and resulting effect - Relay transcripts, error or acceptance responses, and the exact protocol used at each hop - The smallest replayable coercion-to-acceptance sequence
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill