Skip to content
SkillModel-led527 tokens in use

competition-bundle-sourcemap-recovery

A downstream CTF-sandbox skill for built frontends: it uses source maps, manifests and chunk tables to rebuild which served asset runs and what routes or APIs it reveals.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-bundle-sourcemap-recovery

Skill label

measured from its files

What installing competition-bundle-sourcemap-recovery costs

114tokens idle
527tokens in use
755tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Model-led

Script-ledMixedModel-led

Mostly instructions, so how well it works depends on the model that follows them.

This describes the skill's structure, how much of it is scripts. It does not say how well it works.

Touches

Nothing detected: no shell, network, file writes, git or credentials in its files.

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Good
  • Frontmatter12/15
  • Structure23/25
  • Examples3/15
  • Output7/15
  • Size15/15
  • Resources7/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent

No findings.

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity96
  • Maintenance72
  • Community72
  • Maturity28
  • Momentum40

This skill is a specialization of the ctf-sandbox-orchestrator skill for challenges where runtime truth lives in built assets. The agent starts from the served artifact set, which means the entry HTML, build manifest, bootstrap bundle, chunk map and source maps, and reconstructs the smallest runtime graph that explains what executes.

It keeps the served artifacts apart from repository source until the two are shown to match. The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: map the served artifact set, reconstruct runtime structure, reduce to the decisive bundle path
  • A reference checklist covering entry HTML, manifests, chunk registries, source map URLs and framework route manifests
  • A rule to check manifests and source maps before opening large minified bundles
  • A hand-off rule to the template-render skill when the task moves to server-side rendering

Common Use Cases

  • Recovering hidden routes or API endpoints from the emitted assets of a CTF web app
  • Explaining which chunk a lazy loader pulls and what it contains
  • Checking that the repository source matches the bundle the server delivers

What Makes It Unique

It treats the served artifacts as the source of truth and asks the agent to prove which bundle path executes. Its checklist warns against trusting repository source over the served asset set, and against recovering names without showing which module runs.

Under The Hood

The skill is instruction text only: a SKILL.md, one reference checklist and an agent configuration file. It ships no scripts. The method involves requesting the served pages and assets, reading source maps and manifests, and running or decoding bundle code, so the agent’s own tools fetch pages and run commands in the sandbox the orchestrator set up. The skill itself does not call APIs or write files.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers