Agent skill

APK Static Analysis

by dslsdzc in dslsdzc/rev-skills

Guides static analysis of an Android APK with jadx and apktool: reading the manifest, Java code, resources and permissions, and recognizing hardening or obfuscation.

Apache-2.0Auto-check passedSecurity

SKILL.md written in Chinese; this summary is our English description.

Install APK Static Analysis

skills CLI
$ npx skills add dslsdzc/rev-skills --skill re-apk -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install dslsdzc/rev-skills re-apk --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/dslsdzc/rev-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/re-apk .claude/skills/re-apk && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
re-apk
GitHub stars
125
Token cost
~2k tokens
SKILL.md length
599 words
Files
3 (incl. references)
Skills in repo
41
Repo updated
First seen
Licence
Apache-2.0

At a glance

Guides static analysis of an Android APK with jadx and apktool: reading the manifest, Java code, resources and permissions, and recognizing hardening or obfuscation.

  • Works in 6 steps: 解包(apktool d) → AndroidManifest 入口/权限/组件 → jadx 反编译 Java → …
  • Opening an unfamiliar APK to review its manifest, permissions and exported components
  • SKILL.md covers 何时使用 / 何时不用, 工具准备, 操作步骤 and 跨域联合, plus 1 more section
  • Calls brew, adb and apt; reaches github.com

What it does

This skill covers the static side of reversing Android packages. It applies when you have an APK and need to see its manifest, decompiled Java, resources, permissions and component structure, or to recognize packing and resource obfuscation before unpacking or patching. It sends runtime hooking, native library logic and DEX extraction from memory to other skills in the same collection.

A long tool-preparation section gives sources, install routes and a version check for each tool: jadx for Java decompilation (needing Java 11 or newer), apktool for unpacking and rebuilding (with a note that its 3.x and 2.x lines differ in commands), aapt2 for resource dumps, optional dex2jar, apksigner and keytool for re-signing, and adb for device checks. Steps are to be done in order with each result recorded as an evidence path and sha256 hash. Two reference files hold commands and known pitfalls, and the excerpt is cut off before the steps. The skill text is in Chinese.

When your agent uses it

  • Opening an unfamiliar APK to review its manifest, permissions and exported components
  • Decompiling an Android app to read its Java code and resources
  • Telling whether an APK is packed or obfuscated before deeper analysis

Example prompts

  • “Decompile app-release.apk with jadx and list its activities, services and requested permissions.”
  • “Unpack this APK with apktool and tell me whether the resources look obfuscated.”
  • “Check which tools I still need to install for static APK analysis on this machine.”

Requirements

  • Java 11 or newer for jadx
  • jadx and apktool installed
  • Android SDK build-tools for aapt2 and apksigner

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. 解包(apktool d)
  2. AndroidManifest 入口/权限/组件
  3. jadx 反编译 Java
  4. smali 补丁思路
  5. 加固/混淆识别
  6. AAB 与 split APK(分发形态边界)

What it can do on your machine

Read from SKILL.md and the folder at commit bd21db8. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • brew
    • adb
    • apt
    • dnf

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • github.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

APK Static Analysis loads about 2k tokens when it runs, and up to ~5.2k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 599 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~21
When it runs · the whole SKILL.md, loaded when a task matches
~2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~5.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from dslsdzc/rev-skills at commit bd21db8, republished under its Apache-2.0 licence (© dslsdzc). 599 words, ~1,952 tokens.

Download SKILL.mdSave it as .claude/skills/re-apk/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
re-apk
description
APK 静态分析:jadx/apktool、manifest、smali、加固识别。 触发词:apk、android逆向、jadx、smali、dex
capabilities
dex-parser

APK 静态分析

何时使用 / 何时不用

  • 用:拿到 APK / 安卓应用包,需要看清单、Java 代码、资源、权限、组件结构
  • 用:需要识别加固 / 混淆(壳、资源混淆),为脱壳或补丁做准备
  • 不用:需要运行时 hook / 解密 / 绕过(走 [[re-frida]])
  • 不用:目标是原生库 .so 的逻辑(走 [[re-binary-core]] 的 [[re-format-elf]])
  • 不用:需要从运行时内存提取 DEX(走 [[re-memdump]])

工具准备

纯静态分析(解包 / 反编译)可免沙箱([[re-analyze/platform-tips]] 最高原则);涉及动态 / 脱壳转 [[re-frida]] / 脱壳域。所有工具先验证再使用。

jadx —— Java 反编译主力(含 JADX GUI)
  • 官方/GitHub release:https://github.com/skylot/jadx/releases 下载 jadx-<版本>.zip,解压后运行 bin/jadx(Linux/macOS)或 bin\jadx.bat(Windows);GUI 是 bin/jadx-gui
  • macOS: brew install jadx;Arch: pacman -S jadx
  • 依赖 Java 11+(官方要求 11+ 且 64 位):Linux apt install openjdk-17-jre / dnf install java-17-openjdk / pacman -S jre17-openjdk;macOS brew install openjdk
  • Windows/WSL: WSL 内用 Linux 版 zip
  • 验证: jadx --version;版本注——release zip 与 brew/pacman 包同步更新,以实测版本为准
apktool —— 解包 / 回编译(官方/GitHub release)
  • 依赖 Java 8+(官方安装页的最低要求,jar 以 Java 8 为目标编译)。官方 wrapper:从 https://github.com/iBotPeaches/Apktool/releases 下载 apktool_<版本>.jar 与 wrapper 脚本(Linux/macOS apktool、Windows apktool.bat),脚本与 jar 放同目录
  • 版本模型:3.x 为当前主线,2.x 为维护线——两线命令不完全兼容,官方文档也按 3.x / 2.x 分轨。下载后先 apktool --version 确认 major version;2.x 时代的命令与教程直接拿到 3.x 上会报 Unrecognized option(变化清单见 [[gotchas]] 版本差异)
  • Debian/Ubuntu: apt install apktool(仓库版较旧,命令行为兼容即可)
  • macOS: brew install apktool
  • Windows/WSL: WSL 内 Linux 版
  • 验证: apktool --version
aapt2 —— 资源转储 / 还原混淆资源
  • Android SDK build-tools 自带。安装 cmdline-tools 后:sdkmanager "build-tools;34.0.0",路径 $ANDROID_HOME/build-tools/34.0.0/aapt2
  • macOS: brew install --cask android-commandlinetools 后 sdkmanager "build-tools;34.0.0"
  • Windows: Android Studio → SDK Manager 勾选 build-tools
  • 验证: aapt2 version;版本注——build-tools 版本随 SDK 更新(示例 34.0.0,新版 SDK 自带更高版本),命令接口稳定,按已装版本使用即可
dex2jar(可选)—— dex → jar
  • GitHub release:https://github.com/pxb1988/dex2jar/releases 下载 zip,解压后 d2j-dex2jar.sh classes.dex 得 jar,再用 jd-gui 浏览
  • 需要 Java
  • 验证: d2j-dex2jar.sh --version
apksigner / keytool —— 重打包签名(smali 补丁配套)
  • apksigner 在 Android SDK build-tools(同 aapt2 路径);keytool 随 Java 自带
  • 验证: apksigner --version;keytool -help
adb —— 设备安装 / 重打包闭环验证
  • Android SDK platform-tools 自带(sdkmanager "platform-tools")
  • Linux: apt install adb(Debian/Ubuntu);macOS: brew install --cask android-platform-tools;Arch: pacman -S android-tools
  • Windows: platform-tools zip 官方下载
  • 验证: adb version

操作步骤

按顺序执行,每步记下结果(证据路径 + sha256,见 [[re-triage]])。

  1. 解包(apktool d):

    sh
    apktool d app.apk -o out/

    解出 AndroidManifest.xml、smali/(可回编译的字节码)、res/、assets/、lib/。-s(--no-src)不解码源码(只出资源)、-r(--no-res)不解码资源(只出 smali),补丁时按需组合。产物比 jadx 更适合改后回编译。

  2. AndroidManifest 入口/权限/组件:

    sh
    grep -E 'application|activity|service|receiver|provider' out/AndroidManifest.xml | head -40

    记录:主入口(application / 首个 activity 的 android:name)、uses-permission(短信 / 通话记录 / 设备管理权限是恶意或敏感信号)、exported 组件、android:debuggable="true"(可调试应用可直接 [[re-frida]] attach)。加固后入口常被替换成壳类(见坑 1)。

  3. jadx 反编译 Java:

    sh
    jadx -d java-out app.apk          # 批量反编译全部 dex 类
    jadx app.apk                      # 或 GUI 模式逐类浏览

    先看入口类(Application / MainActivity)与算法 / 校验类;敏感串(密钥、URL、校验逻辑)按 grep -rE 'key|secret|sign|license' java-out/ 定位。dex2jar 等价替代:d2j-dex2jar.sh app.apk 得 jar 后用 jd-gui,jar 也可转 [[re-java]] 流程(CFR/JD-GUI 浏览、Java 加固识别)。反编译不出业务代码 → 加固识别(步骤 5)。

  4. smali 补丁思路:

    sh
    # 改 smali 后回编译、对齐、签名、安装(用 apksigner 时 zipalign 必须在签名之前,签名后不得再改包)
    apktool b out/ -o patched.apk
    keytool -genkey -v -keystore ks.jks -alias r -keyalg RSA -validity 3650 -storepass 123456
    zipalign -P 16 -f -v 4 patched.apk aligned.apk
    apksigner sign --ks ks.jks --out signed.apk aligned.apk
    adb install signed.apk

    常用改法:条件跳转取反(if-eqz ↔ if-nez)、把 const/4 v0, 0x0 改成返回常量、把校验方法直接 return-void。先 jadx 定位逻辑再在对应 smali 里改。目标含签名自校验时补丁可能被拦(见坑 2)。

  5. 加固/混淆识别:

    • 壳特征:jadx 只见壳类(com.stub.StubApp=爱加密、com.secneo.apkwrapper / com.bangcle.*=梆梆,乐固等);lib/ 多一个壳 so(libjiagu.so=360 加固、libDexHelper.so=爱加密…);classes.dex 体积异常小(真 dex 运行时解密)
    • 资源混淆特征:res/ 资源路径被随机改名、resources.arsc 结构异常
    • 识别为加固 → 转脱壳域([[re-anti-analysis]] / [[re-mobile-pack]])或动态取内存 DEX([[re-frida]] / [[re-memdump]]);壳名/节区/熵的细粒度指纹对照走 [[re-packer-id]];资源混淆用 aapt2 还原:
      sh
      aapt2 dump badging app.apk      # 包名 / 入口 / 权限速览
      aapt2 dump resources app.apk    # 混淆后的资源映射
  6. AAB 与 split APK(分发形态边界):

    • .aab(Android App Bundle):本质是 zip,内含 dex 与资源——jadx 可直接打开读代码;真机安装需经 bundletool 生成 APKS,拿到 .aab 按步骤 1-3 走即可
    • split APK(base.apk + config.*.apk):主 dex 与代码在 base,语言/密度等配置在 split——静态分析以 base 为主,资源差异在 split 中比对;apktool 对 base 与 split 分别解包
Show full SKILL.md (227 more words)Show less

跨域联合

  • [[re-mobile]]:工作流第 2 步(APK 静态分支)固定调用本技能
  • 需要运行时(解密 / hook / 绕过)→ [[re-frida]];运行时内存取 DEX → [[re-memdump]]
  • 加固 / 带壳 → [[re-anti-analysis]](脱壳域)与 [[re-mobile-pack]](加固脱壳专项);原生 .so → [[re-binary-core]]([[re-format-elf]] / [[re-ghidra]])
  • dex→jar 后的 Java 层深挖(混淆 / Java 加固)→ [[re-java]]
  • 本技能被 [[re-analyze]] 的 triage「移动 App 分析」路径调用(re-mobile → re-apk)

常见坑与陷阱

  • 加固样本 jadx 只看到壳壳:现象——反编译出来只有 StubApp 之类壳类,业务代码全无;原因——真 dex 加密存放在 assets/ 或运行时才解密;对策——按步骤 5 识别壳,转 [[re-anti-analysis]] 脱壳,或 [[re-frida]] / [[re-memdump]] 运行时取内存 DEX

  • 签名校验拦补丁:现象——重打包安装后闪退或报"签名不一致 / 未签名";原因——应用内自校验签名(对比 PackageManager 的签名信息);对策——定位校验点打补丁绕过(smali 改返回值 / 跳转),或 [[re-frida]] hook PackageManager.getPackageInfo 调用链

  • 资源混淆后无法直接看资源:现象——res/ 路径与资源 ID 对不上、strings 定位不到目标资源;原因——资源被混淆随机改名;对策——aapt2 dump 还原映射(步骤 5),必要时结合动态分析对照

  • 原生 .so 被当 Java 分析:现象——Java 层找不到核心逻辑(算法 / 反调试);原因——敏感逻辑写在 JNI 的 .so 里;对策——lib/ 下 so 转 [[re-format-elf]] + [[re-ghidra]]([[re-binary-core]]),用导出表 / Java_<包名>_<类名>_<方法名> 风格符号对 JNI 函数

  • apktool 回编译失败:现象——apktool b 报资源编译错误;原因——解包时资源被解码、部分资源格式不兼容回编译;对策——apktool d -r 保留原资源不解码,只改 smali 后回编译

  • split APK 只分析 base 会缺资源:现象——目标字符串/资源在 base 里找不到;原因——语言/密度配置拆在 config.*.apk split 里;对策——apktool 对 base 与各 split 分别解包,资源差异按 split 比对(步骤 6)

  • 自写 dex 解析四细节:opcode 是 u16 低字节(高字节是寄存器位,读完整 u16 当 opcode 全错位);fill-array-data 是 0x26(31t)、goto 是 0x28(0x24 是 filled-new-array,凭记忆必错);string_data_item 有 uleb128 长度前缀(不跳过会把长度当字符);code_item 的 insns_size 在 +12(+4 是 outs_size)——手写解析器前先对照 dex 规范核对布局

  • jadx 目录只剩启动脚本:现象——jadx 报 ClassNotFound;原因——安装不完整(jar 缺失/被清理);对策——从 GitHub release 重下完整 zip(codeload.github.com 比 github.com 稳),或直接用 baksmali 等单一工具

  • 容器/双开(VirtualApp 类)样本分析:现象——样本跑在双开容器里行为异常、hook 不到目标进程,或要分析容器本身;原因——VA/Blackbox 容器通过"代理桩 + 动态注册"模拟系统:启动 Activity 走容器内假 AMS(Binder 动态代理拦截,把 VAPP 请求参数还原后再转发真实系统);IO 重定向把写死的绝对路径转向容器内安装路径;ContentProvider 的 onCreate 作为容器初始化入口(handleBindApplication 主动调用);原理同老版 Android(VA 只支持老版本,Blackbox 为现代参考实现);对策——分析容器内应用时注意进程真实归属(容器进程 vs 宿主进程)、hook 点选在容器框架层(假 AMS/IO 重定向函数)而非应用层;识别双开环境(双开检测)看 /proc/self/maps 容器 so、假包名路径特征;这类原理对免安装运行/插件化分析也通用

  • 重打包后 install -r 不生效(重打包陷阱):现象——重打包签名安装后行为毫无变化,误判「patch 无效」;原因——同包名同签名时 -r 会替换既有应用并保留数据,versionCode 未递增不阻止内容更新(它主要影响降级安装规则),「patch 未生效」应排查:签名校验链(见下条)、split APK 不一致、多用户/profile 的安装目标、构建产物缓存(apktool 回编译 build 缓存未清理)、目标进程未重启;对策——装机后做闭环验证:adb shell pm path <包名> 取回已装 APK,对 patch 地址做字节级比对,字节确认在位后再排查逻辑层(消费点错误等)(来源:reverse-skills(inliver233),MIT)

  • 签名校验跨层链与系统版本漂移:现象——重打包后仍弹「签名不一致」类提示,或复用旧式签名适配 hook 后在新系统上反而误报篡改;原因——签名校验常是跨层链(Java 层取签名信息 → 摘要计算 → 原生层与硬编码基线比对,任一层不匹配即判失败),只中和单点不够;应用自带 PackageManager 签名适配 hook 可复用(拦截 getPackageInfo 系列、同时替换 signatures 与 signingInfo、只作用于自身包),但其反射构造的内部签名对象(如 SigningDetails)构造器签名随系统版本变化,抛异常返回 null 后触发误判;对策——优先复用应用自带的签名适配 hook,版本漂移时用 Frida 探测活构造器、改走公开构造器重建;带壳目标优先免重打包(运行时签名适配),无壳再考虑重打包;静态侧找原生比对函数中和失败分支(来源:reverse-skills(inliver233),MIT)

© dslsdzc, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in .claude/skills/re-apk of dslsdzc/rev-skills.

  • SKILL.md
  • references/commands.md
  • references/gotchas.md

Open the folder on GitHubat commit bd21db8

Compare with similar skills

APK Static Analysis next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

APK Static Analysis compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
APK Static Analysis this skilldslsdzc/rev-skills125—~2kAutomated safety check: PassApache-2.0
Android APK Pentesterptn1411/skill219—~917Automated safety check: PassNone
Performing Dynamic Analysis Of Android Appmukul975/Anthropic-Cybersecurity-Skills34k—~2.2kAutomated safety check: WarnApache-2.0
Performing Android App Static Analysis With Mobsfmukul975/Anthropic-Cybersecurity-Skills34k—~1.8kAutomated safety check: PassApache-2.0
Mobile Reversesickn33/agentic-awesome-skills47k1 repos~1.5kAutomated safety check: PassMIT
Performing iOS App Security Assessmentmukul975/Anthropic-Cybersecurity-Skills34k—~3kAutomated safety check: PassApache-2.0

Similar skills

  • Runs a full workflow for authorized Android app security testing: static APK analysis, rooted emulator setup, traffic interception and Frida hook generation.

    219 GitHub stars~917 tokensUpdated 17 days ago
    SecurityAuto-check passed
  • Performing Dynamic Analysis Of Android App

    mukul975/Anthropic-Cybersecurity-Skills

    Performs runtime dynamic analysis of Android applications using Frida, Objection, and Android Debug Bridge to observe application behavior during execution, intercept function calls, modify runtime…

    34k GitHub stars~2.2k tokensUpdated 1 mo ago
    SecurityAuto-check: warnings
  • Performing Android App Static Analysis With Mobsf

    mukul975/Anthropic-Cybersecurity-Skills

    Performs automated static analysis of Android applications using Mobile Security Framework (MobSF) to identify hardcoded secrets, insecure permissions, vulnerable components, weak cryptography, and…

    34k GitHub stars~1.8k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Mobile Reverse

    sickn33/agentic-awesome-skills

    Authorized Android/iOS application reverse engineering and security testing: APK/IPA analysis, runtime instrumentation (Frida/Objection), SSL-pinning and jailbreak/root-detection bypass, per OWASP…

    47k GitHub starsUsed in 1 repo~1.5k tokens
    SecurityAuto-check passed
  • Performing iOS App Security Assessment

    mukul975/Anthropic-Cybersecurity-Skills

    Performs comprehensive iOS application security assessments using Frida for dynamic instrumentation, Objection for runtime exploration, SSL pinning bypass for traffic interception, keychain…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    SecurityAuto-check passed
  • Analyzing Android Malware With Apktool

    mukul975/Anthropic-Cybersecurity-Skills

    Perform static analysis of Android APK malware using apktool for resource decompilation, jadx for Java source recovery, and androguard for manifest inspection, dangerous permission-combination…

    34k GitHub stars~620 tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from dslsdzc/rev-skills

All 41 skills in this repo
  • Re Attribution

    dslsdzc/rev-skills

    威胁归因方法论:钻石模型、基础设施图谱、置信度分级与归因报告. An agent skill from dslsdzc/rev-skills.

    125 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Captures an analyzable sample from a live system when the target leaves no file on disk, by finding abnormal executable memory and the execution context that reached it.

    125 GitHub stars~2k tokensUpdated 3 days ago
    Auto-check passed
  • Re Fp Runtime

    dslsdzc/rev-skills

    函数式语言运行时逆向(Haskell/OCaml):闭包/堆对象模型、调用约定、数据流优先策略. An agent skill from dslsdzc/rev-skills.

    125 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Re Hypervisor

    dslsdzc/rev-skills

    虚拟化逆向:VT-x/SVM、hypervisor 检测、VMCS/EPT 分析, 以及 Xen / QNX Hypervisor / Jailhouse / ACRN / Bao / Hyper-V·VMBus / XtratuM / LynxSecure / Quest-V 的分区与 vdev 语义。

    125 GitHub starsUsed in 1 repo~3.4k tokens
    Auto-check: notes
  • Re Sdr

    dslsdzc/rev-skills

    射频逆向:信号采集、频谱分析、解调、帧同步与协议恢复、重放. An agent skill from dslsdzc/rev-skills.

    125 GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed
  • Re Uefi

    dslsdzc/rev-skills

    UEFI/BIOS 固件:SEC/PEI/DXE/BDS 阶段判定、DXE 驱动、UEFI 模块、bootkit. An agent skill from dslsdzc/rev-skills.

    125 GitHub starsUsed in 1 repo~2.3k tokens
    Auto-check passed

Works with

Categories

Questions about APK Static Analysis

What does APK Static Analysis do?

Guides static analysis of an Android APK with jadx and apktool: reading the manifest, Java code, resources and permissions, and recognizing hardening or obfuscation. This skill covers the static side of reversing Android packages. It applies when you have an APK and need to see its manifest, decompiled Java, resources, permissions and component structure, or to recognize packing and resource obfuscation before unpacking or patching.

When should I use APK Static Analysis?

APK Static Analysis fits situations like: opening an unfamiliar APK to review its manifest, permissions and exported components; decompiling an Android app to read its Java code and resources; telling whether an APK is packed or obfuscated before deeper analysis.

How do I install APK Static Analysis in Claude Code?

Run `npx skills add dslsdzc/rev-skills --skill re-apk -a claude-code`. Or copy the skill folder (.claude/skills/re-apk in dslsdzc/rev-skills) into .claude/skills/re-apk in your project. Claude Code loads it when a task matches its description.

How do I install APK Static Analysis in Codex?

Run `npx skills add dslsdzc/rev-skills --skill re-apk -a codex`. Or copy the skill folder (.claude/skills/re-apk in dslsdzc/rev-skills) into .agents/skills/re-apk in your project. Codex loads it when a task matches its description.

Can I use APK Static Analysis in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add dslsdzc/rev-skills --skill re-apk -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/re-apk, .gemini/skills/re-apk, .github/skills/re-apk and .opencode/skills/re-apk in your project.

What does APK Static Analysis need to run?

Going by SKILL.md and its folder, APK Static Analysis needs the command-line tools its instructions call (brew, adb, apt and dnf). Our summary lists: Java 11 or newer for jadx; jadx and apktool installed; Android SDK build-tools for aapt2 and apksigner.

Does APK Static Analysis access the network?

SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is APK Static Analysis safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does APK Static Analysis use?

APK Static Analysis is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does APK Static Analysis use?

About 2k tokens (SKILL.md is roughly 7.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3.3k tokens, read only when the agent opens those files.

What are the alternatives to APK Static Analysis?

Skills that share tags, products or a category with APK Static Analysis: Android APK Pentester (ptn1411/skill, 219 stars), Performing Dynamic Analysis Of Android App (mukul975/Anthropic-Cybersecurity-Skills, 34k stars), Performing Android App Static Analysis With Mobsf (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Mobile Reverse (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains APK Static Analysis?

dslsdzc (a GitHub user) maintains it in dslsdzc/rev-skills, which has 125 GitHub stars. The repository holds 41 skills in this directory. The repository was last updated on October 5, 2026.

Source: dslsdzc/rev-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.