CtrlK
BlogDocsLog inGet started
Tessl Logo

android-performance

Optimize Android app startup, UI rendering, frame stability, and benchmark performance with Baseline Profiles, Macrobenchmark, and lazy initialization. Use when reducing startup time, diagnosing jank, or measuring rendering; defer Compose state API and test-only questions.

62

Quality

74%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/android/android-performance/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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.

The body is concise and well-structured with appropriate one-level-deep references, but it lacks inline executable examples and sequenced workflows with validation checkpoints for benchmarking work. Actionability and workflow clarity are the main weaknesses.

Suggestions

Add a short inline baseline-profile/benchmark code snippet or a concrete command (e.g., ./gradlew :benchmark:connectedBaselineProfile) so guidance is executable without leaving SKILL.md.

Introduce an explicit measure -> optimize -> re-benchmark feedback loop with a validation checkpoint so workflow_clarity reflects the iterative nature of performance work.

Remove the duplicated 'See [baseline & startup](references/implementation.md)' link and the thin 'Canonical response anchors' line to tighten conciseness and navigation.

DimensionReasoningScore

Conciseness

Mostly lean bullet structure that assumes competence and avoids concept padding; minor redundancy (the nested-weights and context guidance repeats the Anti-Patterns section) and a thin 'Canonical response anchors' line could be trimmed.

4 / 5

Actionability

Concrete tools and API hints (Baseline Profiles, LazyColumn with key, .crossfade(), Coil/Glide) are named, but SKILL.md itself contains no executable code — code is deferred to references — so guidance is incomplete rather than copy-paste ready.

3 / 5

Workflow Clarity

Sections are organized by topic but there is no sequenced multi-step process or validation checkpoint (e.g., measure -> optimize -> re-benchmark) for the optimization/benchmarking tasks described.

3 / 5

Progressive Disclosure

The body keeps an overview and offloads detailed code to references/implementation.md at one level deep, clearly signaled and confirmed to exist; minor organization gaps such as duplicate 'See [baseline & startup]...' links.

4 / 5

Total

14

/

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 that clearly states capabilities and explicit use triggers in third person, with a defined niche and even out-of-scope guidance. Minor gaps in action specificity keep specificity and trigger quality just below the top anchor.

DimensionReasoningScore

Specificity

Names the Android performance domain with several concrete capabilities (startup, UI rendering, frame stability, benchmarking) and tools (Baseline Profiles, Macrobenchmark, lazy initialization), but leaves minor gaps in coverage of the listed actions.

4 / 5

Completeness

Explicitly answers both what ('Optimize Android app startup, UI rendering, frame stability, and benchmark performance...') and when ('Use when reducing startup time, diagnosing jank, or measuring rendering...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural trigger phrases like 'reducing startup time, diagnosing jank, or measuring rendering' align with what users would say, but a few common synonyms or variations are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (Android performance with Baseline Profiles, Macrobenchmark) and distinct triggers; minimal conflict risk with other skills, reinforced by the 'defer Compose state API and test-only questions' boundary.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
HoangNguyen0403/agent-skills-standard
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.