deploy SKILL.md skillB
deploy 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/deploy@git:20261115.faa2abaPins git:20261115.faa2aba 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/deploy/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261115.faa2aba, committed Nov 15, 2026
- First version recorded
- Nov 7, 2026
- Size
- 10,455 bytes
- Repository stars
- 9
- License
- MIT
Put a Caligrafy Quill project online - check it is ready for production (Dockerfile, composer.lock, create_db.sql scripts safe to run again, no secrets in git, pushed to GitHub), then deploy it to Caligrafy Cloud (https://<name>.caligrafy.com) with php caligrafer.php cloud, or prepare it for the user's own server (Coolify, Docker).
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
# Put a Caligrafy project online Target: `$ARGUMENTS` (an app name for Caligrafy Cloud; `--own-server` to prepare the project for Coolify or Docker instead). Read [20-putting-it-online.md](../caligrafy/reference/20-putting-it-online.md), gotchas G67-G73 in [gotchas.md](../caligrafy/reference/gotchas.md), and the `deploy` and `cloud` rows of the CLI table in [api-reference.md](../caligrafy/reference/api-reference.md). Needs Caligrafy Quill 2.4.0+ (`php caligrafer.php version`). ## 1. Is the project ready? (read-only, report every point) ```bash php caligrafer.php version # 2.4.0 or later; older: upgrade first (release notes 2.4.0) ls Dockerfile Dockerfile.dockerignore composer.lock git status --short && git log origin/HEAD..HEAD --oneline 2>/dev/null # uncommitted or unpushed work git remote get-url origin # a GitHub repository git ls-files | grep -E '(^|/)\.env($|\.)' | grep -v '\.env\.example$' | grep -v '^framework/settings/' # must print nothing (.env.php too, 2.19.0+) php caligrafer.php doctor --only project ``` …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_5t6eecajytebwxls/a456306bf1d35e32006868198ec33d7b41f3fd9972823e053c0a1b4898534e2b.json
Then /plugin install deploy@markdownregistry-5t6eecajytebwxls in Claude Code. It installs git:20261115.faa2aba, the one graded B here, pinned to the commit it was graded at, and leaves it there.
mdr add caligrafy/caligrafy-quill/deploy@sha256:a456306bf1d35e32The line at the top of this page pins the label git:20261115.faa2aba, 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_5t6eecajytebwxls)
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/deploy 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 deploy from somewhere else? Ask it: where did my deploy 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 7, 2026 and Nov 15, 2026, about one every 2 days. 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:20261115.faa2aba latest | 2026-11-15 | faa2aba | 10,455 B | B | view · diff |
| git:20261115.3de1aab | 2026-11-15 | 3de1aab | 10,426 B | B | view · diff |
| git:20261108.1de0256 | 2026-11-08 | 1de0256 | 9,832 B | B | view · diff |
| git:20261108.89427fb | 2026-11-08 | 89427fb | 9,799 B | B | view · diff |
| git:20261107.579343e | 2026-11-07 | 579343e | 8,948 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/deploy/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 (10455 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_5t6eecajytebwxls GET https://markdownregistry.com/api/v1/resolve?ref=caligrafy/caligrafy-quill/deploy GET https://markdownregistry.com/api/v1/blob/a456306bf1d35e32006868198ec33d7b41f3fd9972823e053c0a1b4898534e2b
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