r8-analyzer
Analyzes Android build files and R8 keep rules to identify redundancies,
Install / Use
npx skills add android/skills --skill r8-analyzerInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
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.
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 foundOur 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.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| r8-analyzer (this skill)by android | 80 | 7.5k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
| lobehubby lobehub | 100 | 85.6k | today | MCP 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.
Skill content
View source on GitHubname: 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, andgradle.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=falseis removed from gradle.properties.
Step 2. Analysis path selection
-
Inspect
build.gradle,build.gradle.kts, andgradle.propertiesandlibs.versions.tomlto 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:analyzeReleaseR8Configto 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 outputstmp/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
protobufpackage 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.txtfor 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 1: Manual evaluation : Inspect
proguard-rules.pro. - Step 2: Library check : Compare rules against references/REDUNDANT-RULES.md. Suggest Remove for bundled rules.
- Step 3: Custom rule check : Use references/KEEP-RULES-IMPACT-HIERARCHY.md and references/REFLECTION-GUIDE.md to prioritize and evaluate. Suggest Refine for broad rules (for example, package-wide).
- Step 4: Validation : Suggest Macrobenchmark tests using UI Automator for any proposed changes. Proceed to Step 3.
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
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
lobehub
85.6k🤯 LobeHub - Super-Agents on Your Team. Add super-agents to the chats your team already uses.They take on work by themselves and get better every week.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
