competition-file-parser-chain

1# Competition File Parser Chain
2 
3Use 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.
4 
5Use this skill when the hard part is following a file from ingress through every parser, extractor, converter, or deserializer boundary that matters.
6 
7Reply in Simplified Chinese unless the user explicitly requests English.
8 
9## Quick Start
10 
111. Preserve the original upload and every derived artifact separately.
122. Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.
133. Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.
144. Separate client-visible validation from backend parser behavior.
155. Reproduce the smallest file-processing chain that yields the decisive branch or artifact.
16 
17## Workflow
18 
19### 1. Map File Ingress And Derivation
20 
21- Record request shape, multipart names, content type, filename, temp paths, upload staging, and storage keys.
22- Note every derived artifact: extracted archive member, converted preview, generated thumbnail, temp document, or deserialized object.
23- Keep original file and each derivative labeled separately.
24 
25### 2. Trace Parser And Conversion Boundaries
26 
27- Show which parser, converter, extractor, or deserializer runs at each step.
28…