competition-relay-coercion-chain

1# Competition Relay Coercion Chain
2 
3Use 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.
4 
5Use this skill when the hard part is proving the full chain from forced authentication to a service that actually accepts the relayed identity.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Split the chain into coercion source, captured auth, relay target, acceptance point, and resulting effect.
122. Record transport, protocol, and service identity at each hop.
133. Separate forced-auth generation from relay success and from downstream privilege.
144. Keep coercion trigger, relay transcript, and accepting service in one evidence chain.
155. Reproduce the smallest coercion-to-acceptance path that proves the decisive edge.
16 
17## Workflow
18 
19### 1. Map The Coercion Source
20 
21- Identify the service, RPC, file path, printer path, WebDAV edge, or protocol trigger that forces authentication.
22- Record source host, coerced principal, transport, and any environmental preconditions.
23- Keep one compact note of exactly what causes the auth to leave the source.
24 
25### 2. Trace The Relay Target
26 
27- Record where the authentication lands, how it is forwarded, and which protocol or service consumes it.
28- Distinguish capture-only, replay-only, and actual relay acceptance.
29…