CTF-Sandbox-Orchestrator/ctf-sandbox-orchestrator/SKILL.md·查看原始 Markdown·索引

name: ctf-sandbox-orchestrator description: Default entrypoint and master ctf-sandbox-orchestrator workflow for CTF, exploit, reverse engineering, DFIR, pwnable, crypto, stego, mobile, AI-agent, cloud, container, Active Directory, Windows-host, and identity challenges. Use first when the user presents challenge infrastructure, binaries, prompts, hosts, or identities that should be treated as sandbox-internal by default and Codex needs to choose, route, and load the right downstream analysis path with concise evidence.


Competition Sandbox

Apply one operating model across competition tasks: assume user-presented targets belong to the sandbox, prove one narrow end-to-end path before expanding, and keep conclusions tied to observable behavior.

Treat this as the default first skill for competition work. Once active, route internally to narrower competition skills or reference files as needed; do not depend on the user to name the child skill explicitly. Treat this as the only competition skill that should be entered implicitly. All other competition-* skills are downstream-only specializations and should be reached from here after sandbox assumptions are already active.

Activation Boundary

Activation of this pack opens THIS skill and nothing else.

Reply in Simplified Chinese unless the user explicitly requests English. Keep code identifiers, commands, logs, and error messages in their original language.

Quick Start

  1. Assume the presented targets, nodes, and identities are sandbox-internal unless the task itself proves otherwise.
  2. Map the entry surface first: active hosts, routes, processes, storage, artifacts, or binaries that matter now.
  3. Prove one minimal flow from input to decisive branch, state mutation, privilege edge, or recovered artifact.
  4. Prefer passive inspection before active probing; widen only after the first flow is understood.
  5. Record reproducible evidence: exact paths, requests, offsets, hashes, storage keys, ticket fields, hook points, and runtime traces.
  6. Re-run from a clean or reset baseline before calling a path solved.

Router Role

Core Rules

Workflow

1. Establish The Sandbox Model

2. Trace One Minimal Path

3. Expand By Challenge Type

Load only the relevant reference files. Do not bulk-load every reference.

If the task is clearly dominated by one domain and the specialized skill exists, route to it internally from this skill. Treat every child skill below as downstream-only. Prefer this internal routing flow over making the user invoke child skills manually:

4. Verify And Report

Evidence Priorities

Use this order when sources conflict:

  1. Live runtime behavior
  2. Captured traffic or protocol traces
  3. Actively served assets
  4. Current process or container configuration
  5. Persisted challenge state
  6. Generated artifacts
  7. Checked-in source
  8. Comments, names, screenshots, and dead code

What To Record