smoke-and-ship SKILL.md skillA
smoke-and-ship from nightly-labs/openbot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nightly-labs/openbot/smoke-and-ship@git:20261016.21e6550Pins git:20261016.21e6550 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nightly-labs/openbot
- Path
.agents/skills/smoke-and-ship/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261016.21e6550, committed Oct 16, 2026
- Size
- 2,037 bytes
- Repository stars
- 5,267
- License
- a license file GitHub does not identify
Smoke test the current branch, then ship it to main only when all smoke items pass. Use when the user asks to smoke and ship, or to test a change in the real app and then merge it.
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
# Smoke and ship
Run the `smoke` skill on the current branch. When all smoke items pass, run
the `ship` skill. Do not ship a branch with a failed smoke item.
When the user invokes this skill, they approve the merge at the end, but only
when the smoke test passes and every `ship` gate is green.
Keep a checklist in `TASKS.md`: one item for the smoke test, and one item for
each `ship` gate.
## Step 1 — Smoke
Run the `smoke` skill on the current branch. Do all of its steps, including
the clean-up and the report.
## Step 2 — Decide
Use the smoke report:
- All items are `pass`: go to Step 3.
- The smoke skill says that the change has no user-visible behavior: this
is a pass. Go to Step 3.
- One or more items are `fail`: stop. Do not ship. Give the smoke report.
Do not fix a failure unless the user asks.
- An item is `not checked`:
- When the cause is outside local reach (a real second computer, a paid
provider, a production build, Windows or Linux), continue to Step 3.
Put the item in the PR `## Verification` section.
- For a different cause, such as a stack that did not start, stop and
ask the user.
## Step 3 — Ship
…Read the whole file at its exact version.
How to install
mdr add nightly-labs/openbot/smoke-and-ship@sha256:189f27dbae1bf161The line at the top of this page pins the label git:20261016.21e6550, 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_i7soy3luku4j25lu)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 16, 2026.
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 (2037 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
nightly-labs/openbot · 5,267 stars · license a license file GitHub does not identify · pushed 2026-11-04 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_i7soy3luku4j25lu GET https://markdownregistry.com/api/v1/resolve?ref=nightly-labs/openbot/smoke-and-ship GET https://markdownregistry.com/api/v1/blob/189f27dbae1bf161518ab067a0a247dba6a2f6803b1c87031c7b40ac5df889b4
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.