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.

69

Quality

86%

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

72%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a well-structured, action-oriented overview with an executable one-level-deep reference, but it lacks an explicit benchmark validation loop and carries minor redundancy (repeated anti-patterns, a stub anchors line). Tightening these would raise conciseness and workflow clarity.

Suggestions

Remove the duplicate 'Anti-Patterns' bullets and the empty 'Canonical response anchors' stub, or fill the stub with real task-grounded anchors, to remove redundancy.

Add an explicit measure-optimize-re-measure workflow with Macrobenchmark validation checkpoints (e.g., run baseline, apply fix, re-benchmark, confirm improvement) so benchmarking has a feedback loop.

Inline one short executable snippet (e.g., a Macrobenchmark config or BaselineProfile rule) directly in the body rather than relying entirely on the reference file.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but the 'Anti-Patterns' section repeats two bullets already stated in section 3 and the stub line 'Additional task-grounded exact anchors: Baseline Profile' adds no value, so it is mostly efficient with minor padding.

2 / 3

Actionability

Directives name exact APIs and tools (Baseline Profiles, App Startup, ConstraintLayout, LazyColumn with key) and point to references/implementation.md, which contains fully executable Kotlin; this is concrete and copy-paste ready rather than vague or pseudocode.

3 / 3

Workflow Clarity

Sections are prioritized and numbered (P1, 1-3), giving a sequence, but there is no measure-optimize-re-measure validation loop for benchmarking work, so checkpoints are missing per the destructive/batch-operation guideline.

2 / 3

Progressive Disclosure

The body is a concise overview that links clearly to references/implementation.md (a real, one-level-deep file) for code, keeping detail appropriately separated; navigation is easy despite a slightly redundant References section.

3 / 3

Total

10

/

12

Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete, naming concrete capabilities and explicit use-conditions with a clear Android-performance niche. It also usefully defers out-of-scope topics (Compose state API, test-only questions).

DimensionReasoningScore

Specificity

Lists multiple concrete actions across 'startup, UI rendering, frame stability, and benchmark performance' with named tools (Baseline Profiles, Macrobenchmark, lazy initialization), matching the multi-action anchor rather than the partial score-2 anchor.

3 / 3

Completeness

Explicitly states what it does (optimize startup/rendering/frame stability/benchmarking) and when to use it via a clear 'Use when...' clause, satisfying both halves rather than leaving 'when' implied.

3 / 3

Trigger Term Quality

'Use when reducing startup time, diagnosing jank, or measuring rendering' provides natural phrases users would say, with accurate technical triggers (Baseline Profiles, Macrobenchmark); coverage is broad, not missing common variations.

3 / 3

Distinctiveness Conflict Risk

The Android-performance niche with Baseline Profiles and Macrobenchmark triggers is distinct and unlikely to fire for unrelated skills, matching the clear-niche anchor.

3 / 3

Total

12

/

12

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.