CtrlK
BlogDocsLog inGet started
Tessl Logo

jetpack-best-practices

USE THIS when writing or reviewing Jetpack Compose / Kotlin code in packages/cds-android or apps/android-app - @Composable APIs, Modifier parameters, CompositionLocal, state hoisting, or naming. Not for React or React Native work.

67

Quality

80%

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

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

A well-structured, concise review skill that defers detail to a vendored reference and surfaces the most-relevant rules inline. Adding brief compliant/non-compliant code examples and an explicit validation step would lift actionability and workflow clarity.

Suggestions

Add one or two short compliant-vs-noncompliant Composable code snippets to make the Modifier, naming, and parameter-ordering rules immediately executable as a review checklist.

Make the review workflow explicit with a short sequenced checklist (e.g. read guidelines → check each rule → flag violations) with a verification step that the change still compiles.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence with no padding of basic Compose concepts; minor framing prose such as 'In practice we hold close to the framework-development bar, because anything we ship publicly is expensive to change later' is justified but mildly explanatory and could be trimmed.

4 / 5

Actionability

Concrete, checkable rules (Modifier is 'the first optional parameter, defaults to Modifier… used exactly once'; parameter ordering; state hoisting) give actionable review guidance; the gap is the absence of illustrative code examples showing compliant vs non-compliant APIs.

4 / 5

Workflow Clarity

The single-purpose review process is unambiguous — read the vendored guidelines, then check the listed rules on every change — and no destructive/batch cap applies; it stops short of explicit validation checkpoints, so it does not reach 5.

4 / 5

Progressive Disclosure

A concise overview that well-signals one real one-level-deep reference (references/compose-api-guidelines.md, verified present), summarizes only the high-value rule subset inline, and defers full detail to the vendored document, making navigation easy.

5 / 5

Total

17

/

20

Passed

Description

82%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 strongly written, tightly scoped description with explicit trigger guidance and a clear negative boundary. The only real weakness is second-person imperative voice ('USE THIS'), which the rubric penalizes on specificity.

Suggestions

Rewrite in third person to avoid the voice penalty, e.g. 'For writing or reviewing Jetpack Compose / Kotlin code in packages/cds-android or apps/android-app - @Composable APIs, Modifier parameters, CompositionLocal, state hoisting, or naming. Not for React or React Native work.'

Add a couple of synonyms or file extensions (e.g. '.kt', 'Composables') to push trigger term coverage toward comprehensive.

DimensionReasoningScore

Specificity

Names the domain and several concrete concerns (@Composable APIs, Modifier parameters, CompositionLocal, state hoisting, naming, writing/reviewing), which would anchor at 4, but 'USE THIS when…' is second-person imperative voice rather than third person, so the rubric's voice penalty reduces specificity by 1.

3 / 5

Completeness

Explicitly answers what (write/review Compose APIs across the listed concerns) and when ('USE THIS when writing or reviewing Jetpack Compose / Kotlin code in packages/cds-android or apps/android-app'), with a concrete trigger phrase plus a negative boundary.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('Jetpack Compose', 'Kotlin', '@Composable APIs', 'Modifier parameters', 'CompositionLocal', 'state hoisting') that a developer would actually say, but no synonyms or file extensions to reach comprehensive coverage.

4 / 5

Distinctiveness Conflict Risk

Clear niche scoped to Compose/Kotlin in named packages, reinforced by an explicit 'Not for React or React Native work' boundary, giving minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
coinbase/cds
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.