android-kotlin

Android Kotlin development with Coroutines, Jetpack Compose, Hilt, and MockK testing

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/android-kotlin/SKILL.md

Quality

Content

65%

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

The content is highly actionable with executable examples and clean sectioning, but it is monolithic and padded with version-pinned template dumps, and it lacks explicit verification workflows for risky operations.

Suggestions

Move large verbatim templates (build.gradle.kts, detekt.yml, the CI workflow) into reference files and link to them, keeping SKILL.md a lean overview.

Isolate version-pinned dependencies into a dedicated, clearly-labeled section so stale numbers don't dilute the core guidance.

Add explicit verification checkpoints (e.g., run ./gradlew testDebugUnitTest and detekt before proceeding) for destructive or build-affecting operations.

Dimension	Reasoning	Score
Conciseness	The body largely assumes Claude's intelligence with no concept primers, but it is padded with verbatim, version-pinned template dumps (full build.gradle.kts, CI yaml, detekt.yml) and inline version numbers that could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready Kotlin/Gradle/YAML examples across ViewModel/Flow, Compose, MockK/Turbine tests, and CI/lint config.	3 / 3
Workflow Clarity	Content is organized by topic but offers no sequenced instructional workflow or validation/feedback checkpoints for the riskier operations it touches (release minify, migrations, test runs).	2 / 3
Progressive Disclosure	It is a single well-sectioned file with no bundle files to reference, but large template reference blocks (build.gradle.kts, detekt.yml, CI yaml) are inlined where separate reference files would be appropriate.	2 / 3
	Total	9 / 12 Passed

Description

67%

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 and distinctive, naming concrete frameworks, but lacks an explicit use-when trigger and has only partial coverage of natural trigger terms.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when working on Android Kotlin files using Coroutines, Compose, Hilt, or MockK') to raise completeness.

Broaden trigger terms to include common variations users say, such as Flow, Room, MVVM, Gradle, and unit/instrumentation testing.

Dimension	Reasoning	Score
Specificity	The description names the domain plus several specific concrete capabilities ("Coroutines, Jetpack Compose, Hilt, and MockK testing"), matching the anchor for listing multiple specific actions.	3 / 3
Completeness	It clearly states what the skill does but provides no "Use when..." trigger in the description field; per guidelines a missing explicit trigger caps completeness at 2.	2 / 3
Trigger Term Quality	It includes natural terms like "Coroutines", "Jetpack Compose", "Hilt", and "MockK testing", but omits common variations users would say (e.g. Flow, Room, Gradle, MVVM, testing), so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The Android Kotlin niche combined with specific frameworks makes it clearly distinguishable and unlikely to trigger the wrong skill.	3 / 3
	Total	10 / 12 Passed

Validation

93%

Warnings & errors only

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

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: alinaqi/claude-bootstrap
Path: skills/android-kotlin/SKILL.md
Commit: bb6195f

Reviewed: 6 days ago

Table of Contents

Discovery Implementation Validation

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.