Skip to content
SkillModel-led612 tokens in use

Competition Windows Pivot

A CTF sandbox skill that documents host-to-host Windows pivots over Kerberos, WinRM, SMB and RDP as a concrete, reproducible chain with evidence.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-windows-pivot
git clone https://github.com/zhaoxuya520/reverse-skill.git
View source

Install command as written in the repository's README

Skill label

measured from its files

What installing Competition Windows Pivot costs

116tokens idle
612tokens in use
790tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

Competition Windows Pivot is a downstream skill of ctf-sandbox-orchestrator for CTF challenges where progress depends on moving between Windows hosts. It organizes the work as a chain: foothold, recovered artifact, replay path, pivot host and resulting capability.

The skill separates stored credential material from usable privilege, keeps host evidence and ticket evidence on one timeline, and records which service accepted each artifact. It is written for sandbox and lab environments set up by the orchestrator, and replies in Simplified Chinese unless English is requested.

What You Get

  • A three-part workflow: recover the replay material, trace the pivot chain, report the edge
  • A Kerberos evidence block listing ticket type, SPN, delegation mode, PAC data, encryption type, cache location and accepting service
  • A host evidence list of event IDs, logon IDs, process, service and task creation, and token or group changes
  • Pointers to four narrower skills for DPAPI, LSASS ticket material, delegation and relay or coercion

Common Use Cases

  • Writing up how a CTF lab chain moved from one Windows host to another
  • Proving which service accepted a ticket or credential in a training domain
  • Separating possession of a ticket from accepted privilege when reviewing a lab result
  • Keeping raw host artifacts apart from the derived timeline in a report

What Makes It Unique

It insists on a destination-side effect. A pivot counts only when the report shows what crossed which boundary and what capability appeared on the target host, and its pitfalls list warns against treating a ticket in hand as proof of privilege. It also acts as a router to the DPAPI, LSASS, delegation and relay skills in the same package.

Under The Hood

The skill is a markdown workflow with one reference checklist and an agent metadata file. It ships no scripts. The instructions direct the agent to inspect host artifacts and logs of the sandbox machines and to follow remote-service traffic, so the agent may run shell or PowerShell commands and open network connections to lab hosts. The skill names credential stores as things to inspect and does not carry commands for extracting them. It applies only after the orchestrator has set sandbox assumptions.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers