publisher-release
95 / 100 · Low risk
Fine to try.
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.
What this skill can do
Runs commands on your computer
Install
Paste this into your terminal. It downloads exactly the version we scanned, not whatever is newest.
if [ -e ~/.agents/skills/'publisher-release' ] || [ -L ~/.agents/skills/'publisher-release' ]; then echo 'A skill folder named publisher-release already exists — not replacing it' >&2; false; else d=$(mktemp -d) && git clone --quiet --filter=blob:none --no-checkout 'https://github.com/malloydata/publisher' "$d" && git -C "$d" checkout --quiet 'bb8ce0db61c90d45273e4b65c5ccfc6475a9193a' -- '.claude/skills/publisher-release' && mkdir -p ~/.agents/skills && cp -R "$d"/'.claude/skills/publisher-release' ~/.agents/skills/'publisher-release' && rm -rf "$d"; fi
Codex reads ~/.agents/skills directly. For Claude Code, Cursor, Copilot, Gemini CLI, Antigravity or OpenCode, also link it. For Claude Code: ln -s ~/.agents/skills/'publisher-release' ~/.claude/skills/'publisher-release' (other agents: ~/.cursor/skills, ~/.copilot/skills, ~/.gemini/skills, ~/.gemini/config/skills, ~/.config/opencode/skills). Or install through the finder skill, which does both.
Badge for your README
[](https://zalavijaysinh.github.io/skilltrust/repos/malloydata/publisher/)
Score history
| Date | Version | Score |
|---|---|---|
| 2026-11-14 | bb8ce0d | 95 |