publisher-release SKILL.md skillA

publisher-release from malloydata/publisher is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add malloydata/publisher/publisher-release@git:20261116.3b6d4a1

Pins git:20261116.3b6d4a1 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
malloydata/publisher
Path
.claude/skills/publisher-release/SKILL.md
Versions recorded
7
Latest version
git:20261116.3b6d4a1, committed Nov 16, 2026
First version recorded
Sep 28, 2026
Size
29,344 bytes
Repository stars
133
License
MIT

Cut a Malloy Publisher release, and write the RELEASE_NOTES.md entries a release ships. Use when asked to release, cut a release, ship a version, or publish Publisher to npm/Docker — and when a change needs a release note, or you are deciding whether it does and what version to stamp on it.

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
-->

# Releasing Publisher

A release is one `workflow_dispatch` of `Release (NPM + Docker + PyPI)`
(`.github/workflows/release.yml`), followed by one pull request: the
`release/v<version>` branch the release published from, merged back into
`main`. That branch already carries the version bump and the stamped release
notes, so **you never create a branch or stamp anything by hand**. You open the
PR from the branch the workflow pushed.

Read `.github/workflows/CONTEXT.md` (path from the repo root) before acting. It carries the publishing rules that are not guessable from the
YAML, and it is the authority when this file and it disagree.

## Release notes: when to write one, and what number goes on it

`RELEASE_NOTES.md` is not written at release time. **The PR that changes the
behaviour writes the note**, in the same PR, as a `## [Unreleased]` section —
which is the only way it gets written by someone who knows what changed. The
release then carries it to users on its own: `prepare` stamps every
`[Unreleased]` heading with the release's version on the release branch, and
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_l52ck2jd6vk3kur3/bc01145324536ee7ee37e110a53725c2d129a3eff4bc410b526a7e17cc453003.json

Then /plugin install publisher-release@markdownregistry-l52ck2jd6vk3kur3 in Claude Code. It installs git:20261116.3b6d4a1, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add malloydata/publisher/publisher-release@sha256:bc01145324536ee7

The line at the top of this page pins the label git:20261116.3b6d4a1, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_l52ck2jd6vk3kur3.svg)](https://markdownregistry.com/a/art_l52ck2jd6vk3kur3)

2 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in malloydata/publisher/publisher-release 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 publisher-release from somewhere else? Ask it: where did my publisher-release 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 7 versions of this file, between Sep 28, 2026 and Nov 16, 2026, about one every 8 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261116.3b6d4a1 latest2026-11-16 3b6d4a1 29,344 BA view · diff
git:20261114.50b4f892026-11-14 50b4f89 28,104 BA view · diff
git:20261103.f38828a2026-11-03 f38828a 27,545 BA view · diff
git:20261029.e0035b52026-10-29 e0035b5 27,538 BA view · diff
git:20261008.60767d12026-10-08 60767d1 27,936 BA view · diff
git:20260929.c5cf71d2026-09-29 c5cf71d 29,057 BA view · diff
git:20260928.0bdcd702026-09-28 0bdcd70 28,701 BA view
Keep it current by itself, install once

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.

Install on GitHub

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.

Keep it current by itself

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.

Check a whole project

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

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (29344 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

GitHub

malloydata/publisher · 133 stars · license MIT · pushed 2026-11-17 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_l52ck2jd6vk3kur3
GET https://markdownregistry.com/api/v1/resolve?ref=malloydata/publisher/publisher-release
GET https://markdownregistry.com/api/v1/blob/bc01145324536ee7ee37e110a53725c2d129a3eff4bc410b526a7e17cc453003

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 malloydata/publisher

fix-scan-finding SKILL.md skill
malloydata/publisher · .claude/skills/fix-scan-finding/SKILL.md · Fix a CRITICAL Trivy finding that is failing CI in this repo (a vulnerability, misconfiguration, or secret from…
git:20261001.a42ad3a · audit A · 133 stars
AGENTS.md AGENTS.md file
malloydata/publisher · AGENTS.md
git:20261117.320a806 · audit B · 133 stars
CLAUDE.md CLAUDE.md file
malloydata/publisher · CLAUDE.md
git:20261116.660817a · audit B · 133 stars
AGENTS.md@examples/html-data-app AGENTS.md file
malloydata/publisher · examples/html-data-app/AGENTS.md
git:20261105.0bd58a0 · audit B · 133 stars
analyst-conventions SKILL.md skill
malloydata/publisher · examples/storefront/agents/analyst/skills/analyst-conventions/SKILL.md · House conventions for revenue questions on the storefront package. Read before answering any revenue, sales, or…
git:20261012.9b94813 · audit A · 133 stars
malloy-phrase-detection SKILL.md skill
malloydata/publisher · examples/storefront/skills/malloy-phrase-detection/SKILL.md · How to turn a storefront question into get_context search targets, including the shop vocabulary that does not appear…
git:20261012.9b94813 · audit A · 133 stars
storefront-conventions SKILL.md skill
malloydata/publisher · examples/storefront/skills/storefront-conventions/SKILL.md · What storefront's measures actually count, and the four places a reasonable reading of them is wrong. Read before…
git:20261012.9b94813 · audit A · 133 stars
AGENTS.md@packages/create-malloy-package/templates AGENTS.md file
malloydata/publisher · packages/create-malloy-package/templates/AGENTS.md
git:20261111.2af71bc · audit A · 133 stars
conventions SKILL.md skill
malloydata/publisher · packages/server/tests/fixtures/skills-agents-test/agents/analyst/skills/conventions/SKILL.md · House rules for the analyst.
git:20261012.9b94813 · audit B · 133 stars
house-rules SKILL.md skill
malloydata/publisher · packages/server/tests/fixtures/skills-agents-test/skills/house-rules/SKILL.md · How this package defines its terms.
git:20261012.9b94813 · audit B · 133 stars
malloy-analysis SKILL.md skill
malloydata/publisher · packages/server/tests/fixtures/skills-agents-test/skills/malloy-analysis/SKILL.md · The package's own analysis guide.
git:20261012.9b94813 · audit B · 133 stars
eval-answer SKILL.md skill
malloydata/publisher · skills/eval-answer/SKILL.md · Score one analytical answer against a verified golden, and score which of the entities the golden depends on retrieval…
git:20261106.0413358 · audit A · 133 stars

Every file in malloydata/publisher

Browse by kind, by grade A, or by owner.