ship SKILL.md skillA
ship from vibemaestro/vibemaestro-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add vibemaestro/vibemaestro-kit/ship@git:20261113.9661a88Pins git:20261113.9661a88 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- vibemaestro/vibemaestro-kit
- Path
plugins/vibemaestro-sdlc/skills/ship/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261113.9661a88, committed Nov 13, 2026
- First version recorded
- Oct 22, 2026
- Size
- 10,024 bytes
- Repository stars
- 4
- License
- Apache-2.0
Use when: the work of an intent in an app repo is done and a PR must be opened — update the repo's kb/current-state.md, run the acceptance commands and record the evidence, then open a draft PR with the plugin's scripts/open-pr.sh (do not open a PR with a bare gh command).
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
# ship — open the PR for the intent of an app repo
The PR is opened through the plugin's core because the core refuses the cases that a bare `gh` command lets through: missing run evidence
(rc 3), standing in the main tree instead of a worktree (rc 5), and — if the repo has `scripts/check-current-state.py` —
a red current-state gate with no exemption line in the PR body (rc 4).
Condition: you stand in a worktree, on the branch `intent/<date>-<slug>`; all child tasks have merged back.
## Do
1. **The current-state ledger.** If the change alters the repo's current state, **overwrite** `kb/current-state.md` in this very PR
so that it matches the state now in force — do not append, do not write a measurement date / PR number / "previously…", do not write how it is done
(push detail to `kb/specs/` or `kb/decisions/`, current-state only points to it). Then run the machine check:
```bash
python3 "${CLAUDE_PLUGIN_ROOT}/scripts/kb.py" check current-state
```
rc `0` is green; rc `65` names each violating line (a history mark, over the cap) — fix until green. A repo with no
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_e4qxgukorxkxbdw3/a8c4c84cdd5db60f0fe490307dde6a0bd46859931f7940411e8cf287bebbd1df.json
Then /plugin install ship@markdownregistry-e4qxgukorxkxbdw3 in Claude Code. It installs git:20261113.9661a88, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add vibemaestro/vibemaestro-kit/ship@sha256:a8c4c84cdd5db60fThe line at the top of this page pins the label git:20261113.9661a88, 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_e4qxgukorxkxbdw3)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in vibemaestro/vibemaestro-kit/ship since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of ship from somewhere else? Ask it: where did my ship come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 22, 2026 and Nov 13, 2026, about one every 6 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261113.9661a88 latest | 2026-11-13 | 9661a88 | 10,024 B | A | view · diff |
| git:20261103.f4a254c | 2026-11-03 | f4a254c | 9,609 B | A | view · diff |
| git:20261031.04472f5 | 2026-10-31 | 04472f5 | 9,043 B | A | view · diff |
| git:20261029.d5142f7 | 2026-10-29 | d5142f7 | 8,525 B | A | view · diff |
| git:20261022.867b0e0 | 2026-10-22 | 867b0e0 | 8,196 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/ship/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (10024 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
vibemaestro/vibemaestro-kit · 4 stars · license Apache-2.0 · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_e4qxgukorxkxbdw3 GET https://markdownregistry.com/api/v1/resolve?ref=vibemaestro/vibemaestro-kit/ship GET https://markdownregistry.com/api/v1/blob/a8c4c84cdd5db60f0fe490307dde6a0bd46859931f7940411e8cf287bebbd1df
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 vibemaestro/vibemaestro-kit
Every file in vibemaestro/vibemaestro-kit