jam-to-e2e SKILL.md skillA
jam-to-e2e from jamdotdev/jam-plugin is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jamdotdev/jam-plugin/jam-to-e2e@git:20261022.832a0b6Pins git:20261022.832a0b6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jamdotdev/jam-plugin
- Path
skills/jam-to-e2e/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261022.832a0b6, committed Oct 22, 2026
- First version recorded
- Oct 22, 2026
- Size
- 8,693 bytes
- Repository stars
- 5
- License
- MIT
Turn a Jam (a jam.dev screen recording with the console, network and user actions attached) into steps and an end-to-end test in the project's own runner and language, with first-class guidance for Playwright and tester-army/e2e, grounded in the current code. A Jam of a flow or demo becomes a test that guards it; a Jam of a bug becomes a failing test the fix turns green. Use when the user pastes a jam.dev link and asks for an e2e test, a regression test, a repro, or to "write a test for this".
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
# jam-to-e2e The Jam shows what the user did and what the screen, console and network did in return. The code shows what the labels and routes are today. The tests assert what the product must do. One test per claim: a Jam that walks through three screens is three tests, and a Jam of one bug is one. A Jam is not always a bug report, so the user's request decides what the test must do today, not the Jam: - "Cover this flow", "write a test for this demo": the test asserts what the Jam shows and **passes** today. It guards the flow. - "Regression test", "reproduce this bug", "test for this bug": the test asserts what should have happened and **fails** until the fix lands. - Neither said: take the Jam's title and description as the hint, state which reading you took, and ask when you can. ## Pick the interface Use the Jam Model Context Protocol (MCP) tools when they are connected. Otherwise read [references/cli.md](references/cli.md) for the Jam CLI setup; the table below gives the command for each read. ## 1. Read the Jam Fetch in this order and stop when you have the steps and the expected results. | What | MCP | CLI | | --- | --- | --- | …
Read the whole file at its exact version.
How to install
mdr add jamdotdev/jam-plugin/jam-to-e2e@sha256:ce5a4e68be902611The line at the top of this page pins the label git:20261022.832a0b6, 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_775l3iq7ur5u5nfn)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, all committed on Oct 22, 2026.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.832a0b6 latest | 2026-10-22 | 832a0b6 | 8,693 B | A | view · diff |
| git:20261022.8fed62f | 2026-10-22 | 8fed62f | 8,645 B | A | view · diff |
| git:20261022.cf595bb | 2026-10-22 | cf595bb | 8,270 B | A | view · diff |
| git:20261022.e6187ca | 2026-10-22 | e6187ca | 8,185 B | A | view · diff |
| git:20261022.cc0d83c | 2026-10-22 | cc0d83c | 7,187 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 (8693 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/jam-plugin · 5 stars · license MIT · pushed 2026-10-22 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_775l3iq7ur5u5nfn GET https://markdownregistry.com/api/v1/resolve?ref=jamdotdev/jam-plugin/jam-to-e2e GET https://markdownregistry.com/api/v1/blob/ce5a4e68be90261113bbe9e8b2377fd81a5ce01a198b989e05d358fb5a5fb695
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.