feat: ship as npm package via @netresearch/agent-skill-coordinator#19
feat: ship as npm package via @netresearch/agent-skill-coordinator#19
Conversation
Adds a package.json so the skill is npm-installable straight from this GitHub repo (no npm-registry publication required to start). README gains a parallel 'npm (Node Projects)' section under Installation, mirroring the existing 'Composer (PHP Projects)' section. Same pattern applied across the Netresearch skill collection in 2026-05. Coordinator: https://github.com/netresearch/node-agent-skill-coordinator Sibling PRs already merged on git-workflow-skill, github-project-skill, security-audit-skill. Version stays at 0.0.0-source until npm publication is decided separately. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request introduces npm installation support for the GitHub release skill by adding a package.json file and updating the README.md with installation instructions for Node.js projects. A review comment correctly identified that the files allowlist in package.json is missing critical directories, such as .claude-plugin/ and commands/, which are necessary for the skill to function properly when installed via npm.
There was a problem hiding this comment.
Pull request overview
Adds npm install support for this skill repo so Node projects can consume it via @netresearch/agent-skill-coordinator, alongside the existing Composer-based installation approach.
Changes:
- Added a root
package.jsonto make the skill installable via npm directly from the GitHub repo. - Documented npm-based installation (including pnpm postinstall allowlisting guidance) in the README.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| package.json | Introduces npm package metadata, skill discovery pointer (aiAgentSkill), and an npm packing allowlist (files). |
| README.md | Adds an npm installation section describing coordinator-based discovery and pnpm configuration. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
When the skill is installed via npm, only SKILL.md content is registered (via the coordinator's AGENTS.md mechanism). Slash commands and .claude-plugin hooks aren't picked up — those require Claude Code's plugin mechanism. Documenting that so consumers don't expect parity. Signed-off-by: Sebastian Mendel <info@sebastianmendel.de>
Summary
package.jsonso the skill is npm-installable straight from this GitHub repo (no npm-registry publication required to start).How discovery works (consumer side)
After install, the coordinator's
postinstallwalksnode_modules, finds this package viaaiAgentSkill: skills/github-release/SKILL.md, validates the frontmatter, and writes a<skills_system>block into the project'sAGENTS.md. Same shape as the Composer plugin's output.filesallowlisthooks/is included so Claude Code marketplace consumers still get the guard hooks. There's no top-levelscripts/directory in this repo — the skill's scripts live insideskills/github-release/scripts/and are automatically shipped viaskills/github-release/.Why version stays at
0.0.0-sourceVersioning still lives in git tags and the existing Composer release workflow. A real npm version would be set at publish time; until then,
0.0.0-sourceis the standard "this manifest exists for tooling, not as a release marker" placeholder.Sibling PRs (merged)
Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (
@netresearch/agent-skill-coordinator@0.1.2)