Skip to content

feat: ship as npm package via @netresearch/agent-skill-coordinator#46

Merged
CybotTM merged 1 commit intomainfrom
feat/npm-install
May 2, 2026
Merged

feat: ship as npm package via @netresearch/agent-skill-coordinator#46
CybotTM merged 1 commit intomainfrom
feat/npm-install

Conversation

@CybotTM
Copy link
Copy Markdown
Member

@CybotTM CybotTM commented May 2, 2026

Summary

  • Adds 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.

How discovery works (consumer side)

npm install --save-dev \
  @netresearch/agent-skill-coordinator \
  github:netresearch/agent-rules-skill

After install, the coordinator's postinstall walks node_modules, finds this package via aiAgentSkill: skills/agent-rules/SKILL.md, validates the frontmatter, and writes a <skills_system> block into the project's AGENTS.md. Same shape as the Composer plugin's output.

Why version stays at 0.0.0-source

Versioning 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-source is 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)

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>
Copilot AI review requested due to automatic review settings May 2, 2026 09:29
Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces npm support for the agent rules skill by adding a package.json file and updating the README.md with installation and configuration instructions for Node.js projects. Feedback was provided regarding the files array in package.json, noting that several entries for scripts and license files appear to be redundant or point to incorrect paths, which could cause warnings during package installation.

Comment thread package.json
Copy link
Copy Markdown

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR makes the skill consumable as a GitHub-installed npm package (discovered via @netresearch/agent-skill-coordinator) and documents the Node installation flow alongside the existing Composer flow.

Changes:

  • Add a root package.json that exposes the skill via aiAgentSkill and limits packed contents via files.
  • Extend README.md installation instructions with an npm section (including a pnpm postinstall allowlist note).

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
package.json Defines the npm package metadata and exposes the skill entrypoint for coordinator discovery.
README.md Documents npm-based installation/discovery flow for Node projects.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@CybotTM CybotTM merged commit 3455da2 into main May 2, 2026
13 checks passed
@CybotTM CybotTM deleted the feat/npm-install branch May 2, 2026 10:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants