competition-file-parser-chain
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 con
v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install zhaoxuya520/competition-file-parser-chainWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package306a33b5…5b3166f5
306a33b51e07…65ff5b3166f53 files · 2.0 KBScanLowno findings
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-file-parser-chain@cab634b
On this page
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.mdfor 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
Files in this version
agents/1410 B
- openai.yaml410 B
references/11.0 KB
- file-parser-chain.md1.0 KB
- SKILL.md3.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.9.22-cab634b | Nov 13, 2026 | cab634b | 306a33b5 | Signed | – |
More from zhaoxuya520
All from this publisherMore in Malware and ransomware analysis
See the category- writing-yara-rules-from-reversed-codemeltedinhex/writing-yara-rules-from-reversed-code4
- yara-sigsdariushoule/yara-sigs4
- monitoring-darkweb-sourcesmukul975/monitoring-darkweb-sources3
- deploying-ransomware-canary-filesmukul975/deploying-ransomware-canary-files3
- implementing-honeypot-for-ransomware-detectionmukul975/implementing-honeypot-for-ransomware-detection3
- yaraaeondave/yara3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login