Index of every page on this site: llms.txt
All skills
pingdotgg avatar

/test-t3-mobile

@b5453de
by Ping.ggpingdotgg/t3code67k stars
11,639
Run it yourself

Test T3 Code's native iOS and Android app through its Device panel and returned AgentDevice command. Use for mobile verification, native-client builds, Metro launch, and mobile pairing against isolated development state.

Use this Skill: https://skilld.dev/gh/pingdotgg/t3code/test-t3-mobile

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈59 tokens for metadata: the name and description. ≈994 when used: this file. ≈59 more on demand in 1 file.

Description uses 3.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈237 characters, or 3.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Test T3 Mobile

Open the device

Call device_list, then device_open with the selected host and device IDs. T3 boots the device and shows its live stream in the Device panel. Follow its returned quickStart, using the exact agentDevice.command and all targetArgs on every operation. Use device_screenshot to inspect the screen.

If T3 device tools or the selected device are unavailable, report the blocker and stop verification. Do not install or switch to another automation system.

Use an isolated backend

Reuse this task's healthy backend. Otherwise run vp run dev from the repository root, retain its terminal session, and read the actual backend port from the dev-runner output. Use the worktree's ignored .t3 state. Never run against ~/.t3/userdata. The Browser panel is not required for this workflow.

Test with meaningful project and thread data. Read the shared SQLite fixture reference only when inspecting or seeding SQLite. Stop the test server before fixture writes.

Launch T3 Code Dev

From the checkout being tested on the selected device host, run:

vp run mobile:install <ios|android> <device-id>

This installs the dev client for the checkout's native fingerprint: from the device, the local cache, or the shared cache in seconds, building once only when no machine has that fingerprint yet: in the Mobile Dev Client workflow on Blacksmith when HEAD is pushed and gh may dispatch it (the command waits), otherwise here (5-15 minutes, logged to the file it names). The device id may be omitted when exactly one device is booted. It prints one JSON line; on failure it names the next command. Mobile verification includes that step unless the user prohibits it.

For a device you opened in an agent-device session elsewhere (a device pool, cloud, or remote host), run vp run mobile:install <ios|android> --session <s> --config <file> from the directory you opened the session in, passing the --config file from device_open's targetArgs. Without it, a device pool's gateway refuses the install, wrongly saying agent-device is too old. It installs the cached build into that session (--abi arm64-v8a for an ARM Android device; pool Android emulators are x86_64, the default; --metro <url> also opens it against Metro). Without a cached build for this checkout it builds first, which can outlast the lease, so run vp run mobile:install <ios|android> --prepare (with the same --abi) before you open the device.

Start vp run dev:client from apps/mobile, or reuse a healthy Metro belonging to this checkout. Open its printed development-client URL with AgentDevice open com.t3tools.t3code.dev <url> and all returned target arguments. The device must be able to reach both Metro and the isolated backend. Append &disableAutoLaunch=1&disableFab=1 to the development-client URL query when developer chrome would obscure screenshots or taps; the SDK 58 dev client applies these preferences before the app loads.

Pair and verify

Use the helper from the repository root, with the returned executable and target arguments stored in agent_device_command and the Bash array agent_device_target_args:

.agents/skills/test-t3-mobile/scripts/pair-client.sh \
  <server-port> <base-dir> <device-reachable-backend-origin> \
  "$agent_device_command" "${agent_device_target_args[@]}"

It issues a fresh credential and opens T3 Code Dev's existing pairing route through AgentDevice. For a backend on the device host, use http://127.0.0.1:<server-port> on iOS or http://10.0.2.2:<server-port> on Android. For a remote backend, use its reachable origin.

Confirm the intended projects appear, exercise the affected flow, and capture evidence. Retain the app and environment while iterating. At teardown, remove the disposable connection, close the AgentDevice session, call device_close, and stop only your backend and Metro processes.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts1d3 checks · Risk SAFE
  • Gen Agent Trust Hub4d

    The skill automates mobile app testing workflows, including installing development clients and setting up pairing. It uses project-specific CLI tools and a helper script for orchestration. A minor risk is identified regarding dynamic command execution within a script and the inherent attack surface for indirect prompt injection from processing device screenshots and logs.

  • Socket1d

    No alerts

  • Snyk4d

    Risk: LOW · No issues

Signed by skilld at b5453de. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated last week

README badge

README badge for pingdotgg/t3code/test-t3-mobile