ship SKILL.md skillB
ship from caligrafy/caligrafy-quill is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add caligrafy/caligrafy-quill/ship@git:20261108.1de0256Pins git:20261108.1de0256 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- caligrafy/caligrafy-quill
- Path
claude-plugin/skills/ship/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261108.1de0256, committed Nov 8, 2026
- First version recorded
- Nov 3, 2026
- Size
- 10,504 bytes
- Repository stars
- 9
- License
- MIT
Put the current Caligrafy Quill project online at https://<name>.caligrafy.com without handing the work to the user - commit, create the GitHub repository and push (SSH first, then HTTPS, then a browser approval), sign in to Caligrafy Cloud with a browser approval (no token to copy), create the app, add its deploy key, deploy and check it. The user only approves in the browser and says yes before credits are spent.
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: from the code on this computer to an application online Target: `$ARGUMENTS` (the app name, which is also the GitHub repository name and `https://<name>.caligrafy.com`; the project folder's name when empty; `--public` for a public repository, private by default). **Do everything yourself.** The user is never asked to run a command, copy a key or a token, or come back and say "done". What only they can do happens in their browser, opened for them: approving GitHub's code, approving Caligrafy Cloud's code, signing up and confirming their email the first time, paying for credits. Tell them in one line what the page will ask, open it, and keep going as soon as it is approved (the commands wait for it themselves). The one question you ask is before spending credits. Never ask for, print or write a password, token or key, and never read `.caligrafy/cloud.json`. Never pipe a command whose result matters through `tail` or `head`: the pipe hides its exit code (G89); run it whole, in the background when it is long, and read its output file. Two places run commands: + **this computer** for git and GitHub (the SSH keys, the GitHub CLI and the browser are here): …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_dpcstwqslfllcchc/f69c825813e65c2bce4114ecbc387cc035ca3b82c5585c7c713ee91bd3404ac7.json
Then /plugin install ship@markdownregistry-dpcstwqslfllcchc in Claude Code. It installs git:20261108.1de0256, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add caligrafy/caligrafy-quill/ship@sha256:f69c825813e65c2bThe line at the top of this page pins the label git:20261108.1de0256, 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_dpcstwqslfllcchc)
1 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 caligrafy/caligrafy-quill/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 Nov 3, 2026 and Nov 8, 2026, about one every day. Its first recorded version is graded A and its latest B.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.1de0256 latest | 2026-11-08 | 1de0256 | 10,504 B | B | view · diff |
| git:20261108.89427fb | 2026-11-08 | 89427fb | 10,290 B | B | view · diff |
| git:20261107.75dd463 | 2026-11-07 | 75dd463 | 9,504 B | A | view · diff |
| git:20261103.a75b33c | 2026-11-03 | a75b33c | 9,109 B | A | view · diff |
| git:20261103.ce268b6 | 2026-11-03 | ce268b6 | 8,853 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
- fail: No instruction to read or print local credentials (matched: print nothing (.env)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (10504 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 base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
caligrafy/caligrafy-quill · 9 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_dpcstwqslfllcchc GET https://markdownregistry.com/api/v1/resolve?ref=caligrafy/caligrafy-quill/ship GET https://markdownregistry.com/api/v1/blob/f69c825813e65c2bce4114ecbc387cc035ca3b82c5585c7c713ee91bd3404ac7
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 caligrafy/caligrafy-quill
Every file in caligrafy/caligrafy-quill