agentleFS
terminalx-aiterminalx-ai/terminalx-skills/skills/terminalx-emulator/SKILL.md

terminalx-emulator

Skill0 starsChanged 3 months agoMITView on GitHub

Control a mobile (iOS) emulator / simulator stream from inside TerminalX using the `terminalx` CLI. Use for taps, gestures, typing, hardware buttons, camera injection, permissions, accessibility tree, and more — all while seeing the live view in TerminalX's emulator pane. Prefer this over raw `npx serve-sim` or direct simctl when running agents inside TerminalX (the terminalx surface handles device scoping, helper lifecycle, and worktree context). Complements the terminalx-cli skill for terminals, worktrees, and the built-in browser.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Prefer this over raw serve-sim or direct simctl when running agents inside TerminalX, which handles device scoping, helper lifecycle, and …

    line 20
  2. Very specific:

    If the TERMINALX_CLI_COMMAND environment variable is set, use its value.

    line 28
  3. Distinctive:

    If the selected executable cannot run, report its exact error and stop.

    line 39
  4. Distinctive:

    Don't guess subcommands or flags from memory or from a cached copy of this stub.

    line 53
  5. Very specific:

    Use this fallback only when the selected binary explicitly reports that skills get is an unknown command.

    line 60

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

TerminalX Emulator

This file is a discovery stub, not the usage guide. The full, version-matched TerminalX emulator reference is served by the terminalx binary itself — kept out of this file on purpose so it can never drift from the binary that will actually run your commands.

Engage TerminalX whenever you drive a mobile (iOS) emulator / simulator stream from inside the TerminalX app: taps, gestures, typing, hardware buttons, camera injection, runtime permissions, the accessibility tree, and more — all while the live view stays in TerminalX's emulator pane. Prefer this over raw serve-sim or direct simctl when running agents inside TerminalX, which handles device scoping, helper lifecycle, and worktree context for you. It complements the terminalx-cli skill for terminals, worktrees, and the built-in browser.

Resolve the CLI for this session

Choose the executable once and reuse it for every later command:

  • If the TERMINALX_CLI_COMMAND environment variable is set, use its value. TerminalX exports this for managed WSL sessions.
  • Otherwise, in a dev checkout whose session exposes TERMINALX_DEV_REPO_ROOT, use terminalx-dev.
  • Otherwise, on Linux outside a TerminalX-managed terminal, use terminalx-ide. That is the executable name the Linux package installs; bare terminalx is not on PATH outside TerminalX's terminals.
  • Otherwise, use terminalx.

Below, TERMINALX is a placeholder for the executable you resolved. Substitute it before running anything; do not create a shell variable or run TERMINALX literally. This works the same way in POSIX shells, PowerShell, and cmd.exe.

If the selected executable cannot run, report its exact error and stop. Do not fall through to another executable, which could silently target a different TerminalX build.

Load the full guide before running TerminalX commands

TERMINALX skills get terminalx-emulator

That prints the complete, version-matched guide for the exact binary that will handle your next commands — booting devices, taps and gestures, typing, hardware buttons, camera injection, permissions, and the accessibility tree. Read it first, then run the specific command you need.

Don't guess subcommands or flags from memory or from a cached copy of this stub. They change between TerminalX releases, and this file deliberately no longer lists them. Confirm the app is up with TERMINALX status --json (start it with TERMINALX open --json if needed), and prefer --json for agent-driven calls.

If an older TerminalX does not recognize skills get

Use this fallback only when the selected binary explicitly reports that skills get is an unknown command. Another failure is not proof of an older binary; report it rather than guessing or changing executables. For a confirmed pre-guide binary, use only this bounded, read-only bootstrap to orient. Do not dead-end and do not invent commands:

TERMINALX status --json
TERMINALX emulator list --json

Then tell the user that updating TerminalX restores the full, version-matched guide via TERMINALX skills get terminalx-emulator. Beyond these commands, ask the user rather than guessing a command surface this older binary may not support.

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.