galdr SKILL.md skillA
galdr from nyelonong/galdr is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add nyelonong/galdr/galdr@git:20261119.142bf5ePins git:20261119.142bf5e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- nyelonong/galdr
- Path
skills/galdr/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261119.142bf5e, committed Nov 19, 2026
- First version recorded
- Nov 14, 2026
- Size
- 8,383 bytes
- Repository stars
- 13
- License
- MIT
Use when the user runs /galdr to start or continue a piece of engineering work, or asks which galdr flow fits a request.
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
# galdr galdr is the entry point for engineering work. Pick one playbook, load it, and do its steps to the end. ## 1. Start 1. Before you work in a repository, read `git status` and the remotes. Fetch the upstream if one exists. Never discard work. Never invent an upstream. Never rewrite pushed history. Never force a push. 2. If the runtime has a skill for the main language of the work, load it before you design or edit anything. 3. Pick the playbook: | Request | Playbook | |---|---| | A question, a critique, "what do you think", or anything that is not clearly a change | `investigate` | | New behavior, or a change to existing behavior | `feature` | | Existing behavior that is wrong | `bug` | | Structure or performance pain, with no new behavior | `refactor` | | A design question that throwaway code answers faster than discussion | `prototype` | 4. Write one line: `galdr: <playbook>, <reason>`. Then read `references/playbook-<playbook>.md`, and only that one. If the user names a different playbook, use it. ## 2. Skills that the user calls `shape`, `review` and `handoff` are user-only, so you cannot load them. When a playbook …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_4kxb4m4txdbzfesi/1d32cb26d4f0b7d8b67b08dbce80e8fb963bf1688fbd9c580c2759bc32ee348a.json
Then /plugin install galdr@markdownregistry-4kxb4m4txdbzfesi in Claude Code. It installs git:20261119.142bf5e, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add nyelonong/galdr/galdr@sha256:1d32cb26d4f0b7d8The line at the top of this page pins the label git:20261119.142bf5e, 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_4kxb4m4txdbzfesi)
0 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 nyelonong/galdr/galdr 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 galdr from somewhere else? Ask it: where did my galdr 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 14, 2026 and Nov 19, 2026, about one every day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261119.142bf5e latest | 2026-11-19 | 142bf5e | 8,383 B | A | view · diff |
| git:20261115.1faad52 | 2026-11-15 | 1faad52 | 8,086 B | A | view · diff |
| git:20261114.0740ff1 | 2026-11-14 | 0740ff1 | 7,574 B | A | view · diff |
| git:20261114.fa8b3c3 | 2026-11-14 | fa8b3c3 | 7,612 B | A | view · diff |
| git:20261114.8c6b3b2 | 2026-11-14 | 8c6b3b2 | 5,057 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/galdr/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 (8383 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
nyelonong/galdr · 13 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_4kxb4m4txdbzfesi GET https://markdownregistry.com/api/v1/resolve?ref=nyelonong/galdr/galdr GET https://markdownregistry.com/api/v1/blob/1d32cb26d4f0b7d8b67b08dbce80e8fb963bf1688fbd9c580c2759bc32ee348a
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.