competition-file-parser-chain — Claude Code skill: install
The competition-file-parser-chain Claude Code skill follows a file from upload to a parser or deserializer. It runs after ctf-sandbox-orchestrator routes a file-processing investigation to it.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a claude-codeWhat competition-file-parser-chain does
The skill traces file handling through upload, temporary storage, archive extraction, conversion, parser calls, and deserialization. It separates checks shown to users from the backend parser’s behavior. It records filenames, MIME guesses, temporary paths, and parser choices.
The result is a minimal sequence from the uploaded file to the backend effect under investigation. The skill also identifies whether the decisive boundary is archive handling, MIME inference, conversion, path resolution, or deserialization. ctf-sandbox-orchestrator must establish the sandbox assumptions and route the investigation first. The ingress and parser checklists are in references/file-parser-chain.md.
What it helps with
- trace an uploaded file through to its backend handler
- identify which parser or converter runs at each stage
- separate user-facing validation from backend parsing
- reduce file handling to a minimal replayable sequence
Example prompts for the agent
- Trace the uploaded file through to the parser and its backend effect.
- Follow the archive extraction, conversion, and deserialization steps.
- Compare the UI's file checks with the backend parser behavior.
How to install competition-file-parser-chain
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a claude-code2Manually: put the files in place
~/.claude/skills/competition-file-parser-chain/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-file-parser-chain/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a codex2Manually: put the files in place
.agents/skills/competition-file-parser-chain/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a cursor2Manually: put the files in place
.cursor/skills/competition-file-parser-chain/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md2Manually: put the files in place
.github/skills/competition-file-parser-chain/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-file-parser-chainManually: put the files in place
.devin/skills/competition-file-parser-chain/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-file-parser-chain
How do I install competition-file-parser-chain in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a claude-code. The skill file is at ~/.claude/skills/competition-file-parser-chain/SKILL.md.
What does competition-file-parser-chain do?
It traces file handling from upload through extraction or conversion to a parser or deserializer, then connects that path to the resulting backend effect.
What does competition-file-parser-chain need to run?
ctf-sandbox-orchestrator must first establish the sandbox assumptions and route the investigation to this skill.
Source text
SKILL.md · MIT
--- 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 - 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
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill