Skip to main content
skill CX Codex

competition-bundle-sourcemap-recovery — Claude Code skill

The competition-bundle-sourcemap-recovery Claude Code skill reconstructs JavaScript structure from served assets and source maps. It runs after ctf-sandbox-orchestrator routes a task involving chunk loading or hidden routes.

MIT 110 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-bundle-sourcemap-recovery -a claude-code
Open on GitHub

What competition-bundle-sourcemap-recovery does

The skill connects files served to the browser with the code that runs in the application. It examines entry HTML, build manifests, chunk maps, source maps, and loaders to recover routes, API calls, and frontend behavior from built artifacts.

ctf-sandbox-orchestrator must establish the sandbox assumptions and evidence priorities first; this skill is a downstream step. It traces the path from a served asset through a loader to a module and its runtime effect. The reference references/bundle-sourcemap-recovery.md contains artifact and evidence checklists.

What it helps with

  • reconstruct JavaScript structure from served assets
  • trace chunk loading to the executing module
  • recover hidden routes and APIs from built files
  • explain frontend runtime behavior from emitted artifacts

Example prompts for the agent

  • After ctf-sandbox-orchestrator has routed the task, reconstruct the JavaScript structure from the served assets and source maps.
  • Trace the chunk loader and identify the module that exposes the hidden route.
  • Inspect the built frontend files and explain how the app calls its API.

How to install competition-bundle-sourcemap-recovery

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-bundle-sourcemap-recovery -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-bundle-sourcemap-recovery/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-bundle-sourcemap-recovery/

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

Questions about competition-bundle-sourcemap-recovery

How do I install competition-bundle-sourcemap-recovery in Claude Code?

Run npx skills add zhaoxuya520/reverse-skill --skill competition-bundle-sourcemap-recovery -a claude-code. The skill file is at ~/.claude/skills/competition-bundle-sourcemap-recovery/SKILL.md.

What does competition-bundle-sourcemap-recovery do?

It traces how served assets, source maps, loaders, and runtime modules fit together to explain frontend behavior.

What does competition-bundle-sourcemap-recovery require?

ctf-sandbox-orchestrator must first establish the sandbox assumptions and route the task to this skill.

Source text

SKILL.md · MIT
---
name: competition-bundle-sourcemap-recovery
description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for source maps, build manifests, chunk registries, emitted bundles, obfuscated loader flow, and frontend runtime recovery. Use when the user asks to reconstruct served JavaScript structure, inspect source maps or chunk maps, trace bundle loading, recover hidden routes or APIs from emitted assets, or explain runtime behavior from built frontend artifacts. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition Bundle Sourcemap Recovery

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 runtime truth lives in built assets, source maps, chunk tables, or obfuscated loader flow rather than in checked-in source alone.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Start from the served artifact set: entry HTML, build manifest, bootstrap bundle, chunk map, and source maps.
2. Record chunk ids, route chunks, loader functions, endpoint strings, and config keys before broad manual deobfuscation.
3. Reconstruct the smallest runtime graph that explains which asset executes now.
4. Keep served artifact truth separate from repository source unless parity is proven.
5. Reproduce the smallest asset-to-runtime boundary that proves the decisive behavior.

## Workflow

### 1. Map The Served Artifact Set

- Record entry HTML, script tags, preload hints, manifest files, asset map, chunk registry, and source map URLs.
- Note framework-specific artifacts such as route manifests, client reference manifests, or lazy-loader tables when present.
- Keep emitted filenames, hash suffixes, and route ownership tied together.

### 2. Reconstruct Runtime Structure

- Follow bootstrap code, chunk loaders, module registry, string decoders, and lazy import boundaries.
- Use source maps, manifest files, and stable symbol clusters to recover route names, API calls, feature flags, and hidden panels.
- Distinguish build-time intent from the bundle that is actively served now.

### 3. Reduce To The Decisive Bundle Path

- Compress the result to the smallest sequence: served asset -> loader path -> module or symbol -> runtime effect.
- State clearly whether the decisive weakness lives in manifest drift, chunk loading, hidden route code, string decoding, or stale source assumptions.
- If the task shifts from built assets to SSR or template enforcement, hand back to the tighter template-render skill.

## Read This Reference

- Load `references/bundle-sourcemap-recovery.md` for the artifact checklist, deobfuscation checklist, and evidence packaging.

## What To Preserve

- Served filenames, chunk ids, manifest entries, source map paths, recovered symbols, and endpoint strings
- The exact executing bundle or module that proves the runtime branch
- One minimal asset-to-runtime sequence that reaches the decisive effect

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Security →

From the same set36

The whole set →
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 competition-request-normalization-smuggling competition-request-normalization-smuggling is a Claude Code skill that analyzes HTTP parsing discrepancies between proxies and backend servers in CTF workflows. CX Codex +1 110installs competition-websocket-runtime competition-websocket-runtime is a Claude Code skill that inspects WebSocket and SSE handshakes, subscriptions, and frames after the orchestrator runs. CX Codex +1 110installs competition-stego-media The competition-stego-media Claude Code skill searches media files for hidden payloads in CTF tasks. It runs after ctf-sandbox-orchestrator routes an image, audio, video, or document for steganography analysis. CX Codex +1 110installs competition-ios-runtime competition-ios-runtime — a skill for Claude Code that automates iOS runtime analysis and hooking. It runs as a downstream module after $ctf-sandbox-orchestrator is active. CX Codex +1 110installs competition-graphql-rpc-drift competition-graphql-rpc-drift — a Claude Code skill compares GraphQL and RPC contracts with live handler behavior. It joins a CTF workflow after the main orchestrator sets up the sandbox. CX Codex +1 110installs

Project sponsors

Companies that keep this analytics open