CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

75%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, dense playbook: nearly every step is executable, the workflow is logically sequenced with the key version-specific breaking change (Flutter 3.24.0) handled explicitly, and caveats are honest about hit-or-miss tooling. The main gaps are minor: a duplicated BoringSSL explanation, non-executable Ghidra guidance, and a referenced-but-missing Frida script.

Suggestions

Provide the actual proxy-redirect.js Frida hook (or at minimum its concrete Interceptor.attach skeleton) instead of a one-line description.

Replace the Ghidra comment block with concrete Ghidra script or headless-analyzer commands matching the r2 commands shown for the same purpose.

DimensionReasoningScore

Conciseness

The body is efficient and assumes competence (e.g. the jadx-is-useless note earns its place as non-obvious domain knowledge), but the ssl_crypto_x509_session_verify_cert_chain patch mechanism is explained twice — in the Step 2 intro and again in Step 3 — which could be trimmed.

4 / 5

Actionability

Nearly all commands are copy-paste ready (reflutter, uber-apk-signer, adb, r2 one-liners, the byte-level patch), but the Ghidra block is comment-style pseudo-guidance rather than executable steps, and proxy-redirect.js is referenced without being provided.

4 / 5

Workflow Clarity

Steps 1-6 are clearly sequenced with checkpoints ('Expect: ~1 class', 'Launch app — HTTPS traffic appears in Burp') and an error-recovery fallback ('Manual binary patch (if reFlutter fails...)'), but explicit if-fails-then-check recovery guidance is absent in most steps.

4 / 5

Progressive Disclosure

A single-file skill with no bundle files, organized into clear, logically ordered sections with well-signaled cross-skill references; the ~250-line body is longer than the under-50-line simple-skill case, and sections like the iOS path or severity table could live in reference files, keeping this at good-not-perfect structure.

4 / 5

Total

16

/

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-differentiated description that clearly states what the skill does, but it omits any explicit 'when to use' trigger phrasing in the description itself, which limits discoverability. Moving a condensed trigger clause from metadata.when_to_use into the description would resolve the main gap.

Suggestions

Append a trigger clause to the description, e.g. 'Use when a mobile app shows a thin Java/ObjC shell with no dex business logic, or when the user mentions Flutter, libapp.so, or intercepting Flutter HTTPS traffic.'

Add one or two natural-language phrasings users actually say, such as 'intercept Flutter traffic' or 'MITM Flutter app', to broaden trigger term coverage.

DimensionReasoningScore

Specificity

The description lists five concrete, tool-named actions — 'reFlutter Dart-AOT patching, BoringSSL bypass, libapp.so static analysis in Ghidra/radare2, Dart snapshot dump, and iOS Flutter.framework notes' — which is comprehensive coverage of the skill's domain.

5 / 5

Completeness

The 'what' is explicit and detailed, but the description field contains no 'Use when...' clause or equivalent trigger guidance — that guidance lives only in metadata.when_to_use and the body, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Good natural keywords ('flutter', 'ssl pinning bypass', 'reflutter', 'libapp.so', 'boringssl', 'dart snapshot') but a few common user phrasings are missing, e.g. 'intercept Flutter traffic', 'MITM', or 'flutter https'.

4 / 5

Distinctiveness Conflict Risk

Deeply niche terms (libapp.so, reFlutter, BoringSSL in libflutter) give it a clear niche with distinct triggers and minimal conflict risk against generic mobile-reversing skills.

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/mobile/flutter/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.