flutter

Flutter app reversing and SSL pinning bypass — reFlutter Dart-AOT patching, BoringSSL bypass, libapp.so static analysis in Ghidra/radare2, Dart snapshot dump, and iOS Flutter.framework notes.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Fix and improve this skill with Tessl

tessl review fix ./packages/decepticon/decepticon/skills/standard/mobile/flutter/SKILL.md

Quality

Content

71%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 playbook is actionable and well-sequenced with concrete commands and built-in verification signals, but it is a monolithic ~250-line file with no progressive disclosure into reference files. Splitting the iOS path, manual patch, and snapshot tooling into referenced files would improve navigation.

Suggestions

Move the iOS Flutter.framework workflow and the manual binary-patch details into separate referenced files to reduce inline bulk and improve progressive disclosure.

Provide the proxy-redirect.js Frida script (or a referenced bundle) so the per-app proxy injection path is fully executable.

Add explicit fix-and-retry feedback loops around the patch/sign/install steps (e.g., if `adb install` fails on signature, use `--bypass-low-target-sdk-block` and retry) to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Largely lean with terse code blocks and inline comments assuming Claude's competence; the explanatory prose (BoringSSL mechanism, version-change notes, snapshot caveats) is non-obvious domain knowledge, though a few passages could be trimmed.	4 / 5
Actionability	Mostly copy-paste ready commands (reflutter, uber-apk-signer, adb, r2, codesign) covering Android/iOS/manual paths; minor gaps from the un-provided proxy-redirect.js and environment-specific placeholders (<offset>, <Burp-IP>).	4 / 5
Workflow Clarity	Clear numbered Step 1–6 sequence with verification signals ("Expect: ~1 class", "HTTPS traffic appears in Burp", ZFP artifacts); not capped at 3 because validation checkpoints exist, though explicit fix-and-retry feedback loops are thin.	4 / 5
Progressive Disclosure	Well-sectioned single file with clear headers and no nested references, but at ~250 lines everything is inline with no split into reference files (e.g., iOS workflow, manual binary patch, snapshot tooling), so organization is good yet not progressively disclosed.	3 / 5
	Total	15 / 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.

The description is specific and well-differentiated with strong trigger terms, but it omits any explicit "when to use" guidance, which caps completeness. Adding a Use-when clause would lift it to the top band.

Suggestions

Append a "Use when..." clause naming trigger scenarios (e.g., intercepting Flutter HTTPS traffic, reversing a Dart AOT app where jadx shows only a stub).

Add natural-language trigger phrases such as "Flutter traffic", "intercept Flutter HTTPS", or "Dart AOT reverse engineering" alongside the technical terms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "reFlutter Dart-AOT patching", "BoringSSL bypass", "libapp.so static analysis in Ghidra/radare2", "Dart snapshot dump", "iOS Flutter.framework notes" — giving comprehensive capability coverage rather than vague abstraction.	5 / 5
Completeness	The "what" is explicit and detailed, but there is no "Use when..." clause or equivalent trigger guidance, so per the rubric completeness is capped at 3.	3 / 5
Trigger Term Quality	Good keyword coverage with synonyms (Ghidra/radare2, reFlutter/Dart-AOT) and file artifacts (.so), but the terms skew technical and omit natural phrasings like "intercept Flutter traffic" or "Flutter HTTP traffic".	4 / 5
Distinctiveness Conflict Risk	A clear niche — Flutter/Dart AOT reversing and BoringSSL pinning bypass — with distinct triggers and minimal overlap risk with other mobile skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: PurpleAILAB/Decepticon
Path: packages/decepticon/decepticon/skills/standard/mobile/flutter/SKILL.md
Commit: 31e1c8e

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

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.