competition-identity-windows — Claude Code skill: how it works
competition-identity-windows — a skill for Claude Code and Codex that examines Active Directory attacks, Windows host artifacts, and CTF pivot chains. It runs after routing by $ctf-sandbox-orchestrator.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a claude-codeWhat competition-identity-windows does
This skill traces Active Directory identity flows, maps Kerberos ticket minting, inspects OAuth tokens, and examines Windows host evidence. It correlates SAM, LSA secrets, Sysmon events, and mailbox rules into a coherent lateral-movement graph.
The workflow acts as a downstream step for $ctf-sandbox-orchestrator and references references/identity-windows.md. It prompts the model to answer in Simplified Chinese unless an English response is requested.
Without prior assumptions from $ctf-sandbox-orchestrator, execution halts and routes back to the orchestrator because node ownership must be defined first.
What it helps with
- correlate Windows host artifacts and mailbox rules on one timeline
- trace Kerberos ticket minting and group resolution paths
- map lateral movement steps across sandbox nodes
- separate credential possession from accepted privileges
Example prompts for the agent
- Trace the Kerberos ticket path and verify SPNs on the compromised host.
- Construct the lateral-movement graph from initial access through Sysmon and DPAPI.
- Correlate mailbox rules with identity provider logs to reconstruct the privilege chain.
How to install competition-identity-windows
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a claude-code2Manually: put the files in place
~/.claude/skills/competition-identity-windows/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-identity-windows/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a codex2Manually: put the files in place
.agents/skills/competition-identity-windows/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a cursor2Manually: put the files in place
.cursor/skills/competition-identity-windows/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-identity-windows/SKILL.md2Manually: put the files in place
.github/skills/competition-identity-windows/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-identity-windowsManually: put the files in place
.devin/skills/competition-identity-windows/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -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-identity-windows
How to install competition-identity-windows in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-identity-windows -a claude-code. The file will be placed at ~/.claude/skills/competition-identity-windows/SKILL.md.
What does competition-identity-windows do?
It analyzes Active Directory events, Kerberos tickets, mail rules, and Windows host artifacts in CTF sandbox scenarios.
What is required to run competition-identity-windows?
It requires prior context setup by $ctf-sandbox-orchestrator to establish sandbox node ownership and evidence priorities.
Source text
SKILL.md · MIT
--- name: competition-identity-windows description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Active Directory, Kerberos, LDAP, OAuth, enterprise messaging, Windows host forensics, credential material, and lateral-movement challenges. Use when the user asks to trace tickets or tokens, inspect mailbox rules, analyze Windows host evidence, understand an AD trust path, or explain a lateral-movement chain across sandbox-linked nodes. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Identity Windows 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 revolves around identity flow, replayable credentials, Windows host artifacts, enterprise mail, or lateral movement. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Map the identity or pivot chain before diving into every host artifact. 2. Separate credential possession from accepted privilege. 3. Correlate identity evidence, host evidence, and mail evidence on one timeline. 4. Keep tickets, SIDs, event IDs, mailbox rules, and pivot hosts in compact evidence blocks. 5. Reproduce the privilege edge or mail effect from the smallest viable chain. ## Workflow ### 1. Identity And AD - Trace principal origin, sync path, token or ticket minting, claims transformation, group resolution, and accepting service. - When Kerberos matters, record ticket type, SPN, delegation mode, PAC or group data, encryption type, and cache location. ### 2. Windows Host And Pivoting - Correlate SAM, SECURITY, SYSTEM, NTDS, DPAPI, LSA secrets, ETW, Sysmon, PowerShell, services, tasks, WMI, WinRM, SMB, and RDP as one pivot graph. - Express movement as a concrete chain: foothold -> recovered artifact -> replay path -> pivot host -> resulting capability. ### 3. Enterprise Messaging - Keep phishing lures, consent logs, mailbox rules, and identity-provider events tied together so the mail path and privilege path stay connected. ## Read This Reference - Load `references/identity-windows.md` for the ticket, host, and enterprise-messaging checklist. - If the task is primarily a host-to-host pivot, Kerberos replay, or Windows privilege chain, prefer `$competition-windows-pivot`. - If the task is specifically about constrained delegation, unconstrained delegation, RBCD, S4U, or ticket-acceptance proof, prefer `$competition-kerberos-delegation`. - If the task is specifically about AD CS, certificate templates, EKUs, enrollment rights, PKINIT, or cert-based privilege, prefer `$competition-ad-certificate-abuse`. - If the task is specifically about OAuth or OIDC claims, callback flow, scopes, consent, or accepted login identity, prefer `$competition-oauth-oidc-chain`. - If the task is specifically about DPAPI masterkeys, vault blobs, browser or vault secrets, backup-key use, or protected-secret-to-access chains, prefer `$competition-dpapi-credential-chain`. - If the task is specifically about LSASS memory, ticket caches, LUID-linked material, DPAPI context, or replayable host credential artifacts, prefer `$competition-lsass-ticket-material`. - If the task is specifically about mailbox rules, forwarding, OAuth consent, delegate access, or transport-level mail abuse, prefer `$competition-mailbox-abuse`. - If the task is specifically about forced authentication, relay targets, or proving which service accepts relayed auth, prefer `$competition-relay-coercion-chain`. ## What To Preserve - SIDs, SPNs, ticket fields, event IDs, mailbox rules, and replay points - Exact host-to-host pivot order and the service that accepts the credential or ticket - Raw artifacts, parsed summaries, and derived timelines as separate outputs
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill