competition-stego-media — Claude Code skill: media steganography
The competition-stego-media Claude Code skill searches media files for hidden payloads in CTF tasks. It runs after ctf-sandbox-orchestrator routes an image, audio, video, or document for steganography analysis.
MIT 110 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a claude-codeWhat competition-stego-media does
The skill examines media containers and helps recover concealed payloads. It checks metadata, thumbnails, palette and alpha channels, least significant bits, spectrograms, video frames, and data appended to a file. Attempts follow evidence rather than blindly testing every transform.
It records container structure and suspicious offsets, then keeps extracted layers and their transformation steps separate. references/stego-media.md contains a media checklist, channel-ranking guidance, and evidence-packaging notes. The skill is a downstream step: ctf-sandbox-orchestrator must first establish sandbox assumptions and route the task here.
Recovery is complete when the payload can be reproduced, not just suspected. If the extracted material turns the task into a cryptography problem, the workflow hands it to the broader crypto skill.
What it helps with
- inspect image channels for concealed data
- check media metadata and thumbnails
- find appended archives or payloads
- reconstruct the extraction and decoding chain
Example prompts for the agent
- Inspect this image’s metadata and alpha channel for a hidden payload.
- Check this audio file for steganographic traces and keep each extracted layer separate.
- Examine the video container, identify suspicious frames, and recover the hidden file.
How to install competition-stego-media
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a claude-code2Manually: put the files in place
~/.claude/skills/competition-stego-media/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-stego-media/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a codex2Manually: put the files in place
.agents/skills/competition-stego-media/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a cursor2Manually: put the files in place
.cursor/skills/competition-stego-media/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-stego-media/SKILL.md2Manually: put the files in place
.github/skills/competition-stego-media/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-stego-mediaManually: put the files in place
.devin/skills/competition-stego-media/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -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-stego-media
How do I install competition-stego-media in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-stego-media -a claude-code. The skill file is at ~/.claude/skills/competition-stego-media/SKILL.md.
What does competition-stego-media do?
It searches images, audio, video, documents, and containers for hidden payloads. The workflow examines file structure and candidate channels, then tracks how to extract and reconstruct the payload.
When does competition-stego-media run?
It runs after ctf-sandbox-orchestrator has established sandbox assumptions and routed a media steganography task to it.
Source text
SKILL.md · MIT
--- name: competition-stego-media description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for image, audio, video, document, and container steganography. Use when the user asks to inspect metadata, alpha or palette channels, LSBs, thumbnails, appended trailers, QR fragments, transcoding artifacts, or recover a hidden payload from media without blind brute force. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Stego Media 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 challenge lives inside a media container, hidden channel, or appended payload rather than a conventional crypto blob. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Confirm the real container type, dimensions, duration, codec, and chunk layout before guessing a hidden layer. 2. Check metadata, thumbnails, sidecar files, and appended trailers before deeper signal-domain work. 3. Rank candidate channels by evidence: alpha, palette, LSB, transform-domain residue, frame order, or container slack. 4. Preserve each extracted layer separately so the transform chain stays reproducible. 5. Stop when the hidden payload is reproduced, not merely suspected. ## Workflow ### 1. Establish Container Truth - Inspect headers, chunk tables, EXIF or document metadata, container indexes, thumbnails, and file size anomalies. - Compare declared format against observed structure to catch polyglots, appended archives, or malformed trailers. - Record exact offsets, frame numbers, or channel boundaries that look promising. ### 2. Inspect Candidate Channels - Check alpha, palette order, RGB or YUV planes, LSBs, spectrogram features, document object streams, or video frame deltas. - Prefer evidence-driven attempts over brute forcing every transform. - Note whether the payload is plain bytes, another media layer, compressed data, or an encrypted blob. ### 3. Reconstruct The Hidden Payload Path - Keep the chain in order: container -> channel or carrier -> extraction -> decompression or decode -> final parse. - Separate extraction success from final interpretation; a channel hit is not the same as artifact recovery. - If the problem becomes primarily about cryptography after extraction, hand off to the broader crypto skill. ## Read This Reference - Load `references/stego-media.md` for the media checklist, channel ranking guide, and evidence packaging. ## What To Preserve - File structure facts: offsets, chunks, frame numbers, stream names, metadata keys, and trailer size - Intermediate extractions and the exact command or transform used to produce them - The final recovered payload and the channel that produced it
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill