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 non-functional as a skill selector. It provides only an invocation command and a name, with zero information about what the skill does, what capabilities it offers, or when it should be used. Claude would have no meaningful basis for selecting this skill over any other.
Suggestions
Add a clear 'what' clause describing concrete actions, 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 asks about React Native app specs, mobile app architecture, React Native project planning, or mobile UI specifications.'
Remove the invocation syntax from the description (it's metadata, not a capability description) and replace with domain-specific keywords like 'React Native', 'mobile app', 'specification', 'component design', etc.
| 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 mobile development would not naturally match this description. | 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 word 'spec' is ambiguous—it could mean specification, testing, or something else entirely. | 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 excessively large YAML frontmatter full of configuration fields that don't translate to actionable guidance for Claude. The body content is thin, consisting mostly of generic best practices Claude already knows and a single basic component example. It lacks concrete workflows, validation steps, specific commands for common tasks, and any progressive disclosure structure.
Suggestions
Remove or drastically reduce the YAML frontmatter bloat (hooks, triggers, optimization, examples sections) and move actionable content into the body instead.
Add concrete, sequenced workflows for common tasks like project setup, adding a new screen, integrating a native module, and building/testing on each platform, with explicit validation checkpoints.
Replace the generic 'Best practices' bullet list with specific, executable patterns (e.g., concrete navigation setup code, state management example, platform-specific permission handling).
Split detailed topics (navigation patterns, native modules, platform-specific setup) into referenced files and provide a clear overview with links in the main skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The YAML frontmatter is massively bloated with configuration that Claude doesn't use (hooks, triggers, optimization settings, metadata, examples in YAML). 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 is executable JSX code which is good, but the 'Key responsibilities' and 'Best practices' sections are vague bullet points rather than concrete instructions. There are no specific commands for project setup, no concrete examples of navigation implementation, native module integration, or state management patterns beyond the basic component. | 2 / 3 |
Workflow Clarity | There is no clear workflow or sequenced process for any task. The content is a list of responsibilities and a single component example with no validation steps, no build/test sequence, and no error recovery guidance in the body content. For mobile development involving platform-specific builds and native modules, this lack of workflow is a significant gap. | 1 / 3 |
Progressive Disclosure | The content is a monolithic mix of an enormous YAML frontmatter and a flat body with no references to external files. Platform-specific considerations, navigation patterns, state management, and native module integration could all be separate referenced documents. Everything is either superficially mentioned inline or missing entirely. | 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
ccb062f
- 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.