Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, high-signal architecture skill: nearly every sentence encodes non-obvious project constraints or runtime failure modes that would otherwise be discovered only in production. The main improvement opportunities are a copy-paste example for the most common task (adding a screen/feature graph) and splitting the longest anti-pattern explanation into a reference file.
Suggestions
Add a short copy-paste example of the canonical feature pattern — a @Serializable route object, an EntryProviderScope<NavKey> extension graph, and a @KoinViewModel/@Module pair wired into the app root — since that is the skill's most common use case and is currently only described in prose.
Consider moving the long MultiBackstack/decorator-reuse anti-pattern paragraph into a references/ file (e.g., references/multi-backstack.md) and keeping a two-line summary in SKILL.md, both to stay within a one-screen overview and to leave room for the skill to grow.
Make the validation feedback loop more explicit for DI changes: state directly that after editing @Module(includes = [...]) wiring, KoinVerificationTest should be run and must pass before proceeding, turning the implicit checkpoint into an explicit one.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line carries project-specific knowledge Claude cannot already know (KOIN_ENTRY_POINTS, KOIN-D003, compileSafety whole-graph semantics, MultiBackstack decorator behavior, tab entry lifetime), with zero filler explaining what DI or navigation is and one tight code block. There is nothing to trim, so it matches the "every token earns its place" anchor rather than the minor-over-explanation anchor (4). | 5 / 5 |
Actionability | Guidance names exact symbols and paths (MeshtasticNavDisplay, MultiBackstack, NavigationBackHandler, DeepLinkRouter.route(), AppKoinModule.kt, Routes.kt) plus one executable startup snippet. It falls short of fully copy-paste-ready (5) because the most common task — adding a feature graph via an EntryProviderScope<NavKey> extension — is described but never shown; it is well above pseudocode-level guidance (3). | 4 / 5 |
Workflow Clarity | This is a rules/anti-pattern skill rather than a sequential workflow; each guideline is an unambiguous situation-to-do/don't mapping, and validation is named where it exists (KoinVerificationTest catches dropped includes; compileSafety catches graph errors at entry points). No explicit checkpointed sequence exists for a 5, but nothing is incoherent or validation-blind for a 3. | 4 / 5 |
Progressive Disclosure | A single-file skill (~61 body lines) with clean sections (DI / Navigation 3 / anti-patterns / reference anchors) and no buried references. It slightly exceeds the under-50-line exception for a 5, and the long decorator-reuse anti-pattern paragraph is a candidate for a reference file if the skill grows, so it fits the good-structure-with-minor-gaps anchor (4). | 4 / 5 |
Total | 17 / 20 Passed |