CtrlK
BlogDocsLog inGet started
Tessl Logo

compose-multiplatform-patterns

Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI.

64

Quality

76%

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/compose-multiplatform-patterns/SKILL.md

The canonical home for this skill is tdg-personal/compose-multiplatform-patterns

SKILL.md
Quality
Evals
Security

Quality

Content

80%

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

A lean, highly actionable patterns catalog with executable Kotlin examples and a useful anti-patterns list, held back only by its single-file monolithic structure and the absence of a sequenced workflow with validation checkpoints.

Suggestions

Split deeper material (e.g. performance tuning, theming customization) into one-level-deep reference files under references/ and link to them from SKILL.md to improve progressive disclosure.

For any multi-step recipe (e.g. the expect/actual platform UI setup), add an explicit ordered sequence with a validation/build checkpoint so workflow clarity can score higher.

DimensionReasoningScore

Conciseness

Lean, code-forward content that assumes Claude's competence — each section is a short pattern statement plus an executable Kotlin snippet with minimal commentary, avoiding the concept-explanation padding penalized at level 1.

3 / 3

Actionability

Provides fully executable, copy-paste-ready Kotlin examples for every pattern (ViewModel+StateFlow, type-safe navigation, slot APIs, expect/actual, @Immutable, derivedStateOf, Material 3 theming), matching the level-3 "fully executable code, specific examples" anchor.

3 / 3

Workflow Clarity

Content is organized into clear sections with a "When to Activate" trigger list and an anti-patterns section, but this is a patterns catalog rather than a sequenced multi-step workflow, so there are no ordered steps or validation checkpoints the dimension looks for.

2 / 3

Progressive Disclosure

Well-organized into labeled sections, but everything lives inline in a single ~290-line SKILL.md with no bundle files (references/scripts/assets absent); the "References" section points to sibling skills, not one-level-deep detail files, so content that could be split remains monolithic.

2 / 3

Total

10

/

12

Passed

Description

72%

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 specific, well-keyed description that clearly scopes the Compose Multiplatform/KMP UI niche, but it states capabilities as topic areas without an explicit "Use when..." trigger clause, capping completeness.

Suggestions

Add an explicit trigger clause, e.g. "Use when building Compose UI, managing UI state with ViewModels, implementing KMP/Android navigation, or optimizing recomposition performance."

Reframe capability areas as concrete actions (e.g. "manage UI state with StateFlow, implement type-safe navigation, apply Material 3 theming") to lift specificity from topic-listing to action-listing.

DimensionReasoningScore

Specificity

Names the domain (Compose Multiplatform / Jetpack Compose for KMP) and lists concrete capability areas — "state management, navigation, theming, performance, and platform-specific UI" — but frames them as topics rather than verb-based actions like the "extract, fill, merge" anchor at level 3.

2 / 3

Completeness

Clearly answers "what" (patterns for state management, navigation, theming, performance, platform-specific UI) but lacks an explicit "Use when..." trigger clause, which per the judging guidelines caps completeness at 2.

2 / 3

Trigger Term Quality

Strong natural terms a KMP/Compose user would actually say: "Compose Multiplatform", "Jetpack Compose", "KMP projects", "state management", "navigation", "theming", "performance" — matching the level-3 anchor's coverage of natural user vocabulary.

3 / 3

Distinctiveness Conflict Risk

The Compose Multiplatform / KMP UI niche is distinct and unlikely to trigger for the sibling skills it references (android-clean-architecture, kotlin-coroutines-flows), matching the level-3 "clear niche with distinct triggers" anchor.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
affaan-m/ECC
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.