CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md·查看原始 Markdown·索引

name: competition-file-parser-chain description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for file uploads, imports, previews, archive extraction, format conversion, parser invocation, and deserialization chains. Use when the user asks to inspect an upload or import path, trace archive extraction, preview or converter behavior, explain how a file reaches a parser or deserializer, or connect one uploaded artifact to the decisive backend effect. Use only after $ctf-sandbox-orchestrator has already established sandbox assumptions and routed here.


Competition File Parser Chain

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 hard part is following a file from ingress through every parser, extractor, converter, or deserializer boundary that matters.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Preserve the original upload and every derived artifact separately.
  2. Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.
  3. Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.
  4. Separate client-visible validation from backend parser behavior.
  5. Reproduce the smallest file-processing chain that yields the decisive branch or artifact.

Workflow

1. Map File Ingress And Derivation

2. Trace Parser And Conversion Boundaries

3. Reduce To The Decisive File Chain

Read This Reference

What To Preserve