ship-it SKILL.md skillA
ship-it from adamlinscott/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add adamlinscott/claude-skills/ship-it@git:20261008.fda8754Pins git:20261008.fda8754 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- adamlinscott/claude-skills
- Path
skills/ship-it/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261008.fda8754, committed Oct 8, 2026
- First version recorded
- Aug 28, 2026
- Size
- 8,728 bytes
- Repository stars
- 4
- License
- MIT
[Adam''s Skills] Get the work done in this conversation all the way out — merged, and deployed to every environment the repo has, production included. Grounds itself first in the branches written during this session, the open and closed PRs behind them, and the environments and CI/CD workflows the repo actually defines, then lands and releases the work and verifies each environment is running the commit. If the release would carry other people''s unreleased changes along with it, summarises…
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 It The work of this conversation is finished, or the user thinks it is. Your job is to get it **all the way out** — merged, released, and running in every environment this repo deploys to, production included — and to prove it got there rather than assume it did. Two failure modes to hold in mind. The first is stopping early: a merged PR is not a shipped change, and a green deploy job is not proof the environment is running your commit. The second is shipping more than the user knows about: on most repos a release carries everything sitting unreleased on the target branch, which can include work by other people and other agent sessions. Section 4 exists entirely for that. ## 1. Ground yourself before doing anything Take no action until you can name, from evidence, all four of these. Read; do not recall. **The work.** What this session actually produced — the branches you created or committed to, and the commits on them. If the session is long or compacted and you cannot reconstruct it confidently, do not guess: check `git log --author` for the configured user, recent branches (`git branch --sort=-committerdate`), and the current branch, and state which of it you are …
Read the whole file at its exact version.
How to install
mdr add adamlinscott/claude-skills/ship-it@sha256:71497f3accece4cdThe line at the top of this page pins the label git:20261008.fda8754, 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_b45qirrmo2gjly7r)
6 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Aug 28, 2026 and Oct 8, 2026, about one every 8 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.fda8754 latest | 2026-10-08 | fda8754 | 8,728 B | A | view · diff |
| git:20260911.623fe4a | 2026-09-11 | 623fe4a | 8,401 B | A | view · diff |
| git:20260910.7e7f462 | 2026-09-10 | 7e7f462 | 8,398 B | A | view · diff |
| git:20260830.1896f40 | 2026-08-30 | 1896f40 | 8,384 B | A | view · diff |
| git:20260830.9892229 | 2026-08-30 | 9892229 | 8,195 B | A | view · diff |
| git:20260828.f12d1d0 | 2026-08-28 | f12d1d0 | 7,187 B | A | view |
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 (8728 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
adamlinscott/claude-skills · 4 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b45qirrmo2gjly7r GET https://markdownregistry.com/api/v1/resolve?ref=adamlinscott/claude-skills/ship-it GET https://markdownregistry.com/api/v1/blob/71497f3accece4cdd8334caead9a00fb7775edd720f8aa2051b4d90aacd66025
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 adamlinscott/claude-skills
Every file in adamlinscott/claude-skills