malloy-source-unreachable SKILL.md skillA
malloy-source-unreachable from malloydata/publisher is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add malloydata/publisher/malloy-source-unreachable@git:20261014.c3aabaePins git:20261014.c3aabae in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- malloydata/publisher
- Path
skills/malloy-source-unreachable/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261014.c3aabae, committed Oct 14, 2026
- First version recorded
- Sep 30, 2026
- Size
- 8,619 bytes
- Repository stars
- 133
- License
- MIT
Work out why a source is missing from get_context, or why a query against it was refused with a 404 or a 403, and what to do next. Use when a source you expect is absent from discovery, when execute_query answers "No queryable source", when a query that used to work stops working, or when deciding whether a package's curation is hiding something you need.
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
<!-- Copyright (c) Credible Data Inc. SPDX-License-Identifier: MIT -->
# A source you cannot reach
> **Tool names** are written bare here - `get_context`, `execute_query`, `get_status`, `compile_model`. The exact prefixed name depends on the host surface; match each against the tools you actually have.
Most packages publish a curated surface, so a source being absent or refused is usually the package working as its author intended, not a fault. Read the refusal before working around it, because the three things that can refuse you need three different responses and they are told apart by the status code.
## The three answers
| what you got | what it means | what to do |
| --- | --- | --- |
| **404** that says "not on this package's published surface" | the name is real and the package does not publish it. It is curation, not a typo | follow the fix the message names (usually: name it in the `export { ... }` of `index.malloy` and address the query there), or query what IS published |
…Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_b4c6hmejouzumxlv/0cba78bb46cd37698b9b986728276e3109defe2fe4560e7a7259f2443a776b25.json
Then /plugin install malloy-source-unreachable@markdownregistry-b4c6hmejouzumxlv in Claude Code. It installs git:20261014.c3aabae, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add malloydata/publisher/malloy-source-unreachable@sha256:0cba78bb46cd3769The line at the top of this page pins the label git:20261014.c3aabae, 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_b4c6hmejouzumxlv)
2 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 malloydata/publisher/malloy-source-unreachable 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 malloy-source-unreachable from somewhere else? Ask it: where did my malloy-source-unreachable 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 Sep 30, 2026 and Oct 14, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.c3aabae latest | 2026-10-14 | c3aabae | 8,619 B | A | view · diff |
| git:20261012.55216ae | 2026-10-12 | 55216ae | 8,825 B | A | view · diff |
| git:20261006.ff75382 | 2026-10-06 | ff75382 | 8,800 B | A | view · diff |
| git:20261006.b60270d | 2026-10-06 | b60270d | 8,888 B | A | view · diff |
| git:20260930.8321814 | 2026-09-30 | 8321814 | 8,718 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/malloy-source-unreachable/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 (8619 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
malloydata/publisher · 133 stars · license MIT · pushed 2026-11-17 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b4c6hmejouzumxlv GET https://markdownregistry.com/api/v1/resolve?ref=malloydata/publisher/malloy-source-unreachable GET https://markdownregistry.com/api/v1/blob/0cba78bb46cd37698b9b986728276e3109defe2fe4560e7a7259f2443a776b25
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.