run-interactive-cli-session
Perform interactive testing on Kobiton devices using natural language. Translates user intents into CLI commands - WebDriver actions (find elements, type, click, swipe), device operations (adb shell, screen capture, port forwarding), file management (push/pull), app management, and test execution. Use when the user wants to interact with a mobile device on Kobiton, run exploratory tests, inspect device state, manage files on a device, or execute test sessions - even if they don't say "interactive test" explicitly. Trigger with "interact with kobiton device", "explore on kobiton", or "tap/sw
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill run-interactive-cli-session --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Drives interactive testing on Kobiton devices by translating user natural-language intents into the Kobiton CLI, covering WebDriver actions (find elements, type, click, swipe), device operations (adb shell, screen capture, port forwarding), file management (push/pull), app management, and test execution. It can create or resume a Kobiton session, execute the corresponding CLI commands, capture artifacts (screenshots, page source) under the workspace, and report results in plain language.
How it works
All CLI calls go through a single wrapper at ~/.kobiton/bin/kobiton that resolves the bundled binary, uses credentials from ~/.kobiton/.credentials, and a session from ~/.kobiton/.session. For each user request, it may:
- Pick a device with listDevices / getDeviceStatus as needed and capture UDID and device id.
- Create a session with $KOBITON_BIN -u <udid> session create if none exists, parse kobitonSessionId: <id>, and mkdir -p .kobiton/sessions/<session-id> for artifacts.
- Translate the natural-language intent into one or more CLI commands, executing them via the literal path ~/.kobiton/bin/kobiton and parsing the JSON or text responses.
- Capture artifacts in .kobiton/sessions/<session-id>/ (screenshot and source) and report results in plain language.
- End the session with $KOBITON_BIN session end when done.
Commands and workflows follow the references in the skill’s Command Reference, including how to chain commands (e.g., finding an element, then acting on it) and how to structure artifact storage.
When to use it
Use when the user wants to interact with a Kobiton mobile device, run exploratory tests, inspect device state, manage files on a device, or execute test sessions—even if the user doesn’t explicitly say “interactive test.” Trigger phrases include "interact with kobiton device", "explore on kobiton", or "tap/swipe on device".
What it can touch
It can run the Kobiton CLI via the shell wrapper at ~/.kobiton/bin/kobiton, targeting commands like wd (WebDriver), device (adb-shell, forward, screen), file (push/pull), app, and test. Artifacts are stored under the workspace at .kobiton/sessions/<session-id>/; commands and responses are read and interpreted to produce user-facing results.
Caveats
Requires the Bundled Kobiton CLI binary at ~/.kobiton/bin/kobiton (macOS target). If credentials are missing or the binary is unavailable, the skill advises running /automate:doctor and then /automate:setup to repair.
# Run Interactive Test ## Overview Drive a Kobiton device interactively from natural-language intent. Given a request like "find the Login button and tap it" or "pull the latest log file from this Pixel", this skill creates (or resumes) a session, translates the intent into the right CLI command - WebDriver action, `adb shell`, file transfer, app launch, test run - captures the response, saves art
What does the run-interactive-cli-session skill do?
Perform interactive testing on Kobiton devices using natural language. Translates user intents into CLI commands - WebDriver actions (find elements, type, click, swipe), device operations (adb shell, screen capture, port forwarding), file management (push/pull), app management, and test execution. Use when the user wants to interact with a mobile device on Kobiton, run exploratory tests, inspect device state, manage files on a device, or execute test sessions - even if they don't say "interactive test" explicitly. Trigger with "interact with kobiton device", "explore on kobiton", or "tap/sw
How do I install it?
Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill run-interactive-cli-session --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From jeremylongshore/claude-code-plugins-plus-skills, a repository with 2,596 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.