Skills
Last updated:Nov 15, 2026
A skill is a set of instructions written for an AI assistant: a SKILL.md file plus a few reference files that tell the assistant how to use the yunyoo tools properly for one kind of job, such as looking at the screen before tapping, which actions need your go-ahead first, and what to do when something fails. A skill does not run any program of its own. The work is still done by the yunyoo tools the assistant calls, and what those can do is set by your account permissions and the scopes of your token.
There are two official skills at the moment:
| Name | What it is for |
|---|---|
yunyoo-automation | The general way to operate cloud phones through the MCP tools or the command line |
yunyoo-app-smoke | Installs and opens one app on your cloud phones, walks a path you give, and reports each step with screenshots |
A skill only teaches the assistant what to do. To actually operate a cloud phone the assistant also needs the yunyoo MCP server or the command line, see "Connect MCP" below.
Three ways to get a skill
Install from the Skill market in the desktop app (recommended)
- Open the desktop app (1.1.0 and later) and go to "Skill market" in the sidebar.
- Under "Browse", open a skill and read its description, the permissions and tools listed under "Permissions", the files under "Files", and "Review".
- Click "Install", choose where to install it, and confirm.
Before writing anything, the desktop app checks the package signature and digest, and does not install a package that fails the check. Installed skills appear under "Installed" with their location, version and whether an update is available.
Install with npx skills
If you do not use the desktop app, the open-source skills command line can install from the public index on our website (Node.js 22.20 or later is required):
npx skills add https://www.yunyoo.ai
After you pick the skills and the assistants at the prompts, it installs the skills into .agents/skills/ under the current project folder (and copies them to .claude/skills/ when you pick Claude Code).
skillsis a third-party tool and is not provided by yunyoo. Its usage statistics are handled by the provider of that tool. To turn them off, set the environment variableDISABLE_TELEMETRY=1orDO_NOT_TRACK=1first.- This way checks the download against the digest in the index. It does not check the yunyoo signature.
- The desktop app only manages folders it installed itself: a skill installed this way does not show up under "Installed" and is not updated or uninstalled by the desktop app.
Export a ZIP and upload it to claude.ai
In the skill details click "Export ZIP", then upload the file as a custom skill in the claude.ai settings (whether this is available depends on your claude.ai plan). claude.ai runs in the cloud, so it can only use yunyoo through the remote MCP address and cannot use the command line on your computer.
Two install locations
| Location | Path | Read by |
|---|---|---|
| Shared skills folder | ~/.agents/skills/ | Most AI assistants that support skills, such as Codex, Cursor and Gemini CLI |
| Claude Code skills folder | ~/.claude/skills/ | Claude Code |
Some AI assistants read both folders and will list a skill twice when it is installed in both. If you are not sure, install it in one place: the Claude Code folder when you mainly use Claude Code, the shared folder otherwise.
When a folder with the same name already exists and was not installed by the desktop app (one you placed by hand, or one that npx skills put in your home folder), the desktop app does not overwrite it. Move it away yourself first, or install to the other location.
Updates, uninstalling and withdrawn versions
- Updates: "Installed" marks skills that have a newer version. Before updating you see which files change, and when the new version needs more permissions or tools you confirm each of them.
- Local changes: if you edited installed files, updating and uninstalling list those changes first and only overwrite or delete them after you confirm.
- Uninstalling only removes folders that the desktop app installed.
- Withdrawn versions: when a version turns out to have a problem, we withdraw it. The desktop app then asks you to update or uninstall. For a serious problem it disables that version by moving its folder to
.yunyoo-quarantine/next to it, so assistants no longer read it (a folder you edited is not moved, you only get the notice). A withdrawn version cannot be installed again.
Connect MCP
The tools a skill refers to come from the yunyoo MCP server. There are three ways to connect. They share one set of tools; a few tools and parameters differ with the way you connect, and the tool reference marks each of them. See MCP:
| Way | Good for | Credentials |
|---|---|---|
Local (yunyoo --local mcp) | Only the environments the desktop app on this computer can manage | The desktop app's sign-in, no token needed |
Command line (yunyoo mcp) | The assistant and the command line are on the same computer | The token the command line signed in with |
| Remote MCP address | The assistant runs somewhere else, for example claude.ai | A machine token |
The "AI assistants and MCP" tab of the Skill market finds the AI assistants installed on this computer. It can write the connection settings for you, or just show what would be written so you can do it yourself. You see the change before it is written, and you can click "Test connection" afterwards.
About tokens:
- Configuration files never contain the token itself, only a reference to an environment variable. The local way needs no token at all.
- When you issue a token, tick only the scopes and cloud phones it needs. The skill details list the scopes a skill requires, see Automation overview.
- Do not paste a token into a conversation, and do not ask the assistant to keep it for you.
Common questions
There is no "Skill market" in the sidebar. The feature is being opened gradually. It is in the desktop app from version 1.1.0, and it is not shown when it is not open for your account yet, or when your team role has no permission to view skills. Check the version of your desktop app first.
The skill is installed but the assistant does not use it. Most assistants read the skills folder only when they start, so reopen the assistant after installing. Then check that the skill is in the folder that assistant reads, and that MCP is connected or the command line is installed.
Installing reports a signature or digest problem. The desktop app does not install a package that fails the check. Try again later. If it still fails, contact us, and do not download a file with the same name from another source instead.
Can a skill act behind my back? A skill is only text and does not run by itself. Every action the assistant takes goes through the yunyoo tools and is limited by your account permissions and the token scopes. For actions that change data or cost money, the official skills tell the assistant to ask you first. A skill that passed scanning and review is still not guaranteed to be safe in every situation, so read what it may use before installing.
How do I know it is the officially released version? Open "Review" in the skill details: the signing key, the package digest and the scan and evaluation results are listed there.
