How do I install the Android Recovery skill?

Run npx skillmds@latest add samraddhashrivastavatech/android-recovery in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Android Recovery skill do?

Reconnect and self-heal devices — transport drops, offline/unauthorized states, stale ADB servers, and post-reboot recovery. Use when a device disappears, goes offline, or stops answering. It is listed under Coding & Dev Tools on SkillMD.

Is Android Recovery safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Android Recovery?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Android Recovery free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Android Recovery?

SAMRADDHASHRIVASTAVATECH (@samraddhashrivastavatech) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Android Recovery by samraddhashrivastavatech

Name: Android Recovery
Rating: 4.666666666666667 (3 reviews)
Author: SAMRADDHASHRIVASTAVATECH

File contents

Android recovery

Restore a broken or missing device session without dropping into generic troubleshooting.

When to use

Serial listed as offline, unauthorized, or connecting.
Device vanished from the list after USB/Wi-Fi events or reboots.
ADB server looks stale (misbehaving list_devices / hung transports).

Tools used

reconnect — tear down and re-establish the transport (first step).
list_devices / status — reassess the state after each action.
discover — re-scan when the device is not visible.
verify — confirm the recovered transport with a harmless probe.

Procedure

status / list_devices to classify the failure (offline? missing? unauthorized?).
Stop and think before anything destructive — recovery is escalation-ordered:
- reconnect → verify
- fail → discover + connect (authorisation prompt may appear)
- fail → check ADB server on the host; restart it only with approval.
After the transport returns, verify and re-run the capability scan that the session needs.
If a gate refuses a given action, do not try to escalate around it — report and offer the next option.

Security

reconnect / connect are transport mutations: confirm=true.
Restarting the ADB server is host-level: require explicit approval.

Related skills

android-adb · android-discovery · android-multi-device · android-control

Frequently asked questions