mobile-pentest

Mobile app pentest for bug bounty (Android APK + iOS IPA) — runtime-first workflow: install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API exactly like a web target; escalate to decompile (apktool/jadx) and Frida/objection only when traffic is SSL-pinned, encrypted, or absent. Covers APK/IPA decompile for hardcoded secrets + hidden API endpoints + base URLs the web app never exposes, exported-activity and deeplink intent injection, WebView addJavascriptInterface bridge abuse, SSL pinning bypass (objection patchapk / Frida CertificatePinner + checkServerTrusted hooks), OkHttp interceptor chain to recover request signing, JNI native-lib triage, and the quick apktool/grep secret + endpoint sweep. Use when the program scope includes a mobile app, when web recon dries up and you need a fresh attack surface, or when traffic is pinned and you must MitM it.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

77%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and clearly workflow-driven with good validation checkpoints, but it is a verbose monolithic single file with no progressive disclosure to deeper references. Splitting reference material out and tightening time-sensitive prose would lift the weakest dimensions.

Suggestions

Move the detailed Frida/objection hook scripts (sections 4 and 7) and the REAL PAID EXAMPLES into reference files (e.g. references/frida-hooks.md, references/paid-examples.md) and link them one level deep from SKILL.md to improve progressive disclosure and reduce the inline token load.

Relocate time-sensitive version guidance ('Frida 16.7.x, 2025', '--gadget-version 16.7.19') into a dedicated 'Tool versions' or notes section so it does not penalize conciseness and is trivial to update.

Dedupe the KuCoin/Oversecured mentions: keep the impact narrative in sections 5–6 and reduce REAL PAID EXAMPLES to a brief pointer list to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and assumes Claude's competence, but it runs ~330 lines inline, embeds time-sensitive version info ('16.7.x is the stable bug-bounty pick (2025)', '--gadget-version 16.7.19') outside any deprecated/notes section, and repeats the KuCoin/Oversecured examples both inline and in REAL PAID EXAMPLES.	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance — complete adb/apktool/grep/objection commands and complete Frida JavaScript hooks — rather than pseudocode or abstract descriptions.	3 / 3
Workflow Clarity	Sequences work via the numbered RUNTIME-FIRST decision tree with explicit 'STOP'/'escalate' checkpoints, a network-testing loop with 'blocked-by-signer' diagnosis, and a NEVER SUBMIT checklist as an error-recovery gate.	3 / 3
Progressive Disclosure	No bundle files exist and the entire skill lives in one well-sectioned but ~330-line SKILL.md; detailed Frida scripts and the paid-examples section that could be split into reference files are kept inline, and the under-50-line carve-out does not apply.	2 / 3
	Total	10 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete — it clearly communicates both the concrete capabilities and the conditions under which to invoke it, in third person. It is a strong, low-conflict description.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'install app, proxy through Burp/mitmproxy, drive the UI, capture packets, then test the API…decompile (apktool/jadx) and Frida/objection' — matching the anchor for enumerating specific actions rather than vague claims.	3 / 3
Completeness	Explicitly states both what it does and when to use it via an explicit 'Use when the program scope includes a mobile app, when web recon dries up…or when traffic is pinned' clause, with no missing trigger guidance.	3 / 3
Trigger Term Quality	Uses natural terms a bug-bounty hunter would actually say — 'mobile app pentest', 'Android APK', 'iOS IPA', 'SSL pinning', 'Burp/mitmproxy', 'hardcoded secrets' — giving good coverage rather than jargon-only phrasing.	3 / 3
Distinctiveness Conflict Risk	Occupies a clear niche (mobile app pentest for bug bounty) with distinct triggers tied to scope and pinned traffic, making it unlikely to fire for adjacent web-pentest skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: shuvonsec/claude-bug-bounty
Path: skills/mobile-pentest/SKILL.md
Commit: 2009594

Reviewed: 9 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.