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 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install zhaoxuya520/competition-file-parser-chainEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete306a33b5…5b3166f5
306a33b51e07…65ff5b3166f53 archivos · 2.0 KBEscaneoBajosin hallazgos
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-file-parser-chain@cab634b
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
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
Archivos de esta versión
agents/1410 B
- openai.yaml410 B
references/11.0 KB
- file-parser-chain.md1.0 KB
- SKILL.md3.1 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | No | No |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.9.22-cab634b | 13 nov 2026 | cab634b | 306a33b5 | Firmada | – |
Más de zhaoxuya520
Todo de este publicadorMás en Análisis de malware y ransomware
Ver la categoría- 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
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login