CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

java-memory-leaks

How to identify and fix Java memory leaks in Android Chrome using LeakCanary traces.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

—

The risk profile of this skill

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable skill body: concrete commands, Chromium-specific class names, and complete code examples covering the common leak-fix patterns, organized in a clear verified workflow. The only improvements are trimming a few Claude-known explanations and making the post-fix retry loop explicit.

DimensionReasoningScore

Conciseness

The body is efficient and assumes domain competence, but a few passages explain concepts Claude already knows, e.g. "Inner classes (especially anonymous ones) holding implicit references to the outer class", and the pattern descriptions could be tightened slightly. Not verbose enough for a 3; leaner than the anchor-4 "minor instances of over-explanation".

4 / 5

Actionability

Guidance is fully executable: copy-paste ready build/test commands ("autoninja -C out/Debug chrome_public_test_apk", "out/Debug/bin/run_chrome_public_test_apk --enable-leak-checks -f \"YourLeakTest*\""), a concrete trybot footer, and complete Java before/after examples covering the common fix patterns.

5 / 5

Workflow Clarity

The 5-step workflow (Confirm, Analyze, Identify Break Point, Apply Fix, Verify) is clearly sequenced with an explicit verification step and concrete commands, but there is no explicit feedback loop instructing what to do if LeakCanary still reports the leak after the fix, which keeps it below the anchor-5 example.

4 / 5

Progressive Disclosure

With no bundle files present, the single SKILL.md is well-organized into Workflow, Best Practices & Gotchas, and Examples sections that are easy to navigate. The ~40-line before/after Examples section could arguably live in a separate reference file, a minor organization gap consistent with anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

70%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 specific, distinctive description that clearly names the domain, tool, and actions, but it omits any explicit "Use when..." trigger guidance, which both caps completeness and limits natural trigger coverage. Adding a trigger clause and a few synonyms (e.g., LeakCanary, memory leak, OOM) would raise it to the top band.

Suggestions

Add an explicit trigger clause, e.g. "Use when LeakCanary reports a leak in an instrumentation test or when the user mentions a Java memory leak in Android Chrome."

Include a couple of natural synonyms or related terms users might say, such as "OOM", "heap retention", or "activity leak", to broaden trigger matching.

Optionally mention the debugging/verification half of the workflow (analyzing leak traces, verifying fixes) so the action coverage is more comprehensive.

DimensionReasoningScore

Specificity

The description states two concrete actions ("identify and fix Java memory leaks") with a named tool ("LeakCanary traces") and platform ("Android Chrome"), which is more specific than the two-action anchor-3 example, but it does not enumerate several actions as required for a 5.

4 / 5

Completeness

The "what" is clear (identify and fix Java memory leaks using LeakCanary traces), but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user would say in this context ("Java memory leaks", "Android Chrome", "LeakCanary"), but misses common variations and synonyms such as "OOM", "heap", "memory pressure", or "activity leak".

4 / 5

Distinctiveness Conflict Risk

"Java memory leaks in Android Chrome using LeakCanary traces" carves out a very specific niche with distinct trigger terms; conflict risk with other skills is minimal.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

chromium/chromium

Path

agents/skills/java-memory-leaks/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.