Name: competition-windows-pivot
Author: zhaoxuya520

Imported from zhaoxuya520/reverse-skill (CTF-Sandbox-Orchestrator/competition-windows-pivot/SKILL.md). Install upstream with npx skills add zhaoxuya520/reverse-skill --skill competition-windows-pivot. Copyright stays with the author.

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

Compress the pivot into a concrete chain: foothold -> recovered artifact -> replay path -> pivot host -> resulting capability.
Separate stored credential material from usable privilege.
Keep host evidence, ticket evidence, and privilege effect on one timeline.
Record the exact accepting service or host for every replayed artifact.
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

Install competition-windows-pivot and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "zhaoxuya520-reverse-skill-competition-windows-pivot", "kind": "skill", "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.", "publisher": "zhaoxuya520", "version": "1.0.0", "capabilities": { "domains": [ "math", "customer_support" ], "tags": [ "skill-md", "skills-sh" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "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." ], "primary": false, "metadata": { "source": { "provider": "skills.sh", "repository": "https://github.com/zhaoxuya520/reverse-skill", "path": "CTF-Sandbox-Orchestrator/competition-windows-pivot/SKILL.md", "ref": "HEAD", "url": "https://github.com/zhaoxuya520/reverse-skill/blob/HEAD/CTF-Sandbox-Orchestrator/competition-windows-pivot/SKILL.md", "key": "zhaoxuya520/reverse-skill/CTF-Sandbox-Orchestrator/competition-windows-pivot/SKILL.md" } }, "instructions": "# Competition Windows Pivot\n\nUse 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.\n\nUse this skill when the challenge path is dominated by host-to-host movement, replayable ticket material, or Windows privilege edges.\n\nReply in Simplified Chinese unless the user explicitly requests English.\n\n## Quick Start\n\n1. Compress the pivot into a concrete chain: foothold -> recovered artifact -> replay", "cost": { "context_tokens": 712 } }

competition-windows-pivot

About