# Setup Espresso

> Prepare and verify Appium Espresso by validating Node/Appium, Android SDK and Java prerequisites, driver installation, doctor output, and server smoke evidence. Use after the setup Skill selects Espresso. Do not use for an existing Espresso runtime failure after prerequisites pass; this repository does not provide that troubleshooting workflow.

- Skill: `appium/setup-espresso` (Agent Skill, multi-file: 2 files)
- Install (CLI): `npx skillmds@latest add appium/setup-espresso`
- Raw SKILL.md: https://api.skillmd.com/api/skills/appium/setup-espresso/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Productivity
- Author: appium (https://skillmd.com/u/appium)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/appium/setup-espresso

---


# Espresso Setup Workflow

## Routing

Prepare only the Espresso route. Use driver-specific official guidance for an
existing Espresso runtime failure after setup passes. Load FFmpeg or bundletool
only when the user explicitly requested that capability.

## Required inputs

Confirm Android as the target, global `appium` mode or explicitly requested
local `npx appium` mode, host OS, device or emulator expectations, permissions,
and optional dependency requests.

## Workflow

1. Load the global command profile by default or the local profile only when
   explicitly requested.
2. Load the Android profile, shared Appium setup basics, and Android emulator
   setup Context.
3. Load the Espresso decision, installation, doctor, and smoke references in
   that order.
4. Run `node tools/appium/setup/scripts/check-espresso-env.mjs --format summary --report auto`; add
   `--appium-mode local` only for explicitly requested local mode. Require
   top-level `summary.requiredOk: true`.
   Apply required fixes in technical dependency order and rerun affected checks.
   If the gate remains unresolved, report `blocked` with evidence and the next
   action. Load the matching example only when needed.
5. Verify the direct doctor output reports `0 required fixes needed` using
   `appium driver doctor espresso`, or
   `npx --no-install appium driver doctor espresso` in local mode.
6. Run `node tools/appium/setup/scripts/smoke-appium-server.mjs --driver espresso --report auto`;
   add `--appium-mode local` only in local mode. Require
   `summary.requiredOk: true` for server readiness, driver evidence, and
   cleanup. The smoke reference documents target-specific options.

## Espresso setup safety and approval constraints

- Preserve the selected command mode and working Java, Android SDK, device,
  emulator, and Espresso installations.
- Ask before optional FFmpeg or bundletool setup, privileged commands, SDK
  license changes, Espresso build changes, or emulator creation that changes
  local state.

## Completion criteria

- Android environment completion criteria pass.
- Appium succeeds in the selected command mode.
- The installed driver list includes `espresso`.
- `appium driver doctor espresso` reports `0 required fixes needed`; optional
  warnings are non-blocking.
- `/status` succeeds, server logs list `espresso`, and the server
  started for verification has exited.

## Evidence boundary

Report Appium and Espresso versions, helper `requiredOk`, Android prerequisite
summary, doctor required/optional summary, `/status`, server driver evidence,
cleanup, and explicitly requested optional capability results.

## Self-Improvement Prompt

Before the final response, report any missing, ambiguous, outdated, or
retry-causing Espresso setup instruction with its asset path and proposed
wording. Leave unrelated assets unchanged.