[Feature] 'android skills' command failure due to conflict with deprecated SDK tool

### What is the gap in the LLM's knowledge?
Currently, when an AI Agent (or a user) tries to initialize the environment using the instructions in the README, it often fails because the android command name is shared with the legacy/deprecated Android SDK tool.

The LLM does not currently know how to:

1. Diagnose the conflict: It doesn't know to check if which android points to the legacy SDK instead of the new CLI.

2. Self-heal the environment: It lacks the platform-specific installation one-liners (for Windows, Linux, and macOS ARM/Intel) required to install the correct binary that supports the skills command.
This creates a "dead end" for agentic workflows right at the start of the onboarding process.

### Proposed Skill

Documentation Enhancement: Multi-Platform Environment Setup & Troubleshooting
I propose adding a troubleshooting section to the README.md that provides high-fidelity instructions for both the LLM and the user to resolve this naming collision. This should include:
- Diagnostics: Using which android (POSIX) or where android (Windows) to identify the path.
- Installation One-liners:
- macOS (ARM64): curl -fsSL https://dl.google.com/android/cli/latest/darwin_arm64/install.sh | bash
- macOS (x64): curl -fsSL https://dl.google.com/android/cli/latest/darwin_x64/install.sh | bash
- Linux: curl -fsSL https://dl.google.com/android/cli/latest/linux/install.sh | bash
- Windows: curl -fsSL https://dl.google.com/android/cli/latest/windows/install.exe -o android-setup.exe; ./android-setup.exe
- Official Reference: Link to developer.android.com/tools/agents/android-cli.

### Additional Context
By adding these specific "setup skills" to the README, AI Agents can parse the troubleshooting steps and automatically suggest or execute the correct installation command when they detect a skills: command not found error. This significantly reduces friction for developers with existing Android SDK installations.
I attempted to open a PR for this, but noted that public contributions are not currently accepted, so I am submitting the documentation fix here for the maintainers to incorporate.

Open README.md and add the proposed troubleshooting section for the android command conflict. Include the POSIX and Windows diagnostics, the four platform-specific installation commands, and the official Android CLI reference; verify that the commands and link are accurate and that the section explains how to resolve a missing skills command.

Written by the indexing model from the issue text.