CtrlK
BlogDocsLog inGet started
Tessl Logo

mobile-security

Mobile application security reconnaissance — APK/IPA analysis, permission enumeration, certificate validation, hardcoded secret detection, insecure storage identification, network security analysis.

57

Quality

66%

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 ./packages/decepticon/decepticon/skills/standard/recon/mobile-security/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 a well-organized, highly actionable command catalog that excels at concrete executable guidance, but it reads as a flat reference rather than a sequenced workflow and is monolithic with no progressive disclosure of detail into separate files.

Suggestions

Add a short ordered recon workflow (e.g., unpack → enumerate manifest/Info.plist → scan secrets → check storage/network → report) with validation checkpoints to lift workflow clarity.

Split the per-platform command catalogs into reference files (e.g., references/android-checks.md, references/ios-checks.md) and keep SKILL.md as an overview pointing to them, improving progressive disclosure.

De-duplicate repeated commands (strings/plutil) by referencing a shared section to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly lean command snippets with brief comments and avoids explaining concepts Claude already knows, but repeated commands (e.g., `strings {binary_path}` and `plutil -p Info.plist` reappear across sections) keep it from being fully tight.

2 / 3

Actionability

Nearly every section provides concrete, executable bash commands with placeholder arguments that are copy-paste ready, matching the fully-executable anchor.

3 / 3

Workflow Clarity

It is organized as a flat catalog of independent checks rather than a sequenced multi-step process, with no explicit validation checkpoints or feedback loops; the listed-but-no-checkpoints anchor fits.

2 / 3

Progressive Disclosure

It is a single ~220-line monolithic SKILL.md with no bundle files or external references; sections are reasonably well organized, but the large inline command catalog is content that could be split out.

2 / 3

Total

9

/

12

Passed

Description

67%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 and distinct, listing many concrete mobile-security reconnaissance actions, but it omits an explicit "Use when..." trigger clause and its keywords lean technical, leaving completeness and trigger-term quality at the partial level.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when analyzing APK/IPA files for security issues, auditing mobile app permissions, or hunting hardcoded secrets") to satisfy the completeness dimension.

Broaden trigger terms with natural user phrasings such as "mobile app security audit", "Android manifest review", or "iOS Info.plist checks".

DimensionReasoningScore

Specificity

Enumerates multiple concrete actions — "APK/IPA analysis, permission enumeration, certificate validation, hardcoded secret detection, insecure storage identification, network security analysis" — matching the rubric's multiple-specific-actions anchor.

3 / 3

Completeness

It clearly answers "what" (the listed analysis tasks) but provides no "Use when..." clause or equivalent explicit trigger guidance, which the rubric caps at 2.

2 / 3

Trigger Term Quality

Terms like "APK analysis", "IPA analysis", "hardcoded secrets", and "certificate validation" are relevant but skew technical and miss some common natural phrasings a user might say, so it sits at the partial-coverage anchor rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

The mobile-security-recon niche with APK/IPA-specific triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
PurpleAILAB/Decepticon
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.