Files
inliver233 90f7a58615 Record the selective-install measurement and the external checks
The brief asked for the shared-tooling question to be settled by the install product
rather than by preference. Measured with --skill apk-reverse -y --copy in an empty
directory:

  the skill is copied whole and self-contained into each detected agent directory
  (six here), every file under <agent>/skills/apk-reverse/ -- SKILL.md, all 28
  references, all 34 scripts including dexpatch/. Nothing outside the skill directory
  is installed, and there is no cross-skill sharing mechanism.

So a root-level shared/ can never work: it is not part of the product. With one skill
there is nothing to share, and had the skill been split the halves would have needed
duplicated scripts or a path that does not survive installation.

VERIFY-OUTPUT.md gains a section recording which premises were re-checked against
primary sources and which did not hold: the blutter build budget and compiler floor,
aotopsy as the no-toolchain route, the idalib-mcp shift away from the GUI plugin, and
that "GNU readelf is on PATH" is false here (it is pyelftools' readelf.py, and MinGW
objdump/nm reject aarch64 outright). Also records one intermittent check_repo.py exit 1
that printed "0 problem(s)" and did not reproduce in five later runs, with the line
numbers of the encoding path that produces it.
2026-09-20 05:01:48 +08:00
..

jiongnew.apk 实测记录

This directory is the evidence record for the apk-reverse skill measured against a real target, not target-specific data the skill ships for reuse. It exists so the Coverage statement in SKILL.md can be checked against the runs behind it, and so a later reader can tell which claims were observed, which were inferred, and which are still unverified.

Target: jiongnew.apk — Flutter AOT, 4 dex, 36 native libraries, no packer. sha256 0C2B063E6D1A3BD05777611ABF2F1A64056E290E4F6728C1B12DC202747DC645, 74,394,920 B, 1,982 entries.

The APK itself is not in this repository (.gitignore excludes *.apk).

Strength labels

Every claim below carries one of three labels, used the same way references/verification.md uses them:

  • observed — reproduced here, with the exact command and its output.
  • inferred — follows from observed facts, but the step itself was not executed.
  • unverified — assumed or reported by a tool and not independently confirmed.

Index

File Covers
TOOL-VERDICTS.md One verdict per tested script, with the independent cross-check behind it
TARGET-FACTS.md What the target is: manifest, dex, natives, assets, versions, and what it does at launch
FINDINGS.md Findings about the skill itself: defects, contradictions, boundary evidence
REPO-DECISIONS.md What changed in the repo as a result, and what deliberately did not