competition-ad-certificate-abuse — Claude Code skill for AD CS
The competition-ad-certificate-abuse Claude Code skill traces certificate-based abuse in AD CS CTF sandboxes. It is triggered by questions about templates, enrollment rights, PKINIT, and privilege paths through certificates.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a claude-codeWhat competition-ad-certificate-abuse does
The skill connects CA and certificate-template settings to the way an issued certificate is accepted for authentication or privilege. It records enrollment permissions, EKUs, subject and SAN controls, then follows the path through PKINIT, Schannel, or another accepting service. It runs as a downstream skill: ctf-sandbox-orchestrator must first set the sandbox assumptions and route the task here.
The analysis reduces the path to an enrollment right or misconfiguration, an issued certificate, an accepted mapping, and the resulting privilege. It separates certificate issuance from the later acceptance step. For AD CS and template checklists and evidence packaging, it loads references/ad-certificate-abuse.md. Delegation or ticket transformation after PKINIT belongs back in the Kerberos skill.
What it helps with
- connect enrollment permissions to template settings
- trace how a service accepts an issued certificate
- link a CA or template weakness to resulting privilege
- reduce certificate abuse to its decisive steps
Example prompts for the agent
- Trace certificate-template abuse in this CTF sandbox.
- Show how a certificate's SAN and EKU lead to acceptance through PKINIT.
- Connect the enrollment rights to the privilege granted through this certificate.
How to install competition-ad-certificate-abuse
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a claude-code2Manually: put the files in place
~/.claude/skills/competition-ad-certificate-abuse/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-ad-certificate-abuse/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a codex2Manually: put the files in place
.agents/skills/competition-ad-certificate-abuse/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a cursor2Manually: put the files in place
.cursor/skills/competition-ad-certificate-abuse/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-ad-certificate-abuse/SKILL.md2Manually: put the files in place
.github/skills/competition-ad-certificate-abuse/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-ad-certificate-abuseManually: put the files in place
.devin/skills/competition-ad-certificate-abuse/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -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-ad-certificate-abuse
How do I install competition-ad-certificate-abuse in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-ad-certificate-abuse -a claude-code. The skill file is at ~/.claude/skills/competition-ad-certificate-abuse/SKILL.md.
What does competition-ad-certificate-abuse do?
It examines AD CS settings and follows an issued certificate through authentication or privilege acceptance. It is a downstream CTF-sandbox skill routed by ctf-sandbox-orchestrator.
When does the skill hand a task back to Kerberos?
When the task concerns delegation or ticket transformation after PKINIT, it switches back to the narrower Kerberos skill.
Source text
SKILL.md · MIT
--- name: competition-ad-certificate-abuse description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AD CS, certificate templates, enrollment rights, EKUs, SAN controls, PKINIT, certificate mapping, and cert-based privilege paths. Use when the user asks about ESC-style abuse, certificate templates, enrollment agents, EKUs, SAN or subject controls, smartcard or PKINIT logon, CA policy, or how an issued cert turns into accepted privilege. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition AD Certificate Abuse 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 decisive identity edge is certificate-based and the hard part is proving how a template or CA policy turns into accepted privilege. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Identify the CA, template, enrolling principal, and accepting service before diving into every certificate detail. 2. Separate template enrollability from cert-based authentication or privilege acceptance. 3. Record EKUs, subject or SAN controls, issuance requirements, enrollment rights, and mapping behavior in compact blocks. 4. Tie the issued cert to one accepted path: PKINIT, Schannel, LDAPS, WinRM, or another mapped service. 5. Reproduce the smallest certificate issuance-to-acceptance chain that yields the decisive privilege. ## Workflow ### 1. Map CA And Template Trust - Record CA configuration, template name, enrollment permissions, manager approval, authorized signatures, EKUs, subject requirements, and SAN behavior. - Note whether the path depends on alternate subject names, `UPN`, DNS names, enrollment agent behavior, or template supersedence. - Keep principal, template, and issuance policy tied together. ### 2. Prove Cert-To-Privilege Acceptance - Show how the issued certificate is mapped or accepted: PKINIT, smartcard logon, Schannel auth, service mapping, or explicit certificate mapping. - Record serial, subject, SAN, EKU, validity, and the exact service or domain edge that accepts it. - Distinguish certificate issuance from the separate step where privilege is actually granted. ### 3. Reduce To The Decisive Abuse Chain - Compress the path to the smallest sequence: enrollment right or misconfig -> issued cert -> accepted mapping -> resulting privilege. - State clearly whether the weakness lives in template config, CA policy, mapping logic, relay path, or enrollment rights. - If the task is really about delegation or ticket transformation after PKINIT, switch back to the tighter Kerberos skill. ## Read This Reference - Load `references/ad-certificate-abuse.md` for the AD CS checklist, template checklist, and evidence packaging. ## What To Preserve - CA names, template names, rights, EKUs, issuance flags, SAN controls, and mapping details - Issued certificate fields, serials, subjects, SANs, and the accepting service or logon path - The smallest reproducible enrollment-to-privilege chain
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill