zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/competition-file-parser-chain
competition-file-parser-chain
VerifiedInternal 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.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 3.1 KB |
| agents/openai.yaml | config | 410 B |
| references/file-parser-chain.md | markdown | 1.0 KB |
references/file-parser-chain.md
View on GitHub# File Parser Chain Checklist
## First Pass
- Upload request shape, field names, content type, filename, extension, magic bytes, temp storage
- Archive members, conversion outputs, previews, thumbnails, extracted docs, serialized objects
- Final consumers: parser, converter, renderer, importer, deserializer, worker
## Chain To Reconstruct
1. File ingress accepted
2. Temp or staged artifact created
3. Extraction or conversion performed
4. Parser or deserializer invoked
5. Business-logic effect or artifact produced
## Evidence To Keep Together
- Ingress side: request, filename, MIME, temp path, storage key
- Parser side: tool or library invoked, branch condition, derived artifact, parser choice
- Effect side: rendered output, parsed object, backend branch, worker task, or privilege-bearing result
## Common Pitfalls
- Looking only at the original upload and ignoring derived intermediates
- Treating MIME or extension checks as proof of backend parser choice
- Mixing archive, preview, and deserialization stages without preserving each boundary separately
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 471k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |