SkillAgentSearch skills...

r8-analyzer

Analyzes Android build files and R8 keep rules to identify redundancies,

Install / Use

npx skills add android/skills --skill r8-analyzer

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Universal

Tags

Our assessment of r8-analyzer

r8-analyzer scores 80/100 on our quality scale, 3607th of 4,698 Development & Engineering skills we index.

Its SKILL.md is 4.4 KB long, split into 7 sections and no code examples: a solid amount of guidance for an agent.

With 7,514 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
11/20
Description
12/15
Adoption
16/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so r8-analyzer is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-09-27. Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

r8-analyzer compared with similar skills

All 4 of these similar skills score higher than r8-analyzer; compare them before choosing.

SkillScoreStarsUpdatedFormat
r8-analyzer (this skill)by android807.5k54d agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
lobehubby lobehub10085.6ktodayMCP Server

Frequently asked questions

How do I install r8-analyzer?
Run npx skills add android/skills --skill r8-analyzer. The install tabs above show the steps for each supported agent.
Which AI agents does r8-analyzer work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is r8-analyzer safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is r8-analyzer still maintained?
The repository was last updated about 2 months ago, so r8-analyzer is actively maintained.

name: r8-analyzer description: Analyzes Android build files and R8 keep rules to identify redundancies, broad package-wide rules, and rules that subsume library consumer keep rules. Use when developers want to optimize their app's size, remove redundant or overly broad keep rules, or troubleshoot Proguard configurations. license: Complete terms in LICENSE.txt metadata: author: Google LLC last-updated: '2026-09-22' keywords:

  • R8
  • proguard
  • keep rules
  • app size
  • optimization

Step 1. Setup and configuration check

  • Inspect build.gradle, build.gradle.kts, and gradle.properties.
  • Use references/CONFIGURATION.md to identify missing optimizations.
  • AGP : If version is lower than 9.0, suggest migration to 9.0 for build-time performance improvement.
  • Full Mode : Verify android.enableR8.fullMode=false is removed from gradle.properties.

Step 2. Analysis path selection

  • Inspect build.gradle, build.gradle.kts, and gradle.properties and libs.versions.toml to get the AGP and R8 versions.

  • If AGP >= 9.3.0 : Proceed to Path A (Standalone Task).

  • If AGP < 9.3.0 and R8 >= 9.3.7-dev : Proceed to Path B (Quantitative).

  • If none of the conditions are met, proceed to Path C (Heuristic).

Path A: Standalone Gradle task (AGP >= 9.3.0)

  • Step 1: Run standalone task : Run ./gradlew :app:analyzeReleaseR8Config to evaluate the R8 configuration. You MUST wait for this command to finish before proceeding.
  • Step 2: Convert to JSON : The report is generated at app/build/reports/r8/r8-config-analyzer-release.pb. You MUST explicitly run the conversion script by executing: python3 .agents/skills/r8-analyzer/scripts/convert_pb_to_json.py. Wait for this command to finish.
  • Step 3: Analyze : You MUST explicitly run the analysis script by executing: python3 .agents/skills/r8-analyzer/scripts/analyze.py. This outputs tmp/keepradius/analysis_result.txt. Wait for this command to finish.

Path B: Quantitative data generation (R8 >= 9.3.7-dev and AGP < 9.3.0)

  • Step 1: Check requirements : Python and protobuf package are mandatory.
  • Step 2: Generate and analyze : You MUST run the shell commands described in references/CONFIGURATION-ANALYZER.md to generate the proto file using R8 configuration analyzer, convert it to JSON and analyze the result.
  • Step 3: Analyze : You MUST ensure the analysis produces tmp/keepradius/analysis_result.txt for scores and rule impact metrics.

Path C: Heuristic evaluation and recommendation (R8 < 9.3.7-dev)

(Use ONLY if quantitative data generation is not possible)

Step 3. Report generation

  • Format : Follow references/REPORT_FORMAT.md strictly.
  • Input: Extract metrics (Scores, Impacts, Example Classes) directly from generated file analysis.txt if using Path A, or from manual findings if using Path B.
  • Output : Output ONLY the raw Markdown report in the chat. Do NOT output conversational filler (for example, "Here is your report..."). Do NOT provide recommendations, next steps, or any other text outside of the sections defined in references/REPORT_FORMAT.md Do NOT mention the path used for analysis of the configuration

Constraints

  • Strict output limit: The final output MUST strictly be the Markdown report and nothing else.
  • No code changes: Research and suggest only; Do not modify files.
  • No redundancy: Do not explain R8 benefits or reference skill internal files in the report.
  • Focus: Omit sections (for example, Subsumed Rules, Configuration) if no issues or items are found.

Related Skills

View on GitHub
GitHub Stars7.5k
CategoryDevelopment
Updated1mo ago
Forks488

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions