agent-spec-mobile-react-native
Agent skill for spec-mobile-react-native - invoke with $agent-spec-mobile-react-native
40
7%
Does it follow best practices?
Impact
99%
1.16xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agents/skills/agent-spec-mobile-react-native/SKILL.mdQuality
Discovery
0%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that provides no useful information about the skill's capabilities, purpose, or when it should be selected. It only contains the skill name and invocation syntax, making it impossible for Claude to make an informed decision about when to use it among other available skills.
Suggestions
Add concrete actions describing what this skill does (e.g., 'Generates mobile app specifications for React Native projects, including component architecture, navigation structure, and platform-specific considerations').
Add an explicit 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs to create or review mobile app specs, React Native project plans, or mobile architecture documents').
Remove the invocation syntax from the description and replace with capability-focused language that helps Claude distinguish this skill from other mobile or React Native skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself ('spec-mobile-react-native') and mentions invocation syntax, with no indication of what the skill actually does. | 1 / 3 |
Completeness | Neither 'what does this do' nor 'when should Claude use it' is answered. The description only provides an invocation command with no explanation of purpose or trigger conditions. | 1 / 3 |
Trigger Term Quality | The only potentially relevant terms are 'mobile' and 'react-native' embedded in the skill name, but these are not presented as natural trigger keywords. A user asking about React Native development would not naturally match this description. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'spec' is ambiguous (specification? special?), and 'agent skill' is completely generic. Without knowing what this skill does, it could conflict with any mobile or React Native related skill. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is dominated by an enormous YAML frontmatter block that contains non-functional configuration metadata, while the actual instructional body is thin and generic. The content mostly restates things Claude already knows about React Native development without providing project-specific conventions, concrete workflows, or actionable decision trees. The single code example is a basic boilerplate component that doesn't teach anything beyond introductory React Native tutorials.
Suggestions
Remove or drastically reduce the YAML frontmatter to only essential fields; move the body focus to concrete, project-specific patterns and conventions Claude wouldn't already know.
Add clear multi-step workflows for common tasks (e.g., 'Creating a new screen', 'Adding a native module') with explicit validation steps like running the app on both platforms or checking for TypeScript errors.
Replace generic best practices bullets with specific, actionable guidance—e.g., exact FlatList optimization techniques, specific navigation stack configuration patterns, or concrete state management setup steps.
Split detailed topics (navigation setup, native modules, platform-specific code) into referenced sub-files and provide a clear overview with links in the main SKILL.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The YAML frontmatter is massively bloated with configuration that Claude doesn't use (hooks, optimization, triggers, integration metadata). The body content explains basic concepts Claude already knows ('Use functional components with hooks', 'Handle platform differences appropriately') and the component example is a generic boilerplate that adds little value. | 1 / 3 |
Actionability | The component pattern example is executable and copy-paste ready, which is good. However, the 'Key responsibilities' and 'Best practices' sections are vague bullet points ('Optimize performance and memory usage', 'Test on both iOS and Android') without concrete commands, specific techniques, or actionable guidance. | 2 / 3 |
Workflow Clarity | There is no clear multi-step workflow for any task. The skill lists responsibilities and best practices as bullet points but never sequences them into a process. There are no validation checkpoints, no error recovery steps in the body content, and no guidance on how to approach building a screen or component end-to-end. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block with no references to external files for detailed topics like navigation setup, native module integration, or platform-specific guides. Everything is dumped into one file with no clear navigation structure, and the massive YAML frontmatter dominates the file. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- ruvnet/claude-flow
- Commit
f547cec
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.