feat: ship as npm package via @netresearch/agent-skill-coordinator by CybotTM · Pull Request #67 · netresearch/github-project-skill

CybotTM · 2026-05-02T08:37:20Z

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)

After installing the coordinator + this package, the coordinator's postinstall walks node_modules, finds this package via the aiAgentSkill field, validates the frontmatter, and writes a <skills_system> block into the projects AGENTS.md. Same shape as the Composer plugin output, so any agent that reads either works here unchanged.

Why version stays at `0.0.0-source`

Versioning still lives in git tags and the existing release workflow. A real npm version would be set at publish time; until then, 0.0.0-source is the placeholder that signals "manifest exists for tooling, not as a release marker."

Sibling PRs

Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (released as @netresearch/agent-skill-coordinator@0.1.1)
git-workflow-skill: feat: ship as npm package via @netresearch/agent-skill-coordinator git-workflow-skill#39

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 to git-workflow-skill (PR #39) and on the coordinator side at netresearch/node-agent-skill-coordinator. Version stays at 0.0.0-source until npm publication is decided separately. Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>

github-actions · 2026-05-02T08:37:35Z

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

gemini-code-assist

Code Review

This pull request introduces npm support for the GitHub project skill by adding a package.json file and updating the README.md with installation instructions. A review comment suggests including AGENTS.md and the docs/ directory in the package.json files list to ensure the package is fully documented when installed.

Copilot

Pull request overview

This PR adds a Node/npm distribution path for the existing GitHub project skill so Node-based consumers can install it directly from this repository and have it discovered by @netresearch/agent-skill-coordinator, alongside the existing Composer-based distribution.

Changes:

Add a root package.json that exposes the skill via the custom aiAgentSkill manifest field for Node consumers.
Declare the coordinator as a peer dependency and limit packaged files to the skill content and licensing/docs files.
Document npm-based installation in README.md, including pnpm postinstall allowlisting guidance.

Reviewed changes

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

File	Description
`package.json`	Adds npm package metadata so the skill can be installed from GitHub and discovered by the Node coordinator.
`README.md`	Documents the new npm installation flow and pnpm-specific setup requirements.

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

## 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** section. ## How discovery works (consumer side) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/agent-harness-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/agent-harness/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/file-search-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/file-search/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/enterprise-readiness-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/enterprise-readiness/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/matrix-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/matrix-communication/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/german-technical-writing-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/german-technical-writing/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

) ## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/jira-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/jira-communication/SKILL.md, skills/jira-syntax/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/netresearch-branding-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/netresearch-branding/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`) ## Note: `assets/` in `files` allowlist `skills/netresearch-branding/SKILL.md:24` references `assets/logos/netresearch-symbol-only.svg` (the repo-root `assets/` directory, not a nested one inside the skill folder). To keep the SKILL.md reference valid for npm consumers, `assets/` is included alongside `scripts/` in the `files` allowlist.

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/data-tools-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/data-tools/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/context7-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/context7/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/concourse-ci-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/concourse-ci/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/cli-tools-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/cli-tools/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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 **Via Composer** section. ## How discovery works (consumer side) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/markdown-to-pdf-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/markdown-to-pdf/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

## 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 new **Installation** section with **Composer (PHP Projects)** and **npm (Node Projects)** subsections, matching the rest of the Netresearch skill collection. The previous README had no Installation section at all. ## How discovery works (consumer side) ```bash npm install --save-dev \ @netresearch/agent-skill-coordinator \ github:netresearch/peer-qa-review-skill ``` After install, the coordinator's `postinstall` walks `node_modules`, finds this package via `aiAgentSkill: skills/peer-qa-review/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) - netresearch/git-workflow-skill#39 - netresearch/github-project-skill#67 - netresearch/security-audit-skill#67 Coordinator: https://github.com/netresearch/node-agent-skill-coordinator (`@netresearch/agent-skill-coordinator@0.1.2`)

Copilot AI review requested due to automatic review settings May 2, 2026 08:37

Copilot started reviewing on behalf of CybotTM May 2, 2026 08:37 View session

CybotTM merged commit 24dcbf8 into main May 2, 2026
13 checks passed

CybotTM deleted the feat/npm-install branch May 2, 2026 08:38

gemini-code-assist Bot reviewed May 2, 2026

View reviewed changes

Comment thread package.json

Copilot AI reviewed May 2, 2026

View reviewed changes

Comment thread package.json

Comment thread README.md

CybotTM mentioned this pull request May 2, 2026

feat(templates): bake npm package.json defaults to prevent retrofit drift netresearch/skill-repo-skill#83

Merged

3 tasks

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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

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

CybotTM commented May 2, 2026

Uh oh!

github-actions Bot commented May 2, 2026

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Uh oh!

Uh oh!

Copilot AI left a comment

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

CybotTM commented May 2, 2026

Summary

How discovery works (consumer side)

Why version stays at 0.0.0-source

Sibling PRs

Uh oh!

github-actions Bot commented May 2, 2026

Dependency Review

Scanned Files

Uh oh!

Uh oh!

gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

Code Review

Uh oh!

Uh oh!

Copilot AI left a comment

Choose a reason for hiding this comment

Pull request overview

Reviewed changes

Uh oh!

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Why version stays at `0.0.0-source`