android-kotlin

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

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

46%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 content is highly actionable with complete, executable examples but suffers from significant verbosity and inlining of standard Android reference material that Claude largely already knows. It lacks a multi-step workflow with validation checkpoints and does not use progressive disclosure to split reference detail into bundle files.

Suggestions

Move large reference blocks (full build.gradle.kts, detekt.yml, CI YAML) into separate files under references/ and keep SKILL.md as an overview with one-level-deep links.

Trim boilerplate explanations and reduce code to the minimal illustrative snippets that convey the non-obvious conventions (e.g. StateFlow exposure, dispatcher injection).

Add a short sequenced workflow with validation checkpoints for common tasks like adding a feature (screen + ViewModel + Hilt module + test) including a build/test verification step.

Dimension	Reasoning	Score
Conciseness	The ~450-line body inlines extensive reference material (full Gradle config, complete ViewModel/Repository/Compose/test code blocks, CI YAML, detekt config) that mostly restates knowledge Claude already has about standard Android libraries, with little conceptual value added beyond the code itself.	2 / 5
Actionability	Provides concrete, copy-paste-ready Kotlin and YAML examples across Gradle, coroutines/Flow, Compose, sealed state, MockK/Turbine tests, CI, and lint config, with only minor gaps (e.g. missing Room DAO/Entity and Gradle versions catalog examples).	4 / 5
Workflow Clarity	Sections are organized by topic rather than as a sequenced workflow; there are no step-by-step procedures or validation checkpoints for batch/risky operations like Gradle builds or refactoring, which caps workflow clarity at 3.	3 / 5
Progressive Disclosure	No bundle files exist and the body inlines ~450 lines of reference-grade content (full configs and code templates) that clearly belongs in separate files like GRADLE.md, COMPOSE.md, or TESTING.md, with no one-level-deep references to offload detail.	2 / 5
	Total	11 / 20 Passed

Description

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

The description identifies the Android Kotlin domain and its key technologies but reads as a stack inventory rather than a statement of actions, and omits any inline 'Use when...' trigger guidance. It is clear and distinct but not comprehensive on what-when completeness.

Suggestions

Add a 'Use when...' clause to the description itself, e.g. 'Use when working on Android Kotlin source files (.kt/.kts), Gradle modules, or Compose/Hilt/Room code.'

Reframe from a library list to concrete actions, e.g. 'Builds Android apps with Jetpack Compose UIs, Hilt DI, Room data layers, and MockK unit tests.'

Include natural trigger synonyms users actually say, such as 'Android app', 'Compose screen', or 'Gradle build'.

Dimension	Reasoning	Score
Specificity	Names the domain (Android Kotlin) and lists several concrete technologies (Coroutines, Jetpack Compose, Hilt, MockK testing) but describes no actual actions the skill performs — it enumerates libraries rather than what it does.	3 / 5
Completeness	The description gives a clear 'what' (Android Kotlin development with named technologies) but provides no 'Use when...' trigger clause; the when-guidance lives only in a separate when-to-use field, so completeness is capped at 3 per the missing-trigger guidance.	3 / 5
Trigger Term Quality	Contains relevant technical keywords (Android, Kotlin, Coroutines, Jetpack Compose, Hilt, MockK) a developer would say, but lacks natural trigger phrases or synonyms a user might actually invoke the skill with.	3 / 5
Distinctiveness Conflict Risk	The bundle of Android-specific technologies (Compose, Hilt, MockK) carves a fairly distinct niche with low overlap risk against non-Android skills, though a generic Kotlin skill would overlap.	4 / 5
	Total	13 / 20 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: abc600e

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.