CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-artisan

Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish. Use this skill to extract hardcoded styles to AppTheme, add TalkBack semantics, implement AnimatedVisibility or micro-animations, extract stateless Composables, and add @Preview annotations.

70

Quality

85%

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.

The body is a well-structured, actionable instruction skill with concrete gradle commands and Compose examples plus a clear workflow with validation and an approval gate. The main gaps are minor trimming of persona/philosophy padding and an explicit verification-failure feedback loop.

Suggestions

Drop the 'Philosophy' aphorisms and the 'You are The Artisan 🎨' persona line — they consume tokens without adding executable guidance.

Add an explicit feedback loop to the VERIFY step, e.g. 'If lint/test/ktfmt fails, fix the reported issues and re-run before creating the PR.'

Tighten the OBSERVE bullets into a compact checklist so the discovery criteria read as a scannable rubric rather than prose.

DimensionReasoningScore

Conciseness

Mostly lean and assumes Claude's competence, but the 'Philosophy' aphorisms ('Good UX is invisible; it just works.') and the persona framing ('You are "The Artisan" 🎨') are minor padding that could be trimmed; not verbose enough to drop to 3.

4 / 5

Actionability

Provides concrete commands (`./gradlew ktfmtFormat`, `./gradlew lintDebug`, `./gradlew testDebugUnitTest`) and concrete code-ish examples (`AnimatedVisibility(enter = fadeIn(), exit = fadeOut())`, `MaterialTheme.spacing.medium`, `48.dp`), but examples are illustrative rather than fully copy-paste-ready snippets.

4 / 5

Workflow Clarity

Clear five-step sequence (OBSERVE → SELECT & PROPOSE → CRAFT → VERIFY → PRESENT) with an explicit approval gate and a VERIFY checkpoint running three gradle tasks; minor gap is the absence of an explicit 'if verification fails, fix and re-run' feedback loop.

4 / 5

Progressive Disclosure

A single ~50-line file with no need for external references, organized into clear sections (Goal, Constraints, Instructions, Examples); per the simple-skill exception this earns a 5 with well-organized sections alone.

5 / 5

Total

17

/

20

Passed

Description

92%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 is third-person, specific, and explicitly pairs a clear 'what' with a concrete 'Use this skill to...' trigger clause. It is comprehensive and distinctive, with only minor room to add synonym trigger terms.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'extract hardcoded styles to AppTheme, add TalkBack semantics, implement AnimatedVisibility or micro-animations, extract stateless Composables, and add @Preview annotations' — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both: what ('Elevates the Jetpack Compose user interface through micro-UX improvements, animations, accessibility (a11y) fixes, and UI structural polish') and when ('Use this skill to extract hardcoded styles to AppTheme, add TalkBack semantics...').

5 / 5

Trigger Term Quality

Strong natural domain terms a Compose developer would say ('TalkBack semantics', 'AnimatedVisibility', '@Preview', 'AppTheme', 'Jetpack Compose'), but a few natural synonyms/variations (e.g. 'Material Design', 'Compose UI', 'UI polish') are absent, so it is not fully comprehensive.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Jetpack Compose frontend polish — with distinct triggers (TalkBack, AnimatedVisibility, @Preview, AppTheme) that minimize overlap with other skills.

5 / 5

Total

19

/

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
nekomangaorg/Neko
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.