Agent skill · software engineering · jeremylongshore
drive-automation-session
Drive an already-reserved Kobiton device from a natural-language intent. Opens an automation Appium session directly against the Kobiton WebDriver hub, runs an observe-decide-act loop with one action per iteration, pauses to ask the user when stuck (same-action repetition, screen unchanged, or model self-declared blocker), and returns the session id. Use when the user says "drive the device to X", describes a flow they want exercised on a reserved device, or asks to "automate this intent on Kobiton". Complements run-interactive-session (which uses the CLI session type) by using the automation session type so the resulting session is consumable by saveTestCase and the existing test-run authoring flow.
Why this skill is useful
Adds executable automation scripts for driving Kobiton devices based on natural language intents, which are not available in public documentation.
What it needs
Requires node installed locally. Requires kobiton account access. About 11k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Drive from Intent Overview Drive a Kobiton device from a natural-language intent. The caller provides: 1. An intent string (e.g. "open Settings, enable Bluetooth, then go back to home"). 2. A UDID for a device the caller has already reserved. 3. An app reference (kobiton-store:vXXXXX) or a browser name for web sessions. The skill opens an automation-type Appium session (with appium:newCommandTimeout: 1800 so the session survives pauses while the model asks for guidance), runs an observe-decide-act loop, and returns the session id. The returned session is consumable by the Kobiton MCP tools getSession, getSessionArtifacts, and saveTestCase exactly like any other automation session. Tool naming. This doc refers to Kobiton MCP tools by their bare names (getSession, reserveDevice, terminateSession, …). The exact registered name depends on how the host loaded the MCP server (e.g. Claude Code as a plugin exposes mcppluginautomatekobitongetSession; a repo-local .mcp.json or claude mcp add exposes mcpkobitongetSession; other hosts differ). Models fuzzy-match on the bare name, so use it and let the host resolve the prefix. This skill complements — and does NOT replace — run-interactive-session. They serve different session types: Skill Session type Best for ------- -------------- ---------- run-interactive-session CLI session (~/.kobiton/bin/kobiton) Human-driven exploration, ad-hoc inspection drive-automation-session Automation session (direct Appium HTTP) AI-driven flows, saveable as a test case Prerequisites Runs on any OS, but needs two things from the host: a persistent local filesystem — the observe-decide-act loop passes state between turns through iter-N..json files, so that file handoff is the loop — and ~/.kobiton/.credentials, which scripts/appium.js reads directly (see below). A host with a filesystem but no way to run /automate:setup still can't finish; route those users to create-test-run. Node.js 18+; no native binary (scripts/appium.js uses node:https). …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/drive-automation-session--f30952