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.

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