competition-crypto-mobile — Claude Code skill for CTF analysis
The competition-crypto-mobile Claude Code skill handles CTF tasks involving cryptography, steganography, and mobile apps. It is routed in after sandbox assumptions are set for blob decoding or APK and IPA analysis.
MIT 110 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a claude-codeWhat competition-crypto-mobile does
The skill traces data transformations, looks for concealed media payloads, and examines local trust boundaries in mobile apps. It works through cryptographic parameters in sequence and can follow token storage or request-signing logic.
It runs downstream of $ctf-sandbox-orchestrator, which must establish sandbox assumptions and route the task first. The references/crypto-mobile.md file contains a checklist for transforms, hook targets, and evidence packaging. Android, iOS, and media-steganography tasks can be routed to their specialized skills instead.
What it helps with
- reconstruct a sequence of transforms and recover its keys
- locate concealed data in a media file
- trace how a mobile app signs requests
- inspect token storage and local trust boundaries
Example prompts for the agent
- Trace the transform chain in this CTF challenge and record each parameter.
- Find concealed data in this media file and show the bytes that support the extraction.
- Follow the app's request-signing path and locate its token storage.
How to install competition-crypto-mobile
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a claude-code2Manually: put the files in place
~/.claude/skills/competition-crypto-mobile/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-crypto-mobile/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a codex2Manually: put the files in place
.agents/skills/competition-crypto-mobile/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a cursor2Manually: put the files in place
.cursor/skills/competition-crypto-mobile/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-crypto-mobile/SKILL.md2Manually: put the files in place
.github/skills/competition-crypto-mobile/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-crypto-mobileManually: put the files in place
.devin/skills/competition-crypto-mobile/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -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-crypto-mobile
How do I install competition-crypto-mobile in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-crypto-mobile -a claude-code. The skill file is at ~/.claude/skills/competition-crypto-mobile/SKILL.md.
What does competition-crypto-mobile do?
It supports CTF investigations involving cryptography, steganography, and mobile apps, including transform recovery, hidden payload analysis, and request-signing traces.
What must happen before competition-crypto-mobile runs?
$ctf-sandbox-orchestrator must first establish the sandbox assumptions and route the task to this skill.
Source text
SKILL.md · MIT
--- name: competition-crypto-mobile description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for crypto, encoding, steganography, APK, IPA, and mobile trust-boundary challenges. Use when the user asks to decode a blob, recover a transform chain or key, inspect hidden media payloads, hook an APK or IPA signer, inspect app storage, or replay mobile request-signing logic. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Crypto Mobile 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 active challenge depends on recovering a transform chain, hidden media payload, mobile signing path, or local trust boundary. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Decide whether the dominant path is crypto, stego, or mobile. 2. Recover transforms in order; do not jump straight to the fanciest algorithm. 3. Record exact parameters and boundaries that affect the result. 4. Hook the narrowest mobile boundary that proves the behavior. 5. Reproduce the plaintext, payload, signed request, or accepted branch. ## Workflow ### 1. Crypto And Encoding - Reconstruct the chain step by step: container, compression, encoding, xor or substitution, crypto, integrity, final parse. - Keep exact keys, IVs, nonces, salts, tags, offsets, and byte order. ### 2. Stego - Inspect metadata, chunk layout, palettes, alpha planes, LSBs, thumbnails, trailers, and transcoding artifacts. - Rank decode attempts by evidence, not by brute-force curiosity. ### 3. Mobile - Start with manifest or plist, exported components, deeplinks, native libs, shared prefs, local DBs, and configs. - Trace signer logic, token storage, SSL pinning, protobuf or RPC boundaries, and native bridge calls. ## Read This Reference - Load `references/crypto-mobile.md` for the transform checklist, hook targets, and evidence packaging. - If the task is specifically about Android dynamic tracing, signer hooks, JNI boundaries, or pinning checks, prefer `$competition-android-hooking`. - If the task is specifically about iOS runtime tracing, Keychain access, Objective-C or Swift hooks, or pinning checks inside an IPA, prefer `$competition-ios-runtime`. - If the task is specifically about media carriers, hidden channels, thumbnails, or appended trailers, prefer `$competition-stego-media`. ## What To Preserve - Decisive bytes proving each decode stage - Hook points, signed strings, headers, and local storage paths - Component names, protobuf fields, channel-specific outputs, or trailer offsets
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill