competition-windows-pivot — Claude Code skill: installation
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.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a claude-codeWhat competition-windows-pivot does
The skill maps an artifact to its replay route, the host it reaches, and the resulting capability. It distinguishes passwords, hashes, tickets, cookies, vault data, and gMSA material, then follows movement through WinRM, SMB, RDP, WMI, administrative shares, or other Windows mechanisms.
For Kerberos, it records SPNs, delegation, PAC details, and the accepting service. For Active Directory edges, it checks ACLs, GPO links, SIDHistory, and replication rights. The references/windows-pivot.md file contains a pivot checklist and a Kerberos evidence block. This skill runs only after ctf-sandbox-orchestrator has set sandbox assumptions, node ownership, and evidence priorities; otherwise, it sends the task back to the orchestrator.
What it helps with
- trace movement between Windows hosts
- identify which service accepted a Kerberos ticket
- separate recovered credentials from usable privileges
- connect a replayed artifact to its effect on the destination host
Example prompts for the agent
- Trace a recovered Kerberos ticket to the service that accepted it.
- Follow the move from one Windows host to another over WinRM or SMB.
- Show what capability the replayed artifact provided on the destination host.
How to install competition-windows-pivot
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a claude-code2Manually: put the files in place
~/.claude/skills/competition-windows-pivot/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-windows-pivot/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a codex2Manually: put the files in place
.agents/skills/competition-windows-pivot/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a cursor2Manually: put the files in place
.cursor/skills/competition-windows-pivot/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-windows-pivot/SKILL.md2Manually: put the files in place
.github/skills/competition-windows-pivot/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-windows-pivotManually: put the files in place
.devin/skills/competition-windows-pivot/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -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-windows-pivot
How do I install competition-windows-pivot in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot -a claude-code. The skill file is at ~/.claude/skills/competition-windows-pivot/SKILL.md.
What does competition-windows-pivot do?
It traces Windows host-to-host movement involving recovered credentials and replayable tickets. The skill links each artifact to the service that accepted it and the resulting capability.
What does competition-windows-pivot need to run?
ctf-sandbox-orchestrator must first establish sandbox assumptions, node ownership, and evidence priorities. It then routes the task to this skill.
Source text
SKILL.md · MIT
--- name: competition-windows-pivot description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos, WinRM, SMB, RDP, Windows credential material, replayable tickets, delegation edges, and host-to-host pivot chains. Use when the user asks to replay Kerberos material, trace a WinRM, SMB, or RDP pivot, understand host-to-host privilege movement, or prove which Windows service accepted a credential or ticket. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Windows Pivot 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 challenge path is dominated by host-to-host movement, replayable ticket material, or Windows privilege edges. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Compress the pivot into a concrete chain: foothold -> recovered artifact -> replay path -> pivot host -> resulting capability. 2. Separate stored credential material from usable privilege. 3. Keep host evidence, ticket evidence, and privilege effect on one timeline. 4. Record the exact accepting service or host for every replayed artifact. 5. Reproduce the smallest pivot that still proves the privilege edge. ## Workflow ### 1. Recover The Replay Material - Inspect SAM, SECURITY, SYSTEM, NTDS, DPAPI, LSA secrets, browser stores, PowerShell history, ETW, Sysmon, and event logs in the active path. - Distinguish password, hash, ticket, cookie, vault blob, or gMSA material by where it can actually be used. ### 2. Trace The Pivot Chain - Map the protocol actually used: WinRM, SMB, RDP, WMI, admin shares, remote registry, or service control. - When Kerberos matters, record SPN, delegation, PAC or group data, encryption type, and the accepting service. - When AD edges matter, inspect ACLs, GPO links, SIDHistory, delegation, certificate templates, and replication rights. ### 3. Report The Edge - Keep the pivot path concrete and replayable. - State what artifact crossed which boundary and what capability appeared on the destination host. ## Read This Reference - Load `references/windows-pivot.md` for the pivot checklist, Kerberos evidence block, and common replay mistakes. - If the task is specifically about DPAPI masterkeys, browser or vault stores, protected blobs, or proving where a recovered DPAPI secret is accepted, prefer `$competition-dpapi-credential-chain`. - If the task is specifically about LSASS memory, ticket caches, replayable session material, or host-resident credential extraction, prefer `$competition-lsass-ticket-material`. - If the task is specifically about delegation edges, SPN trust, S4U flow, or which service accepts the delegated ticket, prefer `$competition-kerberos-delegation`. - If the hard part is forced authentication, coercion primitives, relay targets, or the service that accepts relayed auth, prefer `$competition-relay-coercion-chain`. ## What To Preserve - Host names, logon IDs, SIDs, SPNs, ticket fields, service names, and event IDs - Exact replay point and resulting logon session, token, or group change - Raw host artifacts and derived timeline separately
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill