CtrlK
BlogDocsLog inGet started
Tessl Logo

apk-redteam-pipeline

End-to-end Android APK red-team pipeline — automated APK acquisition (Play Store + apkpure + apkmirror fallback), jadx decompilation, secret/URL/JWT/Firebase grep, pinned-cert extraction, exported-component enumeration, Frida runtime instrumentation templates, intent-injection probes. Built from an authorized external red-team engagement where 7 APKs were pulled manually, 4 download attempts truncated, and a hardcoded JWT + 30 internal API endpoints were recovered from one of the apps. Use when target has a mobile app catalogue (Play Store developer page), when you find an APK URL hosted on a web server, or when post-recon mentions "mobile app" in scope.

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Critical

Do not install without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

Highly actionable and well-sequenced, but the body is over-long, lacks validation feedback loops for risky operations, and keeps reference-grade material inline instead of splitting it into bundled files.

Suggestions

Split the 60-pattern secret-grep catalog and Frida scripts into bundled references (e.g. references/secret-patterns.md, scripts/frida-pin-bypass.js) and link from SKILL.md to shrink the monolithic body and lift progressive_disclosure.

Add explicit validation checkpoints for risky batch operations — e.g. confirm a recovered credential still authenticates before mass spraying, and verify Firebase read results before escalating — to raise workflow_clarity above 2.

Trim explanations of concepts Claude already knows (XAPK structure, exported-component intent injection) and merge the two neighboring-skills chain sections into one to improve conciseness.

DimensionReasoningScore

Conciseness

The ~400-line body is mostly efficient and code-dense but includes redundant twin sections ('Bridge to neighboring skills' and 'Related Skills & Chains') and explains concepts Claude already knows (what an XAPK is, how exported components expose attack surface); it is not 3 because those could be trimmed, and not 1 because the bulk is concrete commands.

2 / 3

Actionability

Provides copy-paste-ready curl/jadx/grep commands, a 60-pattern secret catalog with real regexes, executable Frida JS, and mitmproxy setup — fully executable rather than pseudocode.

3 / 3

Workflow Clarity

Stages 0–8 are clearly sequenced with a decision tree, but risky batch/destructive ops (credential 'Spray immediately', Firebase public-read tests) lack explicit validate→fix→retry feedback loops, capping the score at 2 per the batch-operation guideline.

2 / 3

Progressive Disclosure

No bundle files exist and the skill is a monolithic single-file body where the secret-grep catalog and Frida scripts are content that should be split into reference files; it is not 1 because section headers and the decision tree give reasonable organization.

2 / 3

Total

9

/

12

Passed

Description

100%

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

A specific, well-triggered description that covers both capabilities and use-conditions in third person. The only weakness is an over-long authorized-engagement backstory that pads the description without aiding discoverability.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'automated APK acquisition', 'jadx decompilation', 'secret/URL/JWT/Firebase grep', 'pinned-cert extraction', 'exported-component enumeration', 'Frida runtime instrumentation templates', 'intent-injection probes' — matching the level-3 anchor rather than the single-action level-2 example.

3 / 3

Completeness

Explicitly answers both what (the enumerated actions) and when via a literal 'Use when…' clause with three triggers, so it is not capped at 2.

3 / 3

Trigger Term Quality

Trigger terms a user/recon would naturally surface are well covered — 'Play Store developer page', 'APK URL hosted on a web server', 'mobile app in scope' — and it is not below only because the terms are plain and varied rather than jargon-only.

3 / 3

Distinctiveness Conflict Risk

Occupies a clear Android-APK red-team niche with specific triggers, making conflict with other skills unlikely; it is not 2 because the triggers are narrow and domain-locked.

3 / 3

Total

12

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository
elementalsouls/Claude-BugHunter
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.