Menu

Individual skill

to-android-integrate

0upvotes

Integrate MobileEasyUse into one existing Android App debug variant with automatic startup.

skills/to-android-integrate/SKILL.md

Read pinned source

Source commit 79d8da76964b67c5857cd700ea30bf12538b52d0

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 5, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
9
Repository last updated
Sep 17, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Integrate MobileEasyUse into Android

Complete the integration, report the changes, and ask whether to verify. Verification covers building, installation, launch, connection, and probing.

## Acquire the artifact

Before editing the target project, run `node scripts/ensure-artifacts.mjs`, resolving the script path relative to this `SKILL.md`. The script requires Node.js 20 or newer and works on Windows, macOS, and Linux. It:

- fetches the live compatibility catalog for the current run;
- reuses a complete matching artifact in `~/.meu`;
- otherwise downloads the Android Maven archive, verifies it against `SHA256SUMS`, and extracts it;
- prints one JSON object containing the selected Release, paths, compatible MCP range, and exact version-pinned MCP command.

If the JSON result contains `actionRequired: "confirm-update"`, report the cached and latest Release versions and ask whether to update. Run again with `--update` when accepted or `--use-cached` when declined. Preserve a Release already pinned in the project unless the user accepts an upgrade; select it with `--version <version>`.
Back to top