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.
Start a fresh conversation. Replace the highlighted placeholders.
Use competition-file-parser-chain to Use competition-file-parser-chain 在已由 ctf-sandbox-orchestrator 确立授权 CTF 实验室范围后，基于[已脱敏的上传、派生文件与日志]离线追踪文件从入口到提取、转换、解析器及最终消费者的链路，报告最早可证实的用户可见验证与后端行为差异；请用简体中文提供带证据关联的最小文件处理序列，不执行上传、构造载荷、反序列化或实时访问。
Required inputs
[已脱敏的上传、派生文件与日志]
User-approved starter prompt based on a pinned source version; check current skill requirements before running. Task evidence ↗
SKILL.md
name: competition-file-parser-chaindescription: 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
Preserve the original upload and every derived artifact separately.
Map the chain in order: ingress, temp storage, archive extraction, format conversion, parser call, deserialization, and final consumer.
Record filenames, MIME guesses, extensions, temp paths, and parser choices before mutating anything.
Separate client-visible validation from backend parser behavior.
Reproduce the smallest file-processing chain that yields the decisive branch or artifact.
Workflow
1. Map File Ingress And Derivation
Record request shape, multipart names, content type, filename, temp paths, upload staging, and storage keys.
Note every derived artifact: extracted archive member, converted preview, generated thumbnail, temp document, or deserialized object.
Keep original file and each derivative labeled separately.
2. Trace Parser And Conversion Boundaries
Show which parser, converter, extractor, or deserializer runs at each step.
Record parser-specific decisions driven by extension, MIME, magic bytes, schema, archive member names, or embedded metadata.
Distinguish parsing success, preview success, conversion success, and business-logic acceptance.
3. Reduce To The Decisive File Chain
Compress the result to the smallest sequence: upload -> derived artifact -> parser boundary -> resulting effect.
State clearly whether the decisive weakness lives in archive handling, MIME inference, file conversion, path resolution, or deserialization.
If the chain becomes mostly a generic async worker problem after enqueue, hand off to the tighter queue or worker skill.
Read This Reference
Load references/file-parser-chain.md for the ingress checklist, parser checklist, and evidence packaging.
What To Preserve
Original uploads, derived files, temp paths, storage keys, parser names, and conversion steps
The exact boundary where backend behavior diverges from user-visible validation
One minimal replayable file-processing sequence that reaches the decisive effect