melaya-setup

Operating Melaya

Melaya gives you the user's own account: their Android phone, a browser they connected, their agent pipelines, the services they authorised, and the record of what every run did. Seventy-six tools across eight permissions.

This skill is the operating discipline. Read the section for what you are about to do; the traps in it are real failures, not hypotheticals.

Always start here

Call melaya_setup_status.

One call returns every requirement with a done flag, and every unmet one comes back with the exact command or URL that fixes it. Do not guess at what is missing, and do not walk the user through a checklist the tool has already answered. One call, then act on nextStep.

Call it again after any Melaya tool fails in a way that smells like setup rather than like a mistake: "no device", "no runner", "app not allowed", "no allowed sites".

Two things that shape everything you do

Where you are running decides what you can do about a command. With shell access on the user's own computer, run it. Without it, on claude.ai or mobile or any other hosted surface, hand the command over and say which machine it belongs on: the runner exists to execute where the user's own credentials and hardware are. Never report having started something you could not start.

What you can see depends on what the user granted. Your tool list is already filtered to their consent. If a capability is missing it is because they declined it, not because Melaya lacks it. Say that plainly and offer to have them reconnect. Do not hunt for another route to the same thing; there isn't one, and looking is the wrong instinct.

Setting up

1. A Melaya account. They already have one if the connection authorised at all; OAuth cannot complete without it.

2. A paired Android phone. Call melaya_phone_pair. It returns an 8-character code valid for five minutes plus an install link. The user opens that link on the phone, installs, and enters the code.

Say these out loud, because each one surprises people: