CtrlK
BlogDocsLog inGet started
Tessl Logo

gradle-build-performance

Debug and optimize Android/Gradle build performance. Use when builds are slow, investigating CI/CD performance, analyzing build scans, or identifying compilation bottlenecks.

70

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

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 highly actionable, well-organized skill body with executable examples throughout and a clear measurement-driven workflow. Main improvement is splitting the long inline catalog into reference files and adding explicit error-recovery loops.

Suggestions

Extract the '12 Optimization Patterns' and 'CI/CD Optimizations' sections into separate reference files (e.g. references/optimization-patterns.md) referenced one level deep from SKILL.md to improve progressive disclosure.

Add an explicit error-recovery feedback loop to the workflow (e.g. 'If configuration cache fails: inspect --scan problems, fix, re-measure') to lift workflow clarity.

Tighten a few explanatory asides such as 'KSP is 2x faster than kapt for Kotlin' and 'Composite builds are faster than project() for large monorepos' to remove minor over-explanation.

DimensionReasoningScore

Conciseness

The body is dense and mostly action-oriented with little concept padding, but a few explanatory asides (e.g. "KSP is 2x faster than kapt for Kotlin") could be trimmed.

4 / 5

Actionability

It provides copy-paste-ready gradle.properties, Kotlin DSL, and bash snippets across 12 optimization patterns plus diagnostics, covering the common cases fully.

5 / 5

Workflow Clarity

The 6-step Measure→Generate Scan→Identify→Apply ONE→Measure Improvement→Verify sequence has explicit measurement checkpoints and a verification checklist, but lacks an explicit error-recovery feedback loop.

4 / 5

Progressive Disclosure

Content is well-sectioned with clear headers and clearly listed external URL references; with no bundle files present everything is inline, so some bulk (e.g. the 12 patterns, CI/CD section) could be split into reference files.

4 / 5

Total

17

/

20

Passed

Description

87%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 strong description with explicit what/when structure and natural trigger terms in a clearly distinct niche. Minor specificity and synonym-coverage improvements could nudge it higher.

DimensionReasoningScore

Specificity

"Debug and optimize Android/Gradle build performance" names the domain plus two concrete action verbs, and the trigger clause enumerates specific scenarios; minor gaps keep it just below a comprehensive 5.

4 / 5

Completeness

It explicitly answers both what ("Debug and optimize Android/Gradle build performance") and when ("Use when builds are slow, investigating CI/CD performance, analyzing build scans, or identifying compilation bottlenecks") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Phrases like "builds are slow", "CI/CD performance", "build scans", and "compilation bottlenecks" are natural user language with good coverage, though a few common synonyms (e.g. "build times") are missing.

4 / 5

Distinctiveness Conflict Risk

The Android/Gradle build-performance niche has distinct, domain-specific triggers with minimal overlap risk against other skills.

5 / 5

Total

18

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
new-silvermoon/awesome-android-agent-skills
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.