principle-sequence-verifiable-units SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 6 indexed copies. Same content hash, so the same checks give both the same grade.

principle-sequence-verifiable-units 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/principle-sequence-verifiable-units@git:20261013.9e6954c

Pins git:20261013.9e6954c in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

nightly-labs/openbot

Path

marketplace/production-catalog/bundles/pstack/skills/principle-sequence-verifiable-units/SKILL.md

Versions recorded

1

Latest version

git:20261013.9e6954c, committed Oct 13, 2026

Size

1,705 bytes

Repository stars

5,267

License

a license file GitHub does not identify

Apply to multi-step work (sweeps, migrations, runs of similar edits) and to how you stack commits and PRs. Break work into small units that each end in a verifiable state, check each before the next, and order delivery so the sequence proves itself to a reviewer.

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

# Sequence work into verifiable units

Order work as a sequence of small units, each ending in a state you can check, and don't advance until the current one is green.

**Why:** A break caught at the unit that caused it is cheap to localize. A break caught after a batch is buried, and you have already built further on a broken base. Sequencing those same units into a delivery a reviewer can replay turns "trust me" into "watch it go red, then green."

**Execution.** In a sweep, migration, or any run of similar edits, verify each change before starting the next. Each unit is a before/after bracket: known-good state, one change, run the check, then proceed. Rebase onto clean trunk first so every check measures against the real baseline. When a lever does the edits, the per-unit check is nearly free. Run it anyway.

**Delivery.** Stack commits and PRs in the order that proves the work. The canonical shape is the failing test first, then the fix on top. Other story orders are a subtraction before the reshape, a baseline capture before the treatment, the scaffold before the feature. Each commit lands on its own and the sequence reads as an argument.
…

Read the whole file at its exact version.

How to install

mdr add nightly-labs/openbot/principle-sequence-verifiable-units@sha256:2ccbbacc56ace5af

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

Versions

The registry has recorded 1 version of this file, committed on Oct 13, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_adwmmc4b6pqf6mpl
GET https://markdownregistry.com/api/v1/resolve?ref=nightly-labs/openbot/principle-sequence-verifiable-units
GET https://markdownregistry.com/api/v1/blob/2ccbbacc56ace5afdfb8670cef19d7bd009fb2a0033b9a741cbdf2b6baf72187

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 nightly-labs/openbot

Every file in nightly-labs/openbot

Other files named principle-sequence-verifiable-units

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