CtrlK
BlogDocsLog inGet started
Tessl Logo

agent-spec-mobile-react-native

Agent skill for spec-mobile-react-native - invoke with $agent-spec-mobile-react-native

56

1.16x
Quality

32%

Does it follow best practices?

Impact

99%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/agent-spec-mobile-react-native/SKILL.md

The canonical home for this skill is agent-spec-mobile-react-native in ruvnet/claude-flow

SKILL.md
Quality
Evals
Security

Quality

Content

43%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content pairs one genuinely useful, executable component example with a large block of inlined agent-configuration metadata and generic best-practice reminders Claude already knows. It lacks any sequenced workflow or validation guidance for the destructive/platform-specific operations it mentions.

Suggestions

Move the agent-config YAML block (triggers/capabilities/constraints/hooks) out of the SKILL.md body into a separate referenced file so the overview stays lean.

Cut platitudes Claude already knows ('use hooks', 'test on both platforms') and replace with specific, non-obvious guidance (e.g. Metro cache invalidation, pod install ordering).

Add a short workflow with validation checkpoints for platform-specific/native-module changes, since the constraints already flag these as confirmation-required.

DimensionReasoningScore

Conciseness

The body inlines a ~140-line YAML agent-config block (triggers, capabilities, constraints, hooks) plus best-practice platitudes Claude already knows ('Use functional components with hooks', 'Test on both iOS and Android'); only the single code example earns its tokens.

2 / 5

Actionability

The 'Component patterns' section provides a complete, executable JSX example with hooks, navigation, StyleSheet and Platform.select; coverage is limited to one component pattern, leaving minor gaps.

4 / 5

Workflow Clarity

There is no real workflow — only a numbered list of responsibilities and bullet best practices — and no sequencing or validation checkpoints for risky operations like native-module or permission changes.

2 / 5

Progressive Disclosure

Section headers (## Key responsibilities, ## Component patterns, etc.) give some structure, but the large inlined YAML spec and absence of any external reference files leave organization mediocre.

3 / 5

Total

11

/

20

Passed

Description

21%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is essentially a placeholder: it restates the skill name and an invocation token without describing concrete capabilities or when to use the skill. It fails on trigger terms and completeness, and only the inherent specificity of 'React Native' keeps it from being fully generic.

Suggestions

Replace the description with concrete actions, e.g. 'Build, debug, and refactor React Native components and screens for iOS and Android.'

Add an explicit 'Use when ...' clause listing natural trigger phrases such as 'React Native app', 'Expo', 'native module', or '.tsx' mobile screens.

Include synonyms and file extensions (e.g. 'React Native, Expo, .jsx/.tsx mobile screens') to improve trigger-term coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ('spec-mobile-react-native') but provides no concrete actions at all — it only restates 'Agent skill for ... - invoke with ...', which is a tautological wrapper rather than a capability.

2 / 5

Completeness

It offers only a vague 'what' ('Agent skill for spec-mobile-react-native') and no 'when' guidance at all — the 'invoke with' clause gives usage mechanics, not a trigger condition.

2 / 5

Trigger Term Quality

There are no natural keywords a user would say; 'spec-mobile-react-native' and '$agent-spec-mobile-react-native' are a technical slug and invocation syntax, not conversational trigger phrases.

1 / 5

Distinctiveness Conflict Risk

The React Native niche is fairly specific, but the bare 'Agent skill for ...' phrasing still overlaps with general mobile/web development skills and gives no distinguishing triggers.

3 / 5

Total

8

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
ruvnet/ruflo
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.