agent-spec-mobile-react-native
Agent skill for spec-mobile-react-native - invoke with $agent-spec-mobile-react-native
Install with Tessl CLI
npx tessl i github:ruvnet/claude-flow --skill agent-spec-mobile-react-native47
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillEvaluation — 99%
↑ 1.16xAgent success when using this skill
Validation for skill structure
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 critically deficient across all dimensions. It functions only as a label and invocation reference, providing zero information about the skill's capabilities, use cases, or trigger conditions. Claude would have no basis for selecting this skill appropriately from a list of available skills.
Suggestions
Add concrete actions describing what the skill does (e.g., 'Generates mobile app specifications for React Native projects, creates component architecture diagrams, defines API contracts').
Include a 'Use when...' clause with natural trigger terms (e.g., 'Use when the user needs React Native specs, mobile app architecture, iOS/Android specifications, or component documentation').
Add file type or domain keywords users would naturally mention (e.g., 'React Native', 'mobile development', 'app specification', '.tsx', 'cross-platform').
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions whatsoever. It only mentions 'Agent skill for spec-mobile-react-native' and an invocation command, with no explanation of what the skill actually does. | 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 terms present are technical identifiers ('spec-mobile-react-native', '$agent-spec-mobile-react-native'). No natural keywords a user would say like 'mobile app', 'React Native', 'iOS', 'Android', or 'specification' are included. | 1 / 3 |
Distinctiveness Conflict Risk | While the name 'spec-mobile-react-native' hints at a specific domain, the description provides no distinguishing details. Without knowing what it does, it's impossible to differentiate it from other mobile or React Native related skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
37%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a basic React Native component template and high-level guidance but lacks the concrete, actionable workflows needed for effective mobile development. The content reads more like a role description than executable instructions, with generic best practices Claude already knows and missing step-by-step processes for common tasks like building, debugging, or platform-specific setup.
Suggestions
Add concrete step-by-step workflows for common tasks: project setup, building for iOS/Android, debugging metro bundler issues, and deploying to devices
Replace generic best practices bullets with specific commands and code snippets (e.g., exact navigation setup code, state management patterns with Redux Toolkit)
Include validation checkpoints in workflows, especially for native module integration and platform-specific builds (e.g., 'Run `npx react-native run-ios` and verify app launches before proceeding')
Add references to separate files for platform-specific guides (iOS permissions, Android manifest configuration) rather than brief mentions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary explanation like 'You are a React Native Mobile Developer' and generic best practices that Claude already knows. The component example is useful but could be more targeted. | 2 / 3 |
Actionability | Provides one concrete code example with a component pattern, but the guidance is mostly high-level bullet points ('Use functional components with hooks', 'Implement proper navigation'). Missing specific commands for common tasks like setup, debugging, or building. | 2 / 3 |
Workflow Clarity | No clear multi-step workflows for common React Native tasks. The 'Key responsibilities' and 'Best practices' are lists without sequencing or validation checkpoints. Missing workflows for building, testing, or deploying to either platform. | 1 / 3 |
Progressive Disclosure | Content is reasonably organized with clear sections, but everything is inline in one file. The YAML frontmatter references other agents (spec-mobile-ios, spec-mobile-android) but the body doesn't provide navigation to detailed guides for platform-specific concerns or advanced topics. | 2 / 3 |
Total | 7 / 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.
- 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.