Content
85%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 well-structured, actionable skill with an explicit workflow, validation checkpoints, and clear guardrails (ask-first/never-do lists). Its main weaknesses are motivational Philosophy padding and the absence of a concrete Kotlin test code example illustrating the MockK/runTest pattern it mandates.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The constraints and instructions are lean and assume Claude's competence, but the four 'Philosophy' bullets ('Untested code is broken code', 'A failing test is a feature, not a bug') are motivational padding that could be trimmed, fitting the minor-over-explanation anchor. | 4 / 5 |
Actionability | Concrete executable commands ('./gradlew ktfmtFormat', './gradlew testDebugUnitTest --tests "YourTestClass"'), a test-naming convention example, and a PR title format are given, but no actual Kotlin test snippet shows the mandated runTest/MockK pattern — a minor gap. | 4 / 5 |
Workflow Clarity | A clear five-step sequence (SCAN, SELECT & PROPOSE, BUILD, VERIFY, PRESENT) with an explicit user-approval checkpoint and a real validation feedback loop: format, run the specific test class, and verify the test fails when production behavior is temporarily inverted (mutation-check) then passes when restored. | 5 / 5 |
Progressive Disclosure | The ~46-line body is well-organized into Goal/Constraints/Instructions/Examples with no external reference files needed; the only referenced file (the journal) is a clearly signaled runtime path one level deep, which satisfies the simple-skill exception. | 5 / 5 |
Total | 18 / 20 Passed |