investigate-bug SKILL.md skillA
investigate-bug from jamdotdev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jamdotdev/skills/investigate-bug@git:20261001.dd77fcfPins git:20261001.dd77fcf in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jamdotdev/skills
- Path
skills/investigate-bug/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261001.dd77fcf, committed Oct 1, 2026
- First version recorded
- Jul 15, 2026
- Size
- 6,254 bytes
- Repository stars
- 5
- License
- MIT
Structured workflow for analyzing a Jam bug report end-to-end — pulls diagnostics from the Jam MCP server (console, network, user events, screenshots, video frames, transcript) and produces a root-cause hypothesis. Invoke with `/investigate-bug <jam-url-or-id>`.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Investigate Bug A structured workflow for investigating Jam bug reports. Invoke with `/investigate-bug <jam-url-or-id>`. ## Workflow ### Step 1: Get the Bug Report Call `getDetails` with the provided Jam URL or ID. A full `https://jam.dev/c/...` URL or a UUID both work. From the response, extract: - **Description** — what the reporter said - **Type** — `video`, `screenshot`, or `replay` - **Device info** — browser, OS, screen size - **Investigation Guide** — server-recommended next steps, returned as the second text block - **Postprocessing status** — for fresh Jams, some event-backed tools may report "not ready yet" ### Step 2: Follow the Investigation Guide The `getDetails` response includes an Investigation Guide built from real signals in the Jam (console error counts, 4xx/5xx ranges per host, mic enabled, etc.). **Treat it as authoritative** — the steps below are fallbacks for when the guide is light or you want to drill deeper. - Each path specifies a **tool** to call, suggested **arguments**, and **what to look for**. - Investigate `high` priority paths first; defer `medium` until they're exhausted. …
Read the whole file at its exact version.
How to install
mdr add jamdotdev/skills/investigate-bug@sha256:2ff66b18f291b39eThe line at the top of this page pins the label git:20261001.dd77fcf, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_sn37hmflpu5dki3p)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Jul 15, 2026 and Oct 1, 2026, about one every 19 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261001.dd77fcf latest | 2026-10-01 | dd77fcf | 6,254 B | A | view · diff |
| git:20261001.e3d9a43 | 2026-10-01 | e3d9a43 | 6,172 B | A | view · diff |
| git:20261001.fa219c1 | 2026-10-01 | fa219c1 | 6,358 B | A | view · diff |
| git:20260915.13b6889 | 2026-09-15 | 13b6889 | 4,922 B | A | view · diff |
| git:20260715.cef0ba8 | 2026-07-15 | cef0ba8 | 4,886 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6254 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
jamdotdev/skills · 5 stars · license MIT · pushed 2026-10-21 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_sn37hmflpu5dki3p GET https://markdownregistry.com/api/v1/resolve?ref=jamdotdev/skills/investigate-bug GET https://markdownregistry.com/api/v1/blob/2ff66b18f291b39ece12cffb2b00f521bb6eb20a6bcca161b918af2d6cf08c0e
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from jamdotdev/skills
Every file in jamdotdev/skills