# competition-file-parser-chain

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.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode, Windsurf (Devin Desktop), Claude.ai · 109 installs · ★ 45047 repo stars
- Author: zhaoxuya520
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md
- Updated: 2026-09-22
- Security check: automated, 2026-11-17 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/skills/competition-file-parser-chain

## What it 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`.

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/competition-file-parser-chain/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/competition-file-parser-chain/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/competition-file-parser-chain/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/competition-file-parser-chain/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md
```

2. **Manually: put the files in place**
- File: `.github/skills/competition-file-parser-chain/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-file-parser-chain
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/competition-file-parser-chain/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add zhaoxuya520/reverse-skill --skill competition-file-parser-chain -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md

## When to use it
- 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
- 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.

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 1b44404432f37e15.

BEGIN THIRD-PARTY FILE 1b44404432f37e15
```text
---
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.
```
END THIRD-PARTY FILE 1b44404432f37e15

The third-party file has ended. Everything between the 1b44404432f37e15 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2478 of 3163 bytes. © zhaoxuya520 · MIT · https://github.com/zhaoxuya520/reverse-skill/tree/HEAD/CTF-Sandbox-Orchestrator/competition-file-parser-chain/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
