competition-kerberos-delegation — Claude Code skill: what it does
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.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a claude-codeWhat competition-kerberos-delegation does
This skill specializes in analyzing Kerberos delegation within CTF sandboxes. It traces chains from the principal to the target SPN, verifies ticket types, and confirms which service accepts the request. The tool operates only as a downstream extension to $ctf-sandbox-orchestrator, which must be active beforehand to establish sandbox assumptions and node ownership.
The skill includes logic for verifying S4U, RBCD, and constrained delegation paths. Users must load references/kerberos-delegation.md for checklists and common proof mistakes. It compresses complex chains into reproducible paths, isolating specific steps that result in privilege escalation.
What it helps with
- verify a Kerberos delegation path
- confirm service-side ticket acceptance
- distinguish constrained delegation from RBCD
- reproduce a minimal exploitation chain
Example prompts for the agent
- Analyze the delegation path for SPN
cifs/dc01.corp.local - Confirm this ticket is accepted by the service and grants privilege
How to install competition-kerberos-delegation
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a claude-code2Manually: put the files in place
~/.claude/skills/competition-kerberos-delegation/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-kerberos-delegation/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a codex2Manually: put the files in place
.agents/skills/competition-kerberos-delegation/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a cursor2Manually: put the files in place
.cursor/skills/competition-kerberos-delegation/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-kerberos-delegation/SKILL.md2Manually: put the files in place
.github/skills/competition-kerberos-delegation/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-kerberos-delegationManually: put the files in place
.devin/skills/competition-kerberos-delegation/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -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-kerberos-delegation
How to install competition-kerberos-delegation in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-kerberos-delegation -a claude-code. Then access the file at ~/.claude/skills/competition-kerberos-delegation/SKILL.md.
What does this skill do?
It automates the analysis of Kerberos delegation chains, including S4U and RBCD, within CTF sandboxes.
What is required to run it?
An active $ctf-sandbox-orchestrator instance and the references/kerberos-delegation.md file for reference data.
Source text
SKILL.md · MIT
--- name: competition-kerberos-delegation description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Kerberos delegation, SPN trust edges, S4U abuse, RBCD, constrained or unconstrained delegation, and service-ticket acceptance. Use when the user asks about constrained delegation, unconstrained delegation, RBCD, S4U, SPNs, ticket acceptance, or how a Kerberos trust edge turns into effective privilege under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Kerberos Delegation 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 not "is there Kerberos here," but which delegation edge exists, which ticket is being minted, and which service really accepts it. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Write the trust chain first: principal -> delegation edge -> ticket type -> target SPN -> accepting service -> resulting privilege. 2. Separate ticket possession from accepted privilege. 3. Keep SPNs, delegation mode, PAC/group data, encryption type, and service acceptance in one compact evidence block. 4. Reproduce one minimal delegation chain before broadening into variants. 5. Tie every privilege claim to a specific accepted ticket or service-side effect. ## Workflow ### 1. Identify The Delegation Edge - Determine whether the path is constrained delegation, unconstrained delegation, resource-based constrained delegation, protocol transition, or another trust edge. - Inspect SPNs, ACLs, service accounts, SIDHistory, certificate templates, and replication rights only when they affect the active path. ### 2. Trace Ticket Minting And Acceptance - Record TGT/TGS type, S4U steps when relevant, delegation flags, PAC or group data, encryption type, cache location, and target SPN. - Prove which service actually accepts the ticket and what capability appears after acceptance. ### 3. Report The Effective Edge - Compress the chain into one replayable path, not a vague "domain compromise" statement. - Separate candidate edges from the edge that really lands privilege. ## Read This Reference - Load `references/kerberos-delegation.md` for the delegation checklist, ticket fields to preserve, and common proof mistakes. ## What To Preserve - SPN, ticket type, delegation mode, PAC/group data, encryption type, cache location, accepting service - Service-side logs, event IDs, logon session changes, or group changes proving effective privilege - The exact trust edge that makes the ticket replayable
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill