CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

compose-multiplatform-patterns

Compose Multiplatform and Jetpack Compose patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI. Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project.

Quality

81%

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-5

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

Excellent actionable content: concrete, executable Kotlin patterns covering state, navigation, design, platform specifics, performance, and theming, plus an explicit anti-patterns section. Weaknesses are structural — no workflow/decision sequencing for choosing patterns, and no progressive disclosure since everything is inlined in SKILL.md with no reference files.

Suggestions

Add a short decision guide (e.g., when to use the event sink pattern vs. multiple callback lambdas, when expect/actual vs. a multiplatform library) so the reference doubles as a selection workflow.

Split the performance and KMP platform-specific UI sections into one-level-deep reference files (e.g., references/performance.md, references/platform-ui.md) to reduce inline SKILL.md size.

Remove or trim the 'When to Activate' section, which duplicates the frontmatter description.

DimensionReasoningScore

Conciseness

The body is code-forward with minimal prose and assumes Compose competence, but the 'When to Activate' section duplicates the frontmatter description and a few explanatory comments could be trimmed — anchor 4 rather than 5.

4 / 5

Actionability

Every section provides idiomatic, copy-paste-ready Kotlin (ViewModel + StateFlow, event sink, type-safe navigation, slot APIs, expect/actual, @Immutable, key(), derivedStateOf, Material 3 theming) including a BAD/GOOD contrast for allocation in recomposition, covering the common cases fully — anchor 5.

5 / 5

Workflow Clarity

This is a pattern reference with no multi-step sequence: sections are independent patterns with no decision guide for choosing among them and no validation checkpoints, though it contains no destructive or batch operations. It matches anchor 3 and does not qualify for the simple-skill exception (over 50 lines, multiple tasks).

3 / 5

Progressive Disclosure

No bundle files exist and all content is inline in SKILL.md; the ~300 lines are well-sectioned, but performance and platform-specific UI material could live in one-level-deep reference files, and the 'References' section points to other skills rather than navigable bundle files — anchor 3.

3 / 5

Total

15

/

20

Passed

Description

83%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: it names a clear niche, enumerates concrete capability areas, and includes an explicit and specific 'Use when' trigger clause scoped to KMP projects. The only weaknesses are topic-noun phrasing of capabilities and a few missing natural synonyms (Compose Desktop, recomposition).

DimensionReasoningScore

Specificity

Names the domain and five concrete capability areas ("state management, navigation, theming, performance, and platform-specific UI"), matching the several-specific-actions anchor; it falls short of 5 because capabilities are topic nouns rather than explicit actions (e.g., "manages UI state with ViewModels").

4 / 5

Completeness

Explicitly answers both what ("patterns for KMP projects — state management, navigation, theming, performance, and platform-specific UI") and when ("Use when building Compose or Jetpack Compose UI, state, navigation, or theming in a KMP project") with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Good coverage of natural terms a user would say ("Compose Multiplatform", "Jetpack Compose", "KMP", "UI", "state", "navigation", "theming") but missing common variations like "Compose Desktop", "recomposition", or "Kotlin Multiplatform" spelled out, so it matches anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

Clear Compose/KMP niche with distinct triggers, but "building Compose or Jetpack Compose UI" would also fire for pure Android Compose work, giving minor overlap risk with a closely related Android-only skill — anchor 4 rather than 5.

4 / 5

Total

17

/

20

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

affaan-m/ECC

Path

skills/compose-multiplatform-patterns/SKILL.md

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.