competition-android-hooking — Claude Code skill: what it does
competition-android-hooking — a skill for Claude Code that automates Android app security analysis within a CTF sandbox. It activates for hooking APKs, bypassing SSL pinning, or tracing JNI boundaries.
MIT 110 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a claude-codeWhat competition-android-hooking does
This skill handles Android application analysis tasks, including Frida hooking, request-signing recovery, and SSL pinning bypass. It functions as a downstream module that activates only after ctf-sandbox-orchestrator has established the sandbox environment and analysis priorities.
The workflow covers static triage of APK structures, exported components, and JNI boundary inspection. It requires ctf-sandbox-orchestrator to be active beforehand; without this orchestrator, the skill lacks the necessary context to function.
What it helps with
- Hook calls in an Android application
- Bypass SSL pinning checks
- Recover request-signing logic
- Inspect JNI boundaries and local databases
Example prompts for the agent
- Analyze JNI boundaries in this APK
- Bypass SSL pinning to intercept requests
- Recover the signing logic for this request
How to install competition-android-hooking
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a claude-code2Manually: put the files in place
~/.claude/skills/competition-android-hooking/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-android-hooking/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a codex2Manually: put the files in place
.agents/skills/competition-android-hooking/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a cursor2Manually: put the files in place
.cursor/skills/competition-android-hooking/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-android-hooking/SKILL.md2Manually: put the files in place
.github/skills/competition-android-hooking/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-android-hookingManually: put the files in place
.devin/skills/competition-android-hooking/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -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-android-hooking
How to install competition-android-hooking in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-android-hooking -a claude-code.
What does competition-android-hooking do?
It automates Android security analysis, including hooking calls and bypassing checks within a CTF sandbox environment.
What is required to use this skill?
You must have ctf-sandbox-orchestrator running first to establish the necessary sandbox context and priorities.
Source text
SKILL.md · MIT
--- name: competition-android-hooking description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for Android APK hooking, Frida tracing, request-signing recovery, SSL pinning bypass, JNI boundary inspection, and app trust-boundary analysis. Use when the user asks to hook an APK, inspect signer logic, trace Java or native boundaries, bypass pinning or root checks, inspect shared prefs or app databases, or replay accepted mobile requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # Competition Android Hooking 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 decisive path runs through an Android app's live trust boundary rather than static strings alone. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Preserve the original APK, extracted resources, and decompiled output before patching or resigning. 2. Start with manifest, exported components, deeplinks, native libs, prefs, local DBs, and bundled configs. 3. Decide the narrowest runtime boundary to hook: signer, crypto helper, JNI bridge, WebView bridge, or request builder. 4. Correlate static evidence and dynamic traces before claiming a trust edge is understood. 5. Reproduce the signed request, accepted token, or gated branch from the smallest hook set. ## Workflow ### 1. Static Triage Before Hooks - Map package structure, exported activities, services, receivers, providers, and deeplink handlers. - Note SSL pinning logic, root checks, feature flags, token storage, shared prefs, SQLite tables, and protobuf or RPC boundaries. - Identify whether the sensitive logic sits in Java, Kotlin, JNI, or a bundled WebView. ### 2. Hook The Narrowest Boundary - Prefer hooking request signers, crypto helpers, keystore access, protobuf encode or decode, or JNI marshaling instead of broad UI hooks. - Record plaintext inputs, signed strings, headers, nonces, and outputs at the boundary that actually changes trust. - If pinning or environment checks block progress, patch or hook only enough to expose the real request path. ### 3. Replay The Accepted Path - Rebuild the smallest sequence that reaches the accepted server-side branch: local state, nonce, request body, signature, and headers. - Keep hook logs, captured request shapes, and local storage paths tied to the same account or session state. - If the challenge becomes more about transform recovery than Android runtime, switch back to the broader crypto or mobile skill. ## Read This Reference - Load `references/android-hooking.md` for hook targets, storage checklist, and evidence packaging. ## What To Preserve - Hook points, class names, JNI symbols, signer inputs and outputs, and header names - Shared prefs, local DB rows, deeplinks, exported components, and token storage paths - The smallest replayable request or branch that proves the trust boundary
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill