mobile-android
Mobile Android Agent. Kotlin/Compose를 사용한 Android 앱 개발을 담당합니다.
Install with Tessl CLI
npx tessl i github:shaul1991/shaul-agents-plugin --skill mobile-android47
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
32%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 identifies the technology stack (Kotlin/Compose for Android) but is too brief and lacks actionable detail. It fails to specify concrete capabilities or provide explicit trigger conditions, making it difficult for Claude to know when to select this skill over others in a large skill library.
Suggestions
Add a 'Use when...' clause with trigger terms like 'Android app', 'Compose UI', 'Kotlin mobile', 'Jetpack components', or 'Android Studio'.
List specific concrete actions such as 'create Compose UI components', 'implement navigation', 'manage app state', 'handle Android lifecycle', or 'integrate APIs'.
Include common user phrases and file extensions like '.kt', 'build.gradle', 'AndroidManifest' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Android app development) and technology stack (Kotlin/Compose), but lacks specific concrete actions like 'create UI components', 'implement navigation', or 'handle state management'. | 2 / 3 |
Completeness | Only addresses 'what' (Android app development with Kotlin/Compose) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. | 1 / 3 |
Trigger Term Quality | Includes relevant keywords like 'Android', 'Kotlin', 'Compose', and '앱 개발' (app development), but missing common variations users might say like 'mobile app', 'Android Studio', 'Jetpack', or 'UI components'. | 2 / 3 |
Distinctiveness Conflict Risk | Specifies Android with Kotlin/Compose which distinguishes it from iOS or cross-platform development, but could still overlap with general mobile development or Kotlin-focused skills without clearer boundaries. | 2 / 3 |
Total | 7 / 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 is extremely concise but lacks actionable content. It functions more as a role description than a skill that teaches Claude how to perform specific tasks. The listed responsibilities (Compose UI, Room/Retrofit, Firebase, Play Store) are complex topics that need concrete examples, code snippets, and workflow guidance to be useful.
Suggestions
Add executable Kotlin/Compose code examples for common UI patterns (e.g., a basic Composable function, ViewModel setup)
Include concrete commands or steps for Firebase setup and Play Store deployment workflows with validation checkpoints
Provide specific Room database and Retrofit API configuration examples that are copy-paste ready
Add references to detailed documentation files for each major responsibility (e.g., 'See [COMPOSE_PATTERNS.md] for UI guidelines')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is extremely lean with no unnecessary explanations. Every line serves a purpose - role definition, responsibilities, and file locations. No padding or concepts Claude already knows. | 3 / 3 |
Actionability | The skill provides only vague descriptions of responsibilities (e.g., 'Jetpack Compose UI 개발') without any concrete code examples, commands, or executable guidance. It describes rather than instructs. | 1 / 3 |
Workflow Clarity | No workflow or process is defined. The skill lists responsibilities but provides no steps, sequences, or validation checkpoints for any of the mentioned tasks like Firebase integration or Play Store deployment. | 1 / 3 |
Progressive Disclosure | The content is well-organized with clear sections, but it lacks any references to detailed documentation for the complex topics mentioned (Compose patterns, Room setup, Firebase config, deployment process). | 2 / 3 |
Total | 7 / 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.