new-resource SKILL.md skillA
new-resource 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/new-resource@git:20261108.a1af143Pins git:20261108.a1af143 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- caligrafy/caligrafy-quill
- Path
claude-plugin/skills/new-resource/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261108.a1af143, committed Nov 8, 2026
- First version recorded
- Nov 7, 2026
- Size
- 12,678 bytes
- Repository stars
- 9
- License
- MIT
Scaffold a Caligrafy Quill resource capabilities-first - MySQL create_db.sql script, Caligrafy\Model, the CRUD capabilities (list, get, create, update, delete) written once with php caligrafer.php service, their REST routes (Route::capability), pages with Route::page and forms with Route::form (2.19.0+), lists with the query builder - following the framework conventions (only capabilities touch models).
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
# Scaffold a Caligrafy resource Arguments: `$ARGUMENTS` (entity name, then optional `field:type` pairs; `name:fk` = foreign key to model `Name`). If fields are missing, infer sensible ones from the conversation or ask once. Read first: the `caligrafy` skill's [api-reference.md](../caligrafy/reference/api-reference.md) (Model, Route, Build once, Queries, Declarative routes) and [gotchas.md](../caligrafy/reference/gotchas.md) G2, G4, G6, G7, G10, G19, G23, G52, G76, G83, G122-G131, G138, G139. **Only capabilities touch models**: the model is read and written by the capabilities of this resource, never by a controller or a page. Pages get their data with `Route::page`, forms post with `Route::form` (2.19.0+), exports use `Route::download`, anything else is `Route::action` on a `webOnly: true` capability (2.21.0+, G143): no controller. **The people who sign in are not a new resource**: the `users` table, the `User` model and the user capabilities ship with the authentication module. When the entity is an account, or the user wants people to sign in with an email, do not add a table or an …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_fq23rniqfeegdx43/68e9cfc5c44eacd65007a5efec2ba5bf5ffba0378a13b121e8b0f8f5b9b1748b.json
Then /plugin install new-resource@markdownregistry-fq23rniqfeegdx43 in Claude Code. It installs git:20261108.a1af143, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add caligrafy/caligrafy-quill/new-resource@sha256:68e9cfc5c44eacd6The line at the top of this page pins the label git:20261108.a1af143, 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_fq23rniqfeegdx43)
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/new-resource 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 new-resource from somewhere else? Ask it: where did my new-resource 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 8, 2026, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261108.a1af143 latest | 2026-11-08 | a1af143 | 12,678 B | A | view · diff |
| git:20261108.c00811d | 2026-11-08 | c00811d | 12,265 B | A | view · diff |
| git:20261108.64dc062 | 2026-11-08 | 64dc062 | 12,879 B | A | view · diff |
| git:20261108.89427fb | 2026-11-08 | 89427fb | 11,667 B | A | view · diff |
| git:20261107.579343e | 2026-11-07 | 579343e | 9,723 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/new-resource/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 (12678 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
caligrafy/caligrafy-quill · 9 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_fq23rniqfeegdx43 GET https://markdownregistry.com/api/v1/resolve?ref=caligrafy/caligrafy-quill/new-resource GET https://markdownregistry.com/api/v1/blob/68e9cfc5c44eacd65007a5efec2ba5bf5ffba0378a13b121e8b0f8f5b9b1748b
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.