Content
75%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-organized index-style skill that catalogs ~30 rules across 8 prioritized categories with mostly concrete, library-specific directives, deferring details to per-rule files. It scores solidly but not top marks because the body itself has some redundancy, no executable code, and its referenced external files cannot be verified in the bundle.
Suggestions
Remove the redundancy between the priority table and the quick-reference section headers (e.g., drop the category/priority repetition by keeping one authoritative map) to tighten conciseness.
Make vague entries actionable: replace one-liners like "Organize design system imports" and "Use StyleSheet.create or Nativewind" with a concrete criterion or short example so the index alone guides the choice.
Add a short 'How to apply' sequence (identify the category by priority → locate the rule → read rules/<rule>.md before writing code) so the workflow is explicit rather than implied.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is a lean rule catalog with no concept re-teaching ("Use FlashList for large lists", "Animate only transform and opacity"), but the 'When to Apply' bullets duplicate the frontmatter description's triggers and the priority table's category/impact columns are repeated verbatim as quick-reference section headers, so minor trimming is possible. | 4 / 5 |
Actionability | Most rules are concrete directives naming specific tools ("Use FlashList", "Use expo-image for all images", "Use Galeria for image lightboxes", "Use config plugins for custom fonts"), but the body contains no executable code and a few entries are vague ("Organize design system imports"), leaving minor gaps that the deferred rule files must fill. | 4 / 5 |
Workflow Clarity | The lookup process is legible — priority table, prefixed rule names, then "Read individual rule files for detailed explanations and code examples" with example paths and a description of each rule file's structure — but there is no explicit sequence for selecting which rules apply to a task or how to apply them in order. | 4 / 5 |
Progressive Disclosure | The SKILL.md is a well-signaled index pointing one level deep to rules/<name>.md files plus a full compiled alternative ("For the complete guide with all rules expanded: AGENTS.md"), which is good structure; however, the referenced rules/ files and AGENTS.md are not present in the provided bundle to verify, and the table-vs-quick-reference duplication is a minor organization gap. | 4 / 5 |
Total | 16 / 20 Passed |