CTF-Sandbox-Orchestrator/competition-web-runtime/SKILL.md·查看原始 Markdown·索引

name: competition-web-runtime description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for CTF web, API, SSR, frontend, queue-backed app, and routing challenges. Use when the user asks to inspect a site or API, follow real browser requests, debug auth or session flow, trace uploads or workers, find hidden routes, or explain why frontend and backend behavior diverge under sandbox-internal routing. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


Competition Web Runtime

Use this skill only as a downstream specialization after $ctf-sandbox-orchestrator is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to $ctf-sandbox-orchestrator first.

Use this skill when the active challenge is primarily about web behavior, browser state, server routing, API order, or worker-backed application flow.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Assume the presented hosts, domains, and routes belong to the sandbox.
  2. Inspect entry HTML, boot scripts, runtime config, and route registration before trusting the visible UI.
  3. Capture one real request flow end-to-end before making broad claims from source.
  4. Check browser persistence and backend state together.
  5. Re-run the smallest flow with one variable changed.

Workflow

1. Map The Active Runtime

2. Capture The Real Request Order

3. Expand Only After One Path Is Proven

Read This Reference

What To Preserve