Cutting A Release
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one.
$ npx skills add hashintel/hash --skill publishing-packages -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install hashintel/hash publishing-packages --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/publishing-packages .claude/skills/publishing-packages && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .claude/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packagesType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add hashintel/hash --skill publishing-packages -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install hashintel/hash publishing-packages --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/publishing-packages .agents/skills/publishing-packages && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .agents/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashintel/hash --skill publishing-packages -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install hashintel/hash publishing-packages --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/publishing-packages .cursor/skills/publishing-packages && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .cursor/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/hashintel/hash.git --path .agents/skills/publishing-packages--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add hashintel/hash --skill publishing-packages -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install hashintel/hash publishing-packages --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/publishing-packages .gemini/skills/publishing-packages && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .gemini/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install hashintel/hash publishing-packagesInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add hashintel/hash --skill publishing-packages -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/publishing-packages .github/skills/publishing-packages && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .github/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add hashintel/hash --skill publishing-packages -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install hashintel/hash publishing-packages --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/hashintel/hash.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/publishing-packages .opencode/skills/publishing-packages && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "publishing-packages" agent skill from https://github.com/hashintel/hash/tree/main/.agents/skills/publishing-packages into .opencode/skills/publishing-packages/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "publishing-packages", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
publishing-packagesConventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one.
Publishing Packages is an agent skill from hashintel/hash. Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one. Use when adding or editing a changeset, versioning or releasing a package, or deciding whether a change to a publishable library needs a changelog entry.
Its SKILL.md is about 440 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Development, covering Changelog and release notes. It works with npm. The repository describes itself as: 🚀 The open-source, multi-tenant platform for self-building knowledge graphs and simulation. The licence is AGPL-3.0.
Read from SKILL.md and the folder at commit 1fa0c7b. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Publishing Packages loads about 443 tokens when it runs. Until then it costs about 74 tokens; SKILL.md has 145 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from hashintel/hash at commit 1fa0c7b, republished under its AGPL-3.0 licence (© hashintel). 145 words, ~443 tokens.
.claude/skills/publishing-packages/SKILL.md (or your agent's skills folder).npm-publishable packages in this repository are versioned and released with changesets. The changeset configuration, including which packages are ignored, lives in .changeset/config.json.
A PR that changes an npm-publishable package adds a changeset file under .changeset/. The changeset text becomes the package's published changelog entry, so write it for the package's consumers:
A package's own AGENTS.md can carry further conventions, such as the bump level it accepts; check it before writing the changeset.
© hashintel, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .agents/skills/publishing-packages of hashintel/hash.
Open the folder on GitHubat commit 1fa0c7b
Publishing Packages next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Publishing Packages this skillhashintel/hash | 1.7k | — | ~443 | Automated safety check: Pass | AGPL-3.0 | |
| Cutting A ReleaseTriliumNext/Trilium | 38k | — | ~3.2k | Automated safety check: Pass | AGPL-3.0 | |
| Verdaccio Pull Request Workflowverdaccio/verdaccio | 18k | — | ~1.9k | Automated safety check: Pass | MIT | |
| Version ReleaseNG-ZORRO/ng-zorro-antd | 9.2k | — | ~3.1k | Automated safety check: Pass | MIT | |
| AionUi Version BumpiOfficeAI/AionUi | 33k | — | ~2.1k | Automated safety check: Pass | Apache-2.0 | |
| Hunk Release Workflowmodem-dev/hunk | 9.5k | — | ~3.8k | Automated safety check: Pass | MIT |
TriliumNext/Trilium
A skill your agent uses when cutting, preparing, or debugging a Trilium release — bumping the monorepo version, tagging, or diagnosing a failed "Release" workflow run.
verdaccio/verdaccio
Takes a change through a verdaccio pull request: branch, local checks, changeset, title and body, labels, CI and review rounds, and ports to other release lines.
NG-ZORRO/ng-zorro-antd
NG-ZORRO/ng-zorro-antd repository release workflow. An agent skill from NG-ZORRO/ng-zorro-antd.
iOfficeAI/AionUi
Automates an AionUi release: checks the latest AionCore release and its artifacts, updates package.json, writes the changelog, opens a PR and tags the release.
modem-dev/hunk
Maintainer workflow for preparing, publishing, verifying and curating Hunk releases, with confirmation gates before tags, publishes and public edits.
ethereumjs/ethereumjs-monorepo
Runs a coordinated EthereumJS npm release round in six human-gated phases — intent and readiness, CHANGELOG, version bump, publish (human executes), post-publish verification, and announcements.
hashintel/hash
Rust documentation practices for HASH codebase. An agent skill from hashintel/hash.
hashintel/hash
HASH error handling patterns using error-stack crate. An agent skill from hashintel/hash.
hashintel/hash
Cargo.toml dependency management patterns for HASH workspace.
hashintel/hash
HashQL testing strategies including compiletest (UI tests), unit tests, and snapshot tests.
hashintel/hash
HashQL diagnostic writing patterns using hashql-diagnostics crate.
hashintel/hash
HashQL J-Expr syntax for writing queries. An agent skill from hashintel/hash.
Works with
Categories
Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one. Publishing Packages is an agent skill from hashintel/hash. Conventions for publishing npm packages from this repository, including when a PR needs a changeset and how to write one.
Publishing Packages fits situations like: editing a changeset; releasing a package; deciding whether a change to a publishable library needs a changelog entry.
Run `npx skills add hashintel/hash --skill publishing-packages -a claude-code`. Or copy the skill folder (.agents/skills/publishing-packages in hashintel/hash) into .claude/skills/publishing-packages in your project. Claude Code loads it when a task matches its description.
Run `npx skills add hashintel/hash --skill publishing-packages -a codex`. Or copy the skill folder (.agents/skills/publishing-packages in hashintel/hash) into .agents/skills/publishing-packages in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add hashintel/hash --skill publishing-packages -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/publishing-packages, .gemini/skills/publishing-packages, .github/skills/publishing-packages and .opencode/skills/publishing-packages in your project.
SKILL.md names no scripts, command-line tools or credentials: Publishing Packages is instructions for the agent only.
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Publishing Packages is published under the AGPL-3.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 443 tokens (SKILL.md is roughly 1.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Publishing Packages: Cutting A Release (TriliumNext/Trilium, 38k stars), Verdaccio Pull Request Workflow (verdaccio/verdaccio, 18k stars), Version Release (NG-ZORRO/ng-zorro-antd, 9.2k stars) and AionUi Version Bump (iOfficeAI/AionUi, 33k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
hashintel (a GitHub organization) maintains it in hashintel/hash, which has 1,668 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 8, 2026.
Source: hashintel/hash on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.