Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-relay-coercion-chain -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/competition-relay-coercion-chain/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-relay-coercion-chain/

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

Similar skills

All skills for Security →
ntlm-relay-coercion yaklang ntlm-relay-coercion is a skill for capturing and relaying NTLM authentication to SMB, LDAP, HTTP and MSSQL targets, including coercion methods. CX Codex +1 3,900installs nemo-relay-install NVIDIA Corporation and Affiliates The nemo-relay-install skill identifies your installation target and deploys the current stable NeMo Relay package, resolving prerequisites and verifying availability. Works across agent runtimes, frameworks, and language bindings. CX Codex +1 227installs openclaw-relay steipete openclaw-relay is a Claude Code skill that routes prompts and messages to OpenClaw sessions via local acpx or SSH, resolving targets from named aliases in config/session_aliases.json. CX Codex +1 120installs competition-zip-archive freyrswift competition-zip-archive is a Claude Code skill that recovers legacy ZipCrypto keys from archives using known-plaintext attacks. CTF workflows trigger it after ctf-sandbox-orchestrator runs. CX Codex +1 ★ 71repo stars linux-pentesting-command-reference reason-machines linux-pentesting-command-reference — a skill that feeds the agent a Linux command cheat sheet for recon, service enumeration, privilege escalation and staying on the box. Handy in labs and CTFs where a one-liner beats theory. CX Codex +1 290installs windows-privilege-escalation yaklang windows-privilege-escalation — a skill for Claude Code and other AI coders that turns low-privilege shell access on Windows into admin-level control via token abuse, service misconfiguration, and UAC bypass. CX Codex +1 3,900installs

From the same set36

The whole set →
competition-oauth-oidc-chain 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. CX Codex +1 109installs competition-file-parser-chain The competition-file-parser-chain Claude Code skill follows a file from upload to a parser or deserializer. It runs after ctf-sandbox-orchestrator routes a file-processing investigation to it. CX Codex +1 109installs competition-firmware-layout competition-firmware-layout — a skill for Claude Code, Codex, Cursor and other platforms that maps firmware images, partition tables, and boot chains. CX Codex +1 109installs competition-windows-pivot The competition-windows-pivot Claude Code skill traces host-to-host movement in Windows CTF scenarios. It connects recovered credentials or tickets to the service that accepted them. CX Codex +1 109installs competition-kerberos-delegation competition-kerberos-delegation — a skill for Claude Code that automates Kerberos delegation analysis in CTF scenarios. It runs after context setup via $ctf-sandbox-orchestrator to verify exploitation paths. CX Codex +1 109installs competition-mailbox-abuse competition-mailbox-abuse — a skill for Claude Code and other environments specializing in analyzing enterprise mail abuse within CTF sandboxes. CX Codex +1 109installs competition-prompt-injection The competition-prompt-injection Claude Code skill examines CTF challenges involving trust boundaries in agent systems. It traces how untrusted content can alter planner behavior, tool arguments, or expose secrets. CX Codex +1 109installs competition-malware-config competition-malware-config — a skill for Claude Code and other platforms recovers malware configurations, decodes C2 beacon parameters, and extracts IOCs. CX Codex +1 109installs

Project sponsors

Companies that keep this analytics open