Skill

parse-grid-failure

Parses a BrowserStack/SauceLabs/LambdaTest test failure (pasted JSON or session ID) into a clean 5-line markdown summary plus likely root-cause hypotheses. Use when the user shares a cloud-grid failure, a session UUID, asks "why did this run fail", or pastes WDIO/Appium grid output.

npx claudepluginhub rabusek/qa-mobile-pack

Tool Access

This skill is limited to using the following tools:

Read

Preview

Turn a noisy cloud-grid failure into something a QA engineer can triage in under 30 seconds. Input is `$ARGUMENTS` — either a session UUID or a JSON blob from BrowserStack/SauceLabs/LambdaTest API.

SKILL.md

Similar Skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

next-compile

139.2k

Checks Next.js compilation errors using a running Turbopack dev server after code edits. Fixes actionable issues before reporting complete. Replaces `next build`.

1 file

vercel-next-js-2

karpathy-guidelines

90.0k

Guides code writing, review, and refactoring with Karpathy-inspired rules to avoid overcomplication, ensure simplicity, surgical changes, and verifiable success criteria.

andrej-karpathy-skills

Stats

Stars0

Forks0

Last CommitMay 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

parse-grid-failure

Parse Grid Failure

Turn a noisy cloud-grid failure into something a QA engineer can triage in under 30 seconds. Input is $ARGUMENTS — either a session UUID or a JSON blob from BrowserStack/SauceLabs/LambdaTest API.

Requires browserstack MCP for live session fetch — see qa-mobile-pack/mcp/README.md. If MCP is not available, ask the user to paste the session JSON.

Procedure

Detect input type:

36-char UUID matching [0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12} → session ID. If browserstack MCP is available, fetch session details. Otherwise stop and request the JSON.
Otherwise treat input as raw JSON (BrowserStack automate/sessions/{id}.json shape, SauceLabs jobs/{id} shape, or LambdaTest sessions/{id} shape).

Extract the following fields (provider field names vary, use closest match):

device (model name, e.g. iPhone 15 Pro)
os + os_version
locale (default en-US if missing)
browser_version or app_version
created_at / timestamp
failed_step (last step name before failure, or reason)
error_message — first 200 chars only
video_url / screencast_url
logs_url / appium_logs_url
network_url / har_url

Render the summary using the template below.

Generate exactly 3 root-cause hypotheses, each tagged with one of: timing, network, selector, device, data. Base the tags on signals from the error message (e.g. ElementNotInteractable → timing; ECONNRESET/5xx → network; NoSuchElement → selector; OutOfMemory/ANR → device).

Output template

**Failure summary** - Device: <model> (<os> <os_version>, locale <locale>) - App/Browser: <version> - When: <timestamp> - Failed step: <step name> - Error: <first 200 chars> **Artefacts** - Video: <video_url> - Logs: <logs_url> - Network HAR: <network_url> **Likely causes** 1. [<tag>] <hypothesis> 2. [<tag>] <hypothesis> 3. [<tag>] <hypothesis>