CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

conducting-mobile-app-penetration-test

Conducts penetration testing of iOS and Android mobile applications following the OWASP Mobile Application Security Testing Guide (MASTG) to identify vulnerabilities in data storage, network communication, authentication, cryptography, and platform-specific security controls. The tester performs static analysis of application binaries, dynamic analysis at runtime, and API security testing to evaluate the complete mobile attack surface. Activates for requests involving mobile app pentest, iOS security assessment, Android security testing, or OWASP MASTG assessment.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/conducting-mobile-app-penetration-test/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%Weight 40%Scale 1-5

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

The body delivers strong, command-level actionability and a well-sequenced five-phase testing workflow, and the output template with a full finding example is a highlight. However, it spends tokens re-teaching well-known security concepts, lacks explicit validation/reproduction checkpoints between phases, and fails to reference the api-reference.md and agent.py files that exist in its own bundle.

Suggestions

Remove or drastically trim the 'Key Concepts' table and 'Tools & Systems' section — Claude already knows what certificate pinning, Frida, jadx, and Burp Suite are; keep only mobile-specific nuances it would not infer (e.g., ATS exception patterns).

Add explicit validation checkpoints between workflow steps, e.g., after each phase confirm that each suspected finding is reproducible and record the PoC evidence before moving on, mirroring the evidence requirements already shown in the Output Format.

Link the existing bundle files from the body — e.g., under a 'Automation' or 'API reference' heading, point to [api-reference.md](references/api-reference.md) and scripts/agent.py for automated MASTG checks — so the bundled material is discoverable instead of orphaned.

DimensionReasoningScore

Conciseness

The workflow steps are lean and command-driven ('jadx -d output/ target.apk', 'sqlite3 ... ".dump"'), but two full sections explain concepts Claude already knows: the Key Concepts table defines 'Certificate Pinning', 'Frida', 'Deep Links', 'App Transport Security (ATS)', and the Tools & Systems section re-describes MobSF, jadx, and Burp Suite. This is 'mostly efficient but includes some unnecessary explanation' — more than the 'minor instances' of anchor 4, but the rest of the body is not padded, so it is above anchor 2.

3 / 5

Actionability

Mostly executable guidance with copy-paste commands at each step ('grep -rn "api_key\|password\|secret\|token\|aws_" output/', 'objection -g "Target App" explore --startup-command "ios sslpinning disable"', 'adb shell am start -n com.target.app/.InternalActivity -e "user_id" "admin"') and a complete PoC in the output template. Minor gaps keep it from anchor 5: several runtime-manipulation steps describe what to do ('hook the detection function to return false', 'Use Frida to replace Objective-C method implementations') without providing the actual Frida scripts, and the Ghidra/Hopper step gives no procedure.

4 / 5

Workflow Clarity

A clear five-step sequence (Static Analysis → Network → Data Storage → Authentication → Runtime Manipulation) with platform-specific sub-steps, but checkpoints are missing or implicit — the only diagnostics are 'If the app fails to connect through the proxy, it may implement certificate pinning' and 'Verify whether the app detects tampering'. No step validates or reproduces findings before reporting. Matches anchor 3 ('sequence present but checkpoints missing or implicit'); not anchor 4 because 'most checkpoints present' is not satisfied by what is written.

3 / 5

Progressive Disclosure

The bundle contains references/api-reference.md and scripts/agent.py, but the body never mentions or links to either — the API reference and automation script are completely disconnected from SKILL.md navigation. The body itself is well-sectioned, so this matches 'some structure... references present but not clearly signaled' (anchor 3); not anchor 4 because an entire bundle file is orphaned rather than having 'minor organization gaps'.

3 / 5

Total

13

/

20

Passed

Description

92%Weight 40%Scale 1-5

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 strong: it uses third person, enumerates concrete capabilities across the mobile attack surface, and includes an explicit activation clause with natural trigger terms. The only weakness is that the trigger list could include more synonyms and common phrasings users might employ.

DimensionReasoningScore

Specificity

Quotes multiple concrete actions — 'performs static analysis of application binaries, dynamic analysis at runtime, and API security testing' — plus a comprehensive enumeration of vulnerability areas ('data storage, network communication, authentication, cryptography, and platform-specific security controls'). This matches the anchor 'lists multiple specific concrete actions; comprehensive coverage'; it is not score 4 because there are no meaningful coverage gaps, and not below 4 because nothing is generic.

5 / 5

Completeness

Explicitly answers 'what' ('Conducts penetration testing of iOS and Android mobile applications... to identify vulnerabilities in...') and 'when' ('Activates for requests involving mobile app pentest, iOS security assessment, Android security testing, or OWASP MASTG assessment') with concrete trigger phrases — a direct match to the anchor 'clearly and explicitly answers both what AND when with concrete trigger phrases'. Not score 4 because the 'when' clause is explicit and specific, not merely present.

5 / 5

Trigger Term Quality

Trigger clause lists natural phrases users would say: 'mobile app pentest, iOS security assessment, Android security testing, or OWASP MASTG assessment'. Good keyword coverage, but common variations/synonyms are missing (e.g., 'mobile app security audit', 'APK/IPA security review', 'mobile pen test'), so it falls short of the anchor-5 'comprehensive coverage of natural terms including synonyms'; it is clearly above anchor 3 because several relevant natural keywords are present.

4 / 5

Distinctiveness Conflict Risk

Clear niche — mobile application (iOS/Android) penetration testing — with distinct platform-specific triggers ('iOS security assessment, Android security testing, OWASP MASTG assessment'), giving minimal conflict risk with adjacent skills like web or network pentesting. Matches 'clear niche with distinct triggers; minimal conflict risk'; not score 4 because the triggers are platform-anchored and would not naturally fire a non-mobile security skill.

5 / 5

Total

19

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

mukul975/Anthropic-Cybersecurity-Skills

Path

skills/conducting-mobile-app-penetration-test/SKILL.md

Reviewed

Table of Contents

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.