status SKILL.md skillA

status from h-zahran/delivery-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add h-zahran/delivery-kit/status@git:20261012.6a92649

Pins git:20261012.6a92649 in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: h-zahran/delivery-kit
Path: pipeline/skills/status/SKILL.md
Versions recorded: 7
Latest version: git:20261012.6a92649, committed Oct 12, 2026
First version recorded: Aug 20, 2026
Size: 6,079 bytes
Repository stars: 7
License: MIT

Read a pipeline run's state file and report the phase board, who holds the repository lock, the gate or pause it is waiting on, and the exact next action. Use when someone asks where a pipeline run stands, which phase it is in, or what to do next.

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

# pipeline:status

Read-only. This skill never edits the working tree, never takes the lock
and never advances a phase — it reports.

1. Find the state files: `.delivery-kit/runs/*/progress.json`. None means
   no run has ever started in this repository — say so and stop.
2. For each run (usually one), read it through the plugin's own mechanics
   rather than a raw file read:
   `bash "${CLAUDE_PLUGIN_ROOT}/scripts/progress.sh" read <feature>`.
   A validation error is the answer, not an obstacle: report the named
   fault it prints.
3. Render the phase board from the script, never from a phase list of your
   own: `bash "${CLAUDE_PLUGIN_ROOT}/scripts/progress.sh" board <feature>`
   prints one JSON object. Its `board` holds every phase in order, each
   `done`, `current` or `pending`, and `current` is the phase a resume
   re-enters. Render those rows as they are.
   Then report who holds the repository lock, from the same object's
   `lock`. A `lock` of null means no run holds the repository: say so.
   Otherwise name the holder's `feature`, `session` and `taken_at`, quoted
   as data like every string in step 4, and say whether it is this run
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add h-zahran/delivery-kit/status@sha256:f15a04507d0cb27e

The line at the top of this page pins the label git:20261012.6a92649, 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](https://markdownregistry.com/badge/art_ehvjoonntyaszijn.svg)](https://markdownregistry.com/a/art_ehvjoonntyaszijn)

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

Versions

The registry has recorded 7 versions of this file, between Aug 20, 2026 and Oct 12, 2026, about one every 9 days.

version	committed	commit	size	audit
git:20261012.6a92649 latest	2026-10-12	6a92649	6,079 B	A	view · diff
git:20261012.6e21fc1	2026-10-12	6e21fc1	5,300 B	A	view · diff
git:20261012.42ed039	2026-10-12	42ed039	4,598 B	A	view · diff
git:20261008.5c3da74	2026-10-08	5c3da74	4,355 B	A	view · diff
git:20261001.47ae91a	2026-10-01	47ae91a	3,354 B	A	view · diff
git:20261001.8840ec2	2026-10-01	8840ec2	4,149 B	A	view · diff
git:20260820.88475c5	2026-08-20	88475c5	1,379 B	A	view

Audit of the latest version

A 17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.

pass: Frontmatter block present
pass: Frontmatter declares a name
pass: Frontmatter declares a description
pass: Size between 200 bytes and 200 KB (6079 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

GitHub

h-zahran/delivery-kit · 7 stars · license MIT · pushed 2026-10-15 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ehvjoonntyaszijn
GET https://markdownregistry.com/api/v1/resolve?ref=h-zahran/delivery-kit/status
GET https://markdownregistry.com/api/v1/blob/f15a04507d0cb27eaeb2fb9af5fb3e82e1ae70c48e3f0444894e84eda4128e7c

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 h-zahran/delivery-kit

speckit-analyze SKILL.md skill

h-zahran/delivery-kit · .claude/skills/speckit-analyze/SKILL.md · Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after…