mobile-cross
Mobile Cross-Platform Agent. React Native/Flutter를 사용한 크로스플랫폼 앱 개발을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill mobile-cross33
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/skillValidation for skill structure
Discovery
22%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 too brief and vague to effectively guide skill selection. While it mentions specific frameworks (React Native/Flutter), it fails to describe concrete capabilities and completely lacks trigger guidance for when Claude should use this skill. The Korean language description also limits discoverability for English-speaking users.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about React Native, Flutter, cross-platform mobile apps, or mentions .dart/.tsx files'
List specific concrete actions such as 'Build UI components, configure navigation, implement state management, handle platform-specific code, debug mobile apps'
Include common user terms and variations: 'mobile app', 'iOS', 'Android', 'Expo', 'cross-platform', 'hybrid app'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only states it 'handles cross-platform app development' (담당합니다) without listing any concrete actions like 'build UI components', 'configure navigation', or 'implement state management'. This is vague language about a domain. | 1 / 3 |
Completeness | The description weakly addresses 'what' (cross-platform app development) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent instruction for Claude to know when to select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant framework names 'React Native' and 'Flutter' which users would naturally mention, but lacks common variations like 'mobile app', 'iOS', 'Android', 'cross-platform', or file extensions like '.dart', '.tsx'. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of React Native and Flutter provides some distinction from general mobile or web development skills, but 'app development' is broad enough to potentially conflict with native iOS/Android skills or general frontend skills. | 2 / 3 |
Total | 6 / 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 content is essentially a role description rather than actionable guidance. It lists responsibilities and output directories but provides no concrete instructions, code examples, or workflows that would help Claude perform cross-platform mobile development tasks. The content fails to teach Claude anything it couldn't infer from the skill title alone.
Suggestions
Add executable code examples for common tasks like creating a React Native component, integrating a native module, or setting up Fastlane configuration
Define clear workflows with validation steps for key processes like 'building for production' or 'adding a native module'
Include specific commands for development tasks (e.g., `npx react-native run-android`, `flutter build apk`)
Add references to detailed documentation files for complex topics like performance optimization patterns or CI/CD setup
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is brief and doesn't over-explain concepts Claude knows, but it's so minimal that it lacks substance rather than being efficiently dense with useful information. | 2 / 3 |
Actionability | No concrete code, commands, or executable guidance provided. The content only lists responsibilities and folder locations without any specific instructions on how to perform tasks. | 1 / 3 |
Workflow Clarity | No workflows, steps, or processes are defined. The skill mentions tasks like 'native module integration' and 'CI/CD (Fastlane)' but provides no sequence or validation checkpoints for any of them. | 1 / 3 |
Progressive Disclosure | No references to detailed documentation, no links to examples or advanced guides. The content is a flat list with no structure for discovery or navigation to deeper materials. | 1 / 3 |
Total | 5 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
Total | 10 / 11 Passed | |
- 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.