frb-android-emulator-prepare

Use when preparing, installing, diagnosing, or explaining the host Android Emulator environment for flutter_rust_bridge local runtime validation, including Android SDK command-line tools, emulator packages, AVD creation, host emulator startup, and Docker-local ADB connectivity to the emulator TCP endpoint.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

75%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.

A highly actionable, well-sequenced emulator-preparation skill with copy-paste commands and explicit verification gates that satisfy the destructive-operation validation requirement. The main weakness is conciseness: repeated inline Android Developers URL citations and tool re-descriptions across several sections could be consolidated.

Suggestions

Consolidate the Android Developers documentation URLs into the single Preflight references list and stop re-citing them inline in each Install/Create/Start section to improve conciseness.

Move the long command-line-tools install block and sdkmanager/avdmanager command blocks into a reference script or references file, keeping SKILL.md as a lean overview that points to them.

Promote workflow clarity to 5 by adding an inline validate-fix-retry loop at the Start And Verify step (e.g., 'If adb devices -l does not show emulator-5554, re-check the emulator start command, then retry') instead of relying on the separate Common Failures section.

Dimension	Reasoning	Score
Conciseness	The core command listings are tight and assume Claude's competence, but the Android Developers doc URLs and tool descriptions ('documented by Android Developers at https://...') are re-cited inline in several sections (Installation, Emulator Packages, Create AVD, Start And Verify), which is trimmable padding.	3 / 5
Actionability	Provides fully executable, copy-paste-ready bash commands throughout (preflight checks, brew install, curl/ditto, sdkmanager, avdmanager, emulator start, adb verify) with specific flags, real paths, and fallbacks like 'avdmanager list device'.	5 / 5
Workflow Clarity	Clear sequenced sections from Preflight through Cleanup with explicit verification checkpoints ('Verify host ADB can see the emulator', 'Only after both ADB checks pass, run an FRB Android runtime command') that satisfy the destructive/batch validation requirement; falls short of 5 because error recovery lives in a separate 'Common Failures' section rather than inline validate-fix-retry loops at each step.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and one-level-deep external URL references consolidated in a Preflight list; falls short of 5 because no bundle files exist, the inline URL citations are repeated across sections rather than referenced once, and some long install command blocks could be split into reference files.	4 / 5
	Total	16 / 20 Passed

Description

92%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.

A strong, specific description with an explicit 'Use when...' trigger and a comprehensive enumeration of concrete capabilities across the full emulator-preparation workflow. Third-person voice is maintained; the only minor gap is synonym/variation coverage in trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and lists multiple concrete actions ('preparing, installing, diagnosing, or explaining') plus concrete objects ('Android SDK command-line tools, emulator packages, AVD creation, host emulator startup, and Docker-local ADB connectivity to the emulator TCP endpoint'), giving comprehensive coverage of the full workflow.	5 / 5
Completeness	Explicitly answers both 'what' (prepare/install/diagnose/explain the host Android Emulator environment for FRB runtime validation, with enumerated capabilities) and 'when' (leads with an explicit 'Use when...' trigger clause) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good keyword coverage with natural terms users would say ('Android Emulator', 'Android SDK', 'AVD', 'ADB', 'emulator', 'diagnosing'), but missing some common synonyms/variations (e.g., 'virtual device', file-extension-style terms) that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	Clear narrow niche ('host Android Emulator environment for flutter_rust_bridge local runtime validation' with specific triggers like Docker-local ADB and emulator TCP endpoint) makes it highly distinct with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: fzyzcjy/flutter_rust_bridge
Path: .claude/skills/frb-android-emulator-prepare/SKILL.md
Commit: 8f2ab1b

Reviewed: ~2 hours ago

Table of Contents

Discovery Implementation Validation

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.