CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

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

82%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 strong, execution-ready cheat sheet: nearly every line is a runnable command with a domain-specific pointer of what to look for, organized in a clear end-to-end workflow. Minor room to improve by trimming tool-selection commentary and adding recovery guidance for common failure cases.

DimensionReasoningScore

Conciseness

Nearly lean throughout: commands annotated with domain-specific facts Claude may not know (cryptid flags, ATS/plist keys, keychain attributes). A few lines of tool commentary ('Hopper Disassembler — UI-focused, decent Obj-C support', 'IDA Pro — best Objective-C / Swift but $$$') could be trimmed.

4 / 5

Actionability

Copy-paste-ready bash commands cover the full workflow: acquisition ('ipatool download -b com.target.app', 'frida-ios-dump'), unpacking, triage ('security cms -D -i ... | plutil -p -', 'otool -l ... | grep -A4 LC_ENCRYPTION_INFO'), class-dump, disassembly (r2 command sequence), and concrete grep patterns for secrets, endpoints, and Firebase configs.

5 / 5

Workflow Clarity

Clear logical sequence (Acquire → Unpack → numbered Quick triage → Class-dump → Disassembly → Things to look for) with a real checkpoint (cryptid 0 = ready to analyze). Read-only analysis, so the destructive/batch validation cap does not apply, but there are no feedback loops for failure cases such as class-dump producing nothing on a Swift-only binary.

4 / 5

Progressive Disclosure

Single well-sectioned file with no bundle files to reference; external reading is cleanly collected in a References section and the cross-skill pointer to mobile/SKILL.md is one level deep. At ~150 lines, some 'Things to look for' subsections (secrets, JS bridges, file storage) could be split into reference files, but nothing is buried.

4 / 5

Total

17

/

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 highly specific, well-scoped description that names concrete tools and actions across the full static-analysis workflow. Its main weakness is the missing explicit 'Use when...' trigger clause, which both caps completeness and leaves natural user phrasings like 'reverse engineer an iOS app' and '.ipa' unused.

Suggestions

Add an explicit trigger clause, e.g. 'Use when analyzing an iOS app/IPA file (.ipa), reverse engineering a Mach-O/ARM64 binary, or auditing iOS app security statically.'

Include natural synonyms and the file extension users would mention ('reverse engineer iOS app', '.ipa', 'iOS app security audit') to strengthen trigger-term coverage.

Keep the boundary note about dynamic Frida/Objection analysis, as it usefully separates this skill from its sibling.

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, ATS check, plist analysis, provisioning profile parse — comprehensively covering the static iOS analysis workflow.

5 / 5

Completeness

The 'what' is clear and detailed, but there is no 'Use when...' clause or equivalent explicit trigger guidance; the closing 'For dynamic Frida/Objection see mobile/SKILL.md' is a boundary note, not trigger guidance, which caps completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage (iOS, IPA, Mach-O, ARM64, Objective-C, Swift, Hopper, Ghidra, plist, provisioning profile) but missing natural phrases users would say such as 'reverse engineer an iOS app' and the '.ipa' file-extension form.

4 / 5

Distinctiveness Conflict Risk

'iOS IPA static analysis' is a clear niche and the description explicitly disambiguates from the sibling dynamic-analysis skill ('For dynamic Frida/Objection see mobile/SKILL.md'), giving minimal 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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

PurpleAILAB/Decepticon

Path

packages/decepticon/decepticon/skills/standard/reverser/ios-static/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.