CtrlK
BlogDocsLog inGet started
Tessl Logo

reverser-ios-static

iOS IPA static analysis — class-dump-z / class-dump-ng, Hopper / IDA / Ghidra for Mach-O ARM64, Objective-C runtime introspection, Swift demangling, App Transport Security check, plist analysis, embedded provisioning profile parse. For dynamic Frida/Objection see mobile/SKILL.md.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

SKILL.md
Quality
Evals
Security

Quality

Content

90%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.

A tight, highly actionable command reference for iOS IPA static analysis with a clear sequential workflow and good organization. The only gaps are minor: no explicit validation feedback loop and no progressive file-splitting structure, both acceptable for a self-contained cheatsheet of this scope.

DimensionReasoningScore

Conciseness

Lean and command-first throughout — nearly every line is an executable command or a terse operational hint ('cryptid 1 = encrypted', 'PIE always on for iOS'); it assumes Claude's competence with no concept-explanation padding.

5 / 5

Actionability

Fully executable, copy-paste-ready commands cover the common cases (ipatool, unzip, plutil, security cms, otool, class-dump-z, strings|grep, r2 -A, find), with targeted regexes for secrets/URLs and specific symbol names to search for.

5 / 5

Workflow Clarity

Clear sequence (Acquire → Unpack → Quick triage 1–4 → Class-dump → Disassembly → Things to look for) with an implicit checkpoint at the encryption-status check, but no explicit validate→fix→retry feedback loop or checklist; not a destructive/batch op so the cap-3 does not apply.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with content appropriately kept inline for a workflow cheatsheet; the only references are external books/OWASP and a sibling skill, with no bundle files to signal or navigate.

4 / 5

Total

18

/

20

Passed

Description

75%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.

A specific, distinctive description that names the iOS static-analysis niche and its tools with strong keyword coverage. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which leaves the 'when to use' guidance only implied.

Suggestions

Add an explicit trigger clause such as 'Use when statically analyzing an iOS .ipa / .app bundle, inspecting a Mach-O ARM64 binary, or reviewing iOS entitlements, ATS config, and embedded provisioning profiles.'

Lead with the user-natural phrasing (e.g. 'reverse engineer / analyze an iOS app') before the tool list so the trigger matches how users actually phrase the request.

Consider noting prerequisites (e.g. a decrypted IPA) in the trigger clause so Claude knows when static analysis is even possible.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions — 'class-dump-z / class-dump-ng, Hopper / IDA / Ghidra for Mach-O ARM64, Objective-C runtime introspection, Swift demangling, App Transport Security check, plist analysis, embedded provisioning profile parse' — giving comprehensive coverage of the domain.

5 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no explicit 'Use when...' trigger clause; 'For dynamic Frida/Objection see mobile/SKILL.md' is a redirect to a sibling skill rather than a use-trigger for this one, so completeness is capped at 3 per the missing-trigger-clause guideline.

3 / 5

Trigger Term Quality

Good keyword coverage with synonyms (class-dump-z/class-dump-ng, Hopper/IDA/Ghidra) and concrete file types (plist, provisioning profile, IPA, Mach-O), but leans on tool names over the natural phrasings a user might say (e.g. 'reverse engineer an iOS app').

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (iOS IPA static analysis) with highly distinctive tool/term triggers, and explicitly carves out the boundary against the dynamic-analysis sibling skill, minimizing conflict risk.

5 / 5

Total

17

/

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.

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.