Content
36%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.
The body is a generic React Native role description rather than a skill: it relies on knowledge Claude already has, offers one boilerplate example instead of project-specific guidance, and defines no executable workflow. The duplicated YAML config block between frontmatter and body further confuses the file's structure.
Suggestions
Replace the generic best-practice bullets with concrete, project-specific guidance (e.g. the project's navigation setup, state-management choice, exact commands to run/build/test like 'npx react-native run-ios --reset-cache').
Define an actual workflow with sequence and validation, e.g. 1. implement screen, 2. verify types with tsc, 3. run on both platforms via the project's test command, 4. only then report done.
Fix the file structure: remove the duplicated YAML frontmatter/config block so there is a single frontmatter block, and move the hooks/trigger config into clearly-signaled reference files if it is genuinely needed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body spends much of its budget on concepts Claude already knows ('Use functional components with hooks', 'Test on both iOS and Android') and a 57-line boilerplate component example, with several padded/generic bullet sections that could be cut entirely. | 2 / 5 |
Actionability | The single JSX component example is complete and executable, but the surrounding guidance is high-level hints ('Implement proper navigation (React Navigation)', 'Optimize images and assets') with no commands, configs, or concrete steps for the common cases. | 3 / 5 |
Workflow Clarity | The numbered 'Key responsibilities' is a duty list rather than a sequenced process; there is no ordered workflow for building, running, or validating a change (e.g. no run/test/verify loop), leaving many gaps and no checkpoints. | 2 / 5 |
Progressive Disclosure | The body has headed sections and is reasonably short with no bundle files, but the file is structurally malformed: a ~140-line duplicate YAML config block (triggers, capabilities, hooks) sits between the real frontmatter and the body, so overall organization is mediocre. | 3 / 5 |
Total | 10 / 20 Passed |