appium-mcp-auth: Skill for Claude Code

Verify appium-mcp-auth

Run the complete quality gate and report pass/fail crisply. Stop and report at the first failing stage; do not "fix" by editing appium-mcp core (forbidden — see CLAUDE.md).

Stages (run in order)

1. Typecheck (source only):

   npm run typecheck
   

2. Unit tests (60 tests via node:test + tsx):

   npm test
   

   Expect pass 60 / fail 0. If a test fails, show the failing assertion.

3. Build (emit dist/):

   npm run build
   

4. SSE smoke boot — start the real server with a throwaway key, confirm the plugin registers and the health endpoint answers, then stop it:

   export APPIUM_MCP_AUTH_API_KEYS='[{"id":"smoke","secret":"smoke-secret","subject":"smoke","scopes":["appium:use"]}]'
   export APPIUM_MCP_AUTH_AUDIT=false
   PORT=8791
   node dist/cli.js --httpStream --port=$PORT --endpoint=/sse > /tmp/amauth-verify.log 2>&1 &
   SVPID=$!
   for i in $(seq 1 40); do
     grep -q "listening on" /tmp/amauth-verify.log 2>/dev/null && break
     kill -0 $SVPID 2>/dev/null || { echo "SERVER EXITED EARLY"; break; }
     sleep 0.5
   done
   cat /tmp/amauth-verify.log
   curl -s -o /dev/null -w "health HTTP %{http_code}\n" http://localhost:$PORT/health
   kill $SVPID 2>/dev/null; wait $SVPID 2>/dev/null; rm -f /tmp/amauth-verify.log
   

Pass criteria

• typecheck: exit 0, no output
• tests: pass 60, fail 0
• build: dist/ populated, exit 0
• smoke boot log contains:
  • [PluginManager] Registered plugin "appium-mcp-auth"
  • All tools registered
  • httpStream (SSE) listening on http://localhost:8791/sse
• health HTTP 200

Notes

• Requires appium-mcp installed (it is a regular npm dependency) since the plugin composes into it at runtime.
• The smoke boot needs no real device — it only starts the transport and registers tools; it does not create an Appium session.
• If the port is busy, pick another (e.g. 8792) and reuse it consistently.
• Report a one-line summary at the end: which stages passed and any failure.