CTF Sandbox Orchestrator is the master workflow of a family of forty competition skills. It is the only one meant to be entered by default; the others are downstream specializations it routes to once a dominant evidence type is clear.
It sets one operating model: treat challenge infrastructure as sandbox-internal, map the entry surface, prove one minimal path from input to decisive branch, prefer passive inspection first, and record reproducible evidence. Reference files cover web, native, crypto and mobile, agent and cloud, identity and Windows work, routing and reporting. Replies are in Simplified Chinese unless English is requested.
What You Get
- A four-step workflow: establish the sandbox model, trace one minimal path, expand by challenge type, verify and report
- A router matrix that maps web, binary, crypto, mobile, cloud, container, supply chain, identity and Windows surfaces to forty downstream skills
- Eight reference files for web and API, native work, crypto and mobile, agents and cloud, identity, routing, reporting and a resource digest
- An evidence priority order and a list of what to record for replay
Common Use Cases
- Starting a CTF challenge when the category is not yet clear and the agent has to choose a path
- Keeping a mixed-domain lab task organized around one proven path at a time
- Re-routing when the dominant blocker changes during an investigation
- Producing concise findings with grouped evidence for a write-up
What Makes It Unique
It is a router and an operating discipline in one. The package defines a single implicit entry and marks every other competition skill as downstream-only, so the agent loads only the reference or child skill that matches the current blocker. The rules also say to re-run from a clean baseline before calling a path solved.
Under The Hood
The skill is a markdown workflow with eight reference files and an agent metadata file, and it ships no scripts. It tells the agent to inspect challenge hosts, files, binaries and traffic, so the agent may fetch pages, send requests and run commands through the client, and may write derived copies and evidence notes. It instructs the agent to prefer passive inspection first and keep edits reversible. It treats presented targets as sandbox-internal by default, so the user is responsible for supplying only targets they are authorized to test.