agentleFS
Sign inStart free
amit-nayaramit-nayar/android-adb-skill/skills/android-debug/SKILL.md

android-debug

Skill29 starsChanged 8 months agoMITView on GitHub

Debug Android issues using ./tools/android device, screenshot, app, and debug commands.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If reproducing a bug, clear logs first with ./tools/android debug clear-logs --json.

    line 11
  2. Very specific:

    Use raw adb only for diagnostics not yet covered by the command layer.

    line 20

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Debugging workflow:

  1. Collect context with ./tools/android device info --json, ./tools/android app current --json, and ./tools/android screenshot --json.
  2. If reproducing a bug, clear logs first with ./tools/android debug clear-logs --json.
  3. Collect logs with ./tools/android debug logs --json, adding --package and --level when relevant.
  4. Correlate the logs with the current screen and the user's report.
  5. Report:
    • what happened
    • the strongest evidence
    • likely root cause
    • the next debugging step

Use raw adb only for diagnostics not yet covered by the command layer.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free