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

88%

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

77%

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

The body is highly actionable with a well-sequenced, validated workflow and good error-recovery guidance, but it carries redundant doc-URL prose and is monolithic with no progressive-disclosure structure. Tightening the repeated references and optionally splitting detail into reference files would raise the weaker dimensions.

Suggestions

Remove the repeated "documented by Android Developers at <url>" clauses in each Install/AVD/Emulator/ADB section since the official URLs are already consolidated in the Preflight references list; cite the tool name only.

Introduce progressive disclosure by moving the long install command blocks and/or the Common Failures catalog into references/ files (e.g. references/install.md, references/troubleshooting.md) and linking one level deep from SKILL.md.

Trim explanatory asides about what each tool is (e.g. "avdmanager, the Android Developers command-line tool for creating and managing AVDs") since Claude can infer their purpose from context.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and command-oriented, but includes repeatable prose padding — each section restates a doc URL already enumerated in Preflight (e.g. "the Android SDK package manager documented by Android Developers at https://developer.android.com/tools/sdkmanager") and explains what sdkmanager/avdmanager/ADB are, which Claude can infer; matches the score-2 anchor of mostly efficient with some unnecessary explanation.	2 / 3
Actionability	Provides fully executable, copy-paste-ready bash for every phase (preflight probes, brew openjdk, curl/ditto cmdline-tools install, sdkmanager licenses+packages, avdmanager create, emulator start, adb devices, cleanup), matching the score-3 anchor of fully executable commands with specific examples.	3 / 3
Workflow Clarity	A clearly sequenced Preflight → Java → cmdline-tools → packages → AVD → start/verify → test → cleanup flow with explicit validation checkpoints ("Run these before installing anything", "Verify host ADB can see the emulator", "Only after both ADB checks pass, run an FRB Android runtime command") and a Common Failures feedback loop, matching the score-3 anchor.	3 / 3
Progressive Disclosure	No bundle files exist and all content lives in one ~150-line monolithic SKILL.md with no one-level-deep references for detail that could be split out (e.g. install commands, Common Failures); sections are well-organized but the inline bulk fits the score-2 anchor of structure present yet content that could be separate is inline.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 concrete, trigger-explicit, and tightly scoped to a distinct niche; it answers both what and when without vague fluff. No changes needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ("preparing, installing, diagnosing, or explaining") plus concrete artifacts ("Android SDK command-line tools, emulator packages, AVD creation, host emulator startup, and Docker-local ADB connectivity to the emulator TCP endpoint"), matching the score-3 anchor of multiple specific concrete actions.	3 / 3
Completeness	Explicit "Use when ..." trigger answers when, and the enumerated scope (prepare/install/diagnose/explain plus the listed components) answers what, matching the score-3 anchor that clearly answers both what AND when with explicit triggers.	3 / 3
Trigger Term Quality	Natural terms a user would say for this need are present ("Android Emulator", "AVD", "ADB", "emulator packages", "Android SDK command-line tools"); the niche jargon ("flutter_rust_bridge local runtime validation") is the actual vocabulary for this domain rather than generic filler.	3 / 3
Distinctiveness Conflict Risk	The narrow FRB-specific host-emulator niche with its distinct triggers (AVD creation, Docker-local ADB to emulator TCP endpoint) is unlikely to fire for unrelated skills, matching the score-3 clear-niche anchor.	3 / 3
	Total	12 / 12 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: 1d5348b

Reviewed: 4 days 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.