Publishing

SkillFiles & storage

Checks that a Node3D package is ready for npm publishing by auditing its metadata, files, versions, and dependencies.

Use Publishing in Claude, ChatGPT or Ahel Desktop

Free. Sign in, add Publishing and connect your AI. About a minute.

Claude ChatGPT Ahel Desktop

Also: Claude Code · Cursor · Codex

Then ask your AI: use the Publishing skill

Details

Instructions available. Your AI can read the instructions. Execution depends on the setup they require.

Account requirements not reviewed. Check the skill instructions before use; Ahel provides instructions and does not run this skill.

No other account needed.

Add Ahel to your AI once: Claude, ChatGPT, Cursor, Claude Code or Codex. Then ask it to use this.

PublishingStart free

About this skill

Audit or prepare Node3D packages for npm publishing: package metadata, exports/files, versions, lockfiles, npm pack, binary tags/assets, submodule/root release state, and readiness.

What this skill tells your AI

The instructions your AI receives, as published by node-3d/node-3d in .agents/skills/publishing/SKILL.md and read by Ahel’s review.

Owns

Package/release readiness and consistency across standalone package + root superproject state.

This skill does not grant side-effect authority. Re-check root AGENTS.md before commit, push, tag, release, or registry operations.

Workflow

Check affected root/submodule status before release-facing edits.
Determine whether release state affects the package repo, root workspace, or both.
Inspect metadata, exports/files, scripts, dependencies, engines, lockfiles, and native install.js when present.
Run narrow validation first; build before npm pack --dry-run. For native package or consumer validation, use normal npm ci so postinstall-managed binary artifacts are present; --ignore-scripts is metadata-only.
Keep npm package versions decoupled from native binary tags unless native artifacts actually changed.
For package content changes, package commit state precedes the root submodule pointer state.
Before declaring publish-ready, verify requested package/root state is clean, coherent, and synchronized with remotes where required by the task.
Every publishable packages/* package is public by project policy. Require publishConfig.access: public in its manifest and recommend bare npm publish; never add --access public or offer private-package paths. Give authenticated npm commands to the user; do not run them.

Load References

Load .agents/references/publishing-checklist.md for metadata, pack contents, binary-tag decisions, release-state sequencing, or readiness checks.

Load .agents/references/repository-model.md when multiple submodules/workspaces are involved.

Signals

GitHub stars: 66
Forks: 3
Last commit: Oct 2026

Advanced

Item type: skill
Key: publishing-node-3d
Source: github.com/node-3d/node-3d

github.com/node-3d/node-3d