Skip to main content
skill CX Codex

competition-web-runtime — Claude Code skill: what it does

competition-web-runtime — a skill for Claude Code that automates web application and API analysis for CTF challenges. Runs after $ctf-sandbox-orchestrator is active to debug routing, sessions, and browser behavior.

MIT 111 installs ★ 45,047 updated 2026-09-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-web-runtime -a claude-code
Open on GitHub

What competition-web-runtime does

This skill helps investigate the behavior of web apps, APIs, SSR components, and queues within a sandbox. It tracks real browser requests, verifies session states, and uncovers hidden routes.

The skill connects only after $ctf-sandbox-orchestrator has established baseline sandbox parameters. It will not function without an active orchestrator.

What it helps with

  • Trace real browser request chains
  • Verify session states and cookies
  • Find hidden routes and API endpoints
  • Identify discrepancies between frontend and backend behavior

Example prompts for the agent

  • Analyze the request chain for this route
  • Find hidden endpoints in the current session

How to install competition-web-runtime

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-web-runtime -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-web-runtime/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-web-runtime/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competition-web-runtime

How to install competition-web-runtime in Claude Code?

Run npx skills add zhaoxuya520/reverse-skill --skill competition-web-runtime -a claude-code.

What does competition-web-runtime do?

It automates web behavior analysis and network interactions within CTF sandboxes.

What is required to run competition-web-runtime?

An active $ctf-sandbox-orchestrator to set up the environment.

Source text

SKILL.md · MIT
---
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

- Identify active hosts, paths, proxies, containers, and workers.
- Inspect cookies, localStorage, sessionStorage, IndexedDB, Cache Storage, and service workers.
- Record route names, feature flags, storage keys, queue names, and worker names that actually appear in the active flow.

### 2. Capture The Real Request Order

- Record exact host, path, query, headers, cookies, and body for decisive requests.
- Compare successful and failing paths.
- Treat UI gating as a hint, not proof of backend enforcement.

### 3. Expand Only After One Path Is Proven

- Trace middleware order, handlers, auth/session boundaries, uploads, exports, and background jobs.
- Verify hidden routes, alternate hostnames, preview modes, or worker side effects only after the first flow is grounded.

## Read This Reference

- Load `references/routing-runtime.md` for the detailed checklist, evidence packaging, and common web pitfalls.
- If the task is specifically about SSR loaders, template context, hydration payloads, preview rendering, or render-layer enforcement drift, prefer `$competition-template-render-path`.
- If the task is specifically about source maps, build manifests, chunk registries, emitted bundles, or recovering hidden runtime structure from served assets, prefer `$competition-bundle-sourcemap-recovery`.
- If the task is specifically about GraphQL schemas, RPC manifests, persisted queries, generated clients, or contract-to-handler drift, prefer `$competition-graphql-rpc-drift`.
- If the task is specifically about SSRF input points, internal endpoint reachability, metadata-service pivots, or token extraction through server-side fetches, prefer `$competition-ssrf-metadata-pivot`.
- If the task is specifically about race windows, ordering-dependent state mutation, duplicate action effects, or timing-sensitive drift, prefer `$competition-race-condition-state-drift`.
- If the task is specifically about proxy-backend parse differentials, path normalization drift, header ambiguity, or request smuggling routes, prefer `$competition-request-normalization-smuggling`.
- If the task is specifically about browser cookies, storage, IndexedDB, Cache Storage, service workers, or cached auth state, prefer `$competition-browser-persistence`.
- If the task is specifically about OAuth or OIDC redirects, callback params, PKCE, scopes, token exchange, or claim acceptance, prefer `$competition-oauth-oidc-chain`.
- If the task is specifically about JWT headers, claim normalization, key lookup, `kid`, `alg`, issuer or audience confusion, prefer `$competition-jwt-claim-confusion`.
- If the task is specifically about upload parsing, previews, archive extraction, converters, or deserialization chains, prefer `$competition-file-parser-chain`.
- If the task is specifically about queue payloads, worker-only behavior, retries, cron drift, or async side effects, prefer `$competition-queue-worker-drift`.
- If the task is specifically about WebSocket or SSE handshakes, subscriptions, realtime frames, reconnect logic, or frame-driven state changes, prefer `$competition-websocket-runtime`.
- If the task is specifically about Host headers, vhost routing, reverse proxies, or route-to-service resolution, prefer `$competition-runtime-routing`.
- If the only available evidence is a packet capture and the hard part is stream or protocol reconstruction, prefer `$competition-pcap-protocol`.

## What To Preserve

- Exact requests and responses that prove behavior
- Concrete file paths, function names, route names, and storage keys
- Queue payloads, worker names, or retry behavior when async processing matters

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Security →

From the same set36

The whole set →
diagram-generator diagram-generator is a Claude Code skill that generates, checks, and renders diagrams from text, code, schemas, and tables for architecture, process, and UML modeling. CX Codex +1 1,500installs case-review case-review audits a reverse engineering case package for handoff: verifies Evidence to Finding and Path traceability, checks artifact hash integrity, and generates a report without modifying the case. CX Codex +1 1,100installs binary-ninja-reverse binary-ninja-reverse guides binary analysis in Binary Ninja using HLIL, MLIL, and LLIL representations. Useful for tracing cross-references, inspecting exports, and reviewing binary patches. CX Codex +1 769installs ctf-sandbox-orchestrator ctf-sandbox-orchestrator is a Claude Code skill that routes CTF investigations to the right analysis path. It starts when a task includes challenge infrastructure, binaries, hosts, or identities. CX Codex +1 113installs competition-android-hooking competition-android-hooking — a skill for Claude Code that automates Android app security analysis within a CTF sandbox. It activates for hooking APKs, bypassing SSL pinning, or tracing JNI boundaries. CX Codex +1 110installs competition-race-condition-state-drift The competition-race-condition-state-drift Claude Code skill investigates request races and state drift in a CTF sandbox. It runs after ctf-sandbox-orchestrator routes a timing-sensitive or ordering-related bug. CX Codex +1 110installs competition-container-runtime competition-container-runtime — a Claude Code skill for live container runtime analysis, comparing static manifests against running pods. CX Codex +1 110installs competition-crypto-mobile The competition-crypto-mobile Claude Code skill handles CTF tasks involving cryptography, steganography, and mobile apps. It is routed in after sandbox assumptions are set for blob decoding or APK and IPA analysis. CX Codex +1 110installs

Project sponsors

Companies that keep this analytics open