Skip to content
SkillModel-led500 tokens in use

competition-file-parser-chain

A downstream CTF-sandbox skill for upload and import paths: it follows a file through extraction, conversion, parser and deserializer steps to the backend effect it produces.

44,996 stars on the repository MIT Licensezhaoxuya520/reverse-skill · CTF-Sandbox-Orchestrator/competition-file-parser-chain

Skill label

measured from its files

What installing competition-file-parser-chain costs

111tokens idle
500tokens in use
720tokens, 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
  • Output12/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 the hard part is following a file from ingress through every parser, extractor, converter or deserializer that touches it. The agent preserves the original upload and each derived artifact separately and records filenames, MIME guesses, temp paths and parser choices.

The skill states that it runs only after the orchestrator has set sandbox assumptions.

What You Get

  • A three-step workflow: map file ingress and derivation, trace parser and conversion boundaries, reduce to the decisive file chain
  • A reference checklist for ingress details, derived artifacts and final consumers
  • A rule to label the original file and each derivative separately
  • A hand-off rule to the queue and worker skill when the chain becomes an async worker problem

Common Use Cases

  • Tracing where an uploaded archive is extracted and which parser reads its members in a lab app
  • Explaining which converter or deserializer a backend picks for a given file
  • Comparing what client-side validation allows with what the backend parser does

What Makes It Unique

It treats the file as a path through several tools and asks for evidence at each boundary. Its listed pitfalls include looking only at the original upload while ignoring derived intermediates, and treating MIME or extension checks as proof of which parser 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 sending files to a sandbox application, unpacking archives and reading temp files, so the agent’s own tools make requests, run commands and write files in the environment the orchestrator set up. The skill does not fetch pages or call APIs on its own.

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