Agent skill · Testing & QA

run-automation-suite

Run local Appium test scripts against Kobiton devices. Guides through app upload, device selection, capability parsing, and local execution. Use when the user asks to run mobile tests, validate an APK or IPA on Kobiton devices, or kick off an Appium suite from a local script directory. Trigger with "run kobiton tests" or "execute appium on kobiton".

jeremylongshoregithub.com/jeremylongshoreGitHub ↗
claude-codecan modify filesships scriptsMIT
Install
npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill run-automation-suite --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 10
SKILL.md size: 23 KB
Bundled scripts: yes
Version: 1.0.2
Declared author: Kobiton Inc.
Allowed tools: >-ReadEditBash(node:*)Bash(npm:*)Bash(npx:*)Bash(yarn:*)Bash(pnpm:*)Bash(python:*)Bash(python3:*)Bash(pytest:*)Bash(java:*)
Requires: >- Compatible with any MCP-aware AI coding assistant. Requires Node.js >= 18 and Appium 2.x. Test scripts must use…
Path: skills/.curated/run-automation-suite/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 2,596
Language: Python
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

Review
written from the skill's own SKILL.md · Aug 5, 2026

What it does

Executes Appium-based mobile test automation against Kobiton devices using a local Appium script. It guides the user through uploading or selecting an app, choosing a device, parsing and reconciling desired capabilities, and running the test in the background while surfacing session details and artifacts.

How it works

  • It starts by identifying the app workflow: asks the user to either upload a new app or use an existing one from Kobiton Store or a URL, then uses uploadAppToStore and related steps to process the upload, including getAppParsingStatus until terminal state.
  • It then prompts for a device selection by listing devices with a platform filter, checks device status with getDeviceStatus, and reserves a device if needed.
  • It asks for the path to the local Appium test script, detects language from the file extension, and reads the script to extract capability fields (platformName, udid, app, kobiton:* extensions, etc.). It determines how the UDID is passed so it can override with the chosen device.
  • It renders capabilities via the provided render-capabilities.js script using the given parameters, then reconciles the rendered output with the parsed script capabilities according to the reconciliation rules, including handling kobiton:aiToolName for adoption analytics.
  • It injects kobiton:aiToolName into the script if appropriate, verified by a grep, and edits the script if needed to ensure the capability appears.
  • Before execution, it presents a summary with Language, Script path, Platform, Device, App, and the exact command to run, then waits for user confirmation to execute the test in the background.
  • If the user opted to watch the run, it can open a live session in a browser; otherwise, it proceeds with a device-only or full session launch URL based on user choice, and uses a chromeless launcher when appropriate.

When to use it

Use when the user asks to run mobile tests, validate an APK or IPA on Kobiton devices, or kick off a Kobiton-hosted Appium suite from a local script directory. Trigger phrases include "run kobiton tests" or "execute appium on kobiton".

What it can touch

  • Tools and scripts: uploadAppToStore, confirmAppUpload, getAppParsingStatus, listApps, listDevices, getDeviceStatus, reserveDevice, render-capabilities.js.
  • It renders capabilities into the local test script and may modify the script to inject kobiton:aiToolName capability as determined by runtime detection.

Caveats

  • Requires Kobiton MCP access and authentication via .mcp.json or .mcp.apikey-example.json.
  • Requires Node.js >= 18 and Appium 2.x; test scripts must use Appium WebDriver protocol.
  • The injection of kobiton:aiToolName is non-interactive and relies on runtime markers; if not applicable, no change is made.
  • The execution is performed in the background; user confirmation is required prior to launching.
From the SKILL.md

# Run Automation Suite ## Overview Execute Appium-based mobile test automation suites on Kobiton's device cloud. Given a local Appium test script, this skill identifies the target app, selects an available device, parses and reconciles capabilities, runs the script in the background, and surfaces the resulting session URL plus artifacts (video, logs, screenshots, reports). Use this skill when the

More from claude-code-plugins-plus-skills
All skills →
About this skill
What does the run-automation-suite skill do?

Run local Appium test scripts against Kobiton devices. Guides through app upload, device selection, capability parsing, and local execution. Use when the user asks to run mobile tests, validate an APK or IPA on Kobiton devices, or kick off an Appium suite from a local script directory. Trigger with "run kobiton tests" or "execute appium on kobiton".

How do I install it?

Run `npx skills add jeremylongshore/claude-code-plugins-plus-skills --skill run-automation-suite --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.

Keep going