CTF sandbox entry (sidecar, not a second router)
ACTION REQUIRED (execute immediately after reading)
NOW: Run../scripts/case-init.ps1; do NOT act against the real external network untilauth.status=granted. For competitions/labs, use-NetworkProfile laboroffline.NOW: Open../../CTF-Sandbox-Orchestrator/ctf-sandbox-orchestrator/SKILL.mdunder the package root, and continue according to its sandbox assumptions.MUST NOTinclude 40+competition-*sub-skills inrouting.json. This entry is just a PRIMARY latch.ACT: Let the orchestrator select a downstreamcompetition-*. If the specific challenge type is already clear (pwn/ROP, APK, IDA), it should have been won by earlier rules inrouting.json—do not override.
Why a separate layer
CTF-Sandbox-Orchestrator/ is a GPL bypass package, licensed by default inside the sandbox. The core routing package remains MIT + scope.md gates. This skill only serves as a keyword entry point; it does not merge the competition tree into the core.
Task completion self-check (MUST pass before claiming completion)
- Did I run case-init / scope first, rather than treating "user said CTF" as granted external access?
- Did I open the sidecar orchestrator, instead of treating 40 sub-skills as PRIMARY?
- If the task is actually pwn/APK/IDA, did I let a more specific PRIMARY take over?