Content
88%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.
An exemplary workflow-focused skill body: concrete, copy-paste-ready commands, well-sequenced steps with real validation and fallback paths, and clean delegation of bulk detail to reference files. The only deductions are minor redundancy in the Notes section and references that live outside the skill bundle itself.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with task-specific instruction and explains no general concepts, but the Notes section restates rules already given inline (PDF/pen placeholder handling) and a few passages — the OS-opener commentary and the untouched-template detection wording — could be trimmed. | 4 / 5 |
Actionability | Guidance is fully executable throughout: exact glob/grep patterns, a copy-paste bash opener chain with fallbacks, concrete conversion examples ('p="$4"' → 'padding:16px', YStack → styled div), and exact output message formats covering the common cases. | 5 / 5 |
Workflow Clarity | Seven clearly sequenced steps with explicit validation and error recovery: Step 1 validates the project and stops on failure, Step 2 includes read-to-check verification of ambiguous screens, and Step 7 specifies fallback behavior and honest failure reporting when auto-open fails. | 5 / 5 |
Progressive Disclosure | The body appropriately delegates the mapping table, component recipes, and screen templates to three clearly-signaled one-level-deep references with a mandatory read in Step 3. However, all references resolve to plugin-level shared paths ('../../shared/references/…', '${PLUGIN_ROOT}/…') outside the skill's own bundle, with no local references/ directory, a minor organization and portability gap. | 4 / 5 |
Total | 18 / 20 Passed |