Loading...
Loading...
Route a Jam (a jam.dev screen recording or screenshot with the console, network and user actions attached) to the right Jam skill. Use when the user shares a jam.dev link with no clear ask ("look at this jam", a bare link), or types /jam. For a clear ask (fix, test, ticket, record, annotate), use that skill directly.
npx skill4agent add jamdotdev/skills jam$name| The user wants | Load |
|---|---|
| the cause of a bug, a fix, triage, "what went wrong" | |
| an e2e test, a regression test, a repro | |
| the changes they narrated done ("do what I said", "make it look like this") | |
| a ticket in Linear, GitHub Issues or Jira, or whether one exists | |
| a recorded Jam of their change working, a shareable demo video | |
| a screenshot marked up and shared as a Jam | |
| one table of claims and the Jam that shows each | |
| a video file they already have turned into Jams | |
| Jam set up for this agent: the CLI, sign-in, Jam MCP, the skills | |
| a polished, narrated demo video of a feature | |
| a spoken voiceover on a video | |
| a terminal run recorded as a GIF for the pull request | |
getDetailsjam get jam <id> --jsonmicEnabledgetVideoTranscriptjam get transcript <id> --jsonjam-to-tasksjam-fixjamjam agent-contextjamsubmitFeedbackbodycategorysubjectjam feedback "<what you were doing, what you expected, what happened, the mistake>" --category <skills|mcp|cli|docs> --subject <skill name, tool name or command>