jam
Skill11 starsChanged 10 days agoMITView on GitHub
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.
2 other projects use a version of this.
Adopted by
Most recently taken up by
- jamdotdev/skillsword for word, first seen Nov 1, 2026
- PythonShe/Repertoiretheir own version, first seen Jul 10, 2026
Other versions2 projects use a version of this.
Word for word · 1
- jamdotdev/skills★ 11100% same
Edited · 0
None found.
Wrote their own version · 1
- PythonShe/Repertoire★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-voiceoverSkill
- jam-annotateSkill
- jam-fixSkill
- jam-proofSkill
- jam-proof-tableSkill
- jam-setupSkill
- jam-to-e2eSkill
- jam-to-tasksSkill
- jam-to-ticketSkill
- record-demoSkill
- record-terminal-proofSkill
- video-to-jamSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read the request, pick one skill below, and load it with your skill tool (the Skill tool in Claude Code, $name in Codex), not by opening …
- Very specific: line 36
Read the Jam's details first: the getDetails MCP tool, or jam get jam <id> --json.
- Very specific: line 58
When this skill, a Jam MCP tool, a jam command or a Jam doc was wrong, stale or confusing, or worked unusually well, tell Jam.
- Very specific: line 62
Call the submitFeedback MCP tool with body, category and subject.
- Distinctive: line 64
When MCP is unavailable, use the CLI:
- Distinctive: line 72
No secrets, customer data, source code, stack traces or recording content.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
jam
Read the request, pick one skill below, and load it with your skill tool
(the Skill tool in Claude Code, $name in Codex), not by opening its file,
so its references and scripts resolve. Do not do the work from this file;
the target skill holds the steps. Say which skill you picked in one line
before you start.
Route by what was asked
| The user wants | Load |
| the cause of a bug, a fix, triage, "what went wrong" | jam-fix |
| an e2e test, a regression test, a repro | jam-to-e2e |
| the changes they narrated done ("do what I said", "make it look like this") | jam-to-tasks |
| a ticket in Linear, GitHub Issues or Jira, or whether one exists | jam-to-ticket |
| a recorded Jam of their change working, a shareable demo video | jam-proof |
| a screenshot marked up and shared as a Jam | jam-annotate |
| one table of claims and the Jam that shows each | jam-proof-table |
| a video file they already have turned into Jams | video-to-jam |
| Jam set up for this agent: the CLI, sign-in, Jam MCP, the skills | jam-setup |
| a polished, narrated demo video of a feature | record-demo |
| a spoken voiceover on a video | add-voiceover |
| a terminal run recorded as a GIF for the pull request | record-terminal-proof |
Several asks in one request ("fix it and file a ticket"): run the skills in the order asked, and pass what the first one found to the next.
A Jam link with no clear ask
Read the Jam's details first: the getDetails MCP tool, or
jam get jam <id> --json. For a video with the mic on (micEnabled), read
the transcript too (getVideoTranscript, or jam get transcript <id> --json):
the spoken asks are there, and a title like "Feedback" says nothing about
them. If captions are not ready, wait a minute and retry once, then route on
the details and say so. Then route by what it holds:
- Several changes asked for, in the narration or in the title, description
or comments of a silent Jam:
jam-to-tasks. - One bug, an error, or a failed request:
jam-fix. It diagnoses without changing code, so it is the safe default. - Neither is clear: ask one question that names the options in plain words ("fix it, write a test for it, or file a ticket?").
Nothing matches
For anything else about Jams (list, search, comment, move to a folder),
use the Jam MCP tools or the jam CLI directly. jam agent-context prints
every command.
Send feedback to Jam
When this skill, a Jam MCP tool, a jam command or a Jam doc was wrong,
stale or confusing, or worked unusually well, tell Jam. Send it yourself:
Jam's agents read it, so it needs no approval.
Call the submitFeedback MCP tool with body, category and subject.
When MCP is unavailable, use the CLI:
jam feedback "<what you were doing, what you expected, what happened, the mistake>" --category <skills|mcp|cli|docs> --subject <skill name, tool name or command>- Jam surfaces only, not the user's code or other tools.
- At most once per session, and never for a slip you corrected yourself.
- No secrets, customer data, source code, stack traces or recording content.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.