jam-cli SKILL.md skillB

jam-cli from jamdotdev/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add jamdotdev/skills/jam-cli@git:20260915.13b6889

Pins git:20260915.13b6889 in mdr.lock. Pin the fingerprint instead.

Audit grade
B, 16 of 17 checks passed
Kind
SKILL.md skill
Repository
jamdotdev/skills
Path
skills/jam-cli/SKILL.md
Versions recorded
3
Latest version
git:20260915.13b6889, committed Sep 15, 2026
First version recorded
Sep 7, 2026
Size
4,856 bytes
Repository stars
5
License
MIT

Use the `jam` CLI when the Jam MCP server is not connected (Cloud Agents, CI, headless shells) or when you need shell-composable output. Reads a Jam's console, network, frames, and transcript with `jam get`, and records proof of a fix with `jam record run`. Install, auth with JAM_TOKEN, and the triage and proof loops.

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 CLI

The Jam MCP server and the `jam` CLI read the same data with the same personal access token. Prefer the MCP tools when they are connected. Reach for the CLI when they are not (cloud agents, CI, a container) or when you want `--json` output to pipe through `jq`.

## Install

```bash
command -v jam >/dev/null || curl -fsSL https://native.jam.dev/install | bash
export PATH="$HOME/.local/bin:$PATH"
jam --version
```

Windows: `powershell -c "irm https://native.jam.dev/install.ps1 | iex"`.

## Authenticate

Check first, then pick the path that fits the environment:

```bash
jam auth status --json
```

- **Headless (Cloud Agents, CI):** set `JAM_TOKEN` to a personal access token. The CLI reads it for the life of the process and never writes it to disk. Create tokens under Settings → MCP at https://jam.dev/s/settings/mcp. Ask the user to add it as a secret; never paste a token into a file or a commit.
- **A machine with a browser:** `jam auth login` opens OAuth.
- **A token on stdin:** `echo "$TOKEN" | jam auth login --token`.

Exit code 3 means not authenticated. Branch on exit codes, not on stderr text.

## Load the full command reference
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint
mdr add jamdotdev/skills/jam-cli@sha256:5d5b2b243eb58148

The line at the top of this page pins the label git:20260915.13b6889, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_oxkjgkl6sniacj25.svg)](https://markdownregistry.com/a/art_oxkjgkl6sniacj25)

1 badge image fetches in 30 days. What the badge shows.

Versions

The registry has recorded 3 versions of this file, between Sep 7, 2026 and Sep 15, 2026, about one every 4 days.

versioncommittedcommitsizeaudit
git:20260915.13b6889 latest2026-09-15 13b6889 4,856 BB view · diff
git:20260915.568fbdc2026-09-15 568fbdc 4,103 BB view · diff
git:20260907.f34f6a32026-09-07 f34f6a3 4,011 BB view

Audit of the latest version

B  16 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • fail: No curl or wget piped into a shell (matched: curl -fsSL https://native.jam.dev/install | bash)
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (4856 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 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

Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.

Source

GitHub

jamdotdev/skills · 5 stars · license MIT · pushed 2026-10-21 · branch master

API

GET https://markdownregistry.com/api/v1/artifacts/art_oxkjgkl6sniacj25
GET https://markdownregistry.com/api/v1/resolve?ref=jamdotdev/skills/jam-cli
GET https://markdownregistry.com/api/v1/blob/5d5b2b243eb58148e124b78973686665a2f172b3c97bbf94081ad6edb4969193

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

investigate-bug SKILL.md skill
jamdotdev/skills · skills/investigate-bug/SKILL.md · Structured workflow for analyzing a Jam bug report end-to-end — pulls diagnostics from the Jam MCP server (console…
git:20261001.dd77fcf · audit A · 5 stars

Every file in jamdotdev/skills

Browse by kind, by grade B, or by owner.