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 is an extremely weak description that provides virtually no useful information for skill selection. It follows a generic template pattern ('Agent skill for X - invoke with Y') without describing any capabilities, use cases, or trigger conditions. It would be nearly impossible for Claude to correctly select this skill from a pool of available skills.
Suggestions
Add concrete actions describing what this skill does, e.g., 'Generates mobile app specifications for React Native projects, defines component architecture, screen layouts, and navigation flows.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user needs to create or review specifications for React Native mobile apps, iOS/Android development plans, or mobile UI component designs.'
Include common user-facing keywords like 'mobile app', 'React Native', 'iOS', 'Android', 'mobile specification', 'app architecture' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only names itself and provides an invocation command, with no indication of what the skill actually does beyond a vague reference to 'spec-mobile-react-native'. | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no 'Use when...' clause and no explanation of capabilities. | 1 / 3 |
Trigger Term Quality | The only potentially useful keywords are 'mobile' and 'react-native' buried in the skill name, but these are not presented as natural trigger terms a user would say. There are no natural language keywords like 'build mobile app', 'React Native project', 'iOS', 'Android', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so vague that it's impossible to distinguish it from any other mobile or React Native related skill. The generic 'Agent skill for...' pattern provides no distinguishing information. | 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 mostly a generic description of React Native development that Claude already knows, padded with an enormous YAML frontmatter block full of unused configuration. The body content lacks specific workflows, validation steps, and actionable guidance beyond a single basic component template. It reads more like a job description than an operational skill file.
Suggestions
Remove or drastically reduce the YAML frontmatter to only essential fields; move the body focus to project-specific patterns, conventions, and workflows Claude wouldn't already know.
Add concrete multi-step workflows for common tasks (e.g., 'Creating a new screen: 1. Create file in screens/, 2. Add to navigation config, 3. Verify navigation works') with explicit validation checkpoints.
Replace generic best practices bullets with specific, actionable commands and code patterns unique to the project (e.g., specific state management setup, specific navigation configuration, project file structure conventions).
Add progressive disclosure by referencing separate files for detailed topics like native module integration, platform-specific setup, and navigation patterns.
| 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, and no guidance on how to approach building a screen or component from start to finish. | 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. Topics like push notifications, state management, and native modules are mentioned but never linked to deeper resources. | 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/ruflo
- Commit
398f7c2
- 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.