jam-fix

One Jam in, one diagnosis out, plus the fix when the user asks for one. The diagnosis says what happened, the likely cause, the evidence for it, and what to do next. Stop reading data once you have the cause.

A Jam is a recording of what happened on a screen: the video or screenshot with the console logs, network requests and user events of that moment attached. This skill reads one that shows a bug. Its id is the UUID at the end of https://jam.dev/c/<id>; every tool takes the full URL or the id.

Pick the interface

Use the connected Jam Model Context Protocol (MCP) tools (getDetails, getConsoleLogs, ...). If a tool is unavailable, say what could not be read. Do not invent evidence.

When MCP is unavailable and a shell is available, read references/cli.md for Jam CLI setup and the command for each step below. That reference also covers optional proof uploads.