CtrlK
BlogDocsLog inGet started
Tessl Logo

frontend-maestro

Orchestrates macro-level UI architecture, complex Jetpack Compose structures, and screen-to-screen flows. Use this skill to implement adaptive layouts (WindowSizeClass), migrate to type-safe Navigation Compose graphs, design cross-module Design Systems, wire complex screen-level state (MVI/MVVM), or orchestrate deep links and multi-screen workflows.

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

75%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 a well-structured, actionable orchestration playbook with concrete gradle commands and named Compose APIs. Its main gaps are a small block of generic philosophy padding and the absence of an explicit error-recovery loop and copy-paste code in the verify/orchestrate steps.

Suggestions

Drop the "Philosophy" truisms (e.g., "A screen is just a function of its state") that Claude already knows; keep only team-specific guidance like the journaling rules.

Add an explicit feedback loop to VERIFY: "If lintDebug or testDebugUnitTest fail, fix the reported issues and re-run before proceeding to the PR."

Include a minimal executable snippet (e.g., a type-safe kotlinx.serialization NavKey route or a WindowSizeClass adaptive branch) so the orchestration guidance is copy-paste ready.

DimensionReasoningScore

Conciseness

The body is mostly lean and actionable, but the "Philosophy" bullets ("A screen is just a function of its state", "State hoisting is the bedrock of reusable UI") restate Compose truisms Claude already knows.

4 / 5

Actionability

Concrete commands (./gradlew ktfmtFormat, lintDebug, testDebugUnitTest) and named APIs (WindowSizeClass Compact/Medium/Expanded, 800.dp cap, rememberViewModelStoreNavEntryDecorator, kotlinx.serialization NavKey) give mostly executable guidance, though no copy-paste Compose code snippet is included.

4 / 5

Workflow Clarity

PROFILE → SELECT & PROPOSE (await approval) → ORCHESTRATE → VERIFY → PRESENT is clearly sequenced with gradle-based validation gates, but the VERIFY step lacks an explicit validate→fix→retry feedback loop for failing tests or lint.

4 / 5

Progressive Disclosure

Well-organized into Goal, Constraints, Instructions, and Examples with no nested references and no bundle files to navigate; slightly above the simple-skill line with all content inline, though nothing clearly warrants a separate file.

4 / 5

Total

16

/

20

Passed

Description

96%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 specific, third-person, and explicitly pairs concrete capabilities with natural trigger phrases, hitting the what/when requirement cleanly. Its only soft spot is minor overlap risk with adjacent design-system or state-management skills.

DimensionReasoningScore

Specificity

Lists five concrete, technology-specific actions — "implement adaptive layouts (WindowSizeClass)", "migrate to type-safe Navigation Compose graphs", "design cross-module Design Systems", "wire complex screen-level state (MVI/MVVM)", "orchestrate deep links and multi-screen workflows" — giving comprehensive coverage of the skill's capabilities.

5 / 5

Completeness

Explicitly answers both "what" ("Orchestrates macro-level UI architecture, complex Jetpack Compose structures, and screen-to-screen flows") and "when" ("Use this skill to implement ... migrate ... design ... wire ... or orchestrate ...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural developer-facing terms (adaptive layouts, WindowSizeClass, type-safe Navigation Compose, Design Systems, deep links) plus synonyms (MVI/MVVM) align with phrases a user would actually say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Carves a clear macro-architecture niche and even implicitly separates from micro-UX work, but "design cross-module Design Systems" and "MVI/MVVM" state wording could overlap with a dedicated design-system or state-management skill.

4 / 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.