neo-agent-skills

neomjs/neo-agent-skills is an open-source project by neomjs: Install the workflow substrate a cross-model AI team actually runs on: ticket intake, PR review gates, lane coordination and guards, versioned as a package. The skills Neo.mjs maintainers load every session — materialized into your repo, not copied.. Indexed here so it can be found — not resold.

It is free. Get it from the upstream repository: https://github.com/neomjs/neo-agent-skills

From the project's own README (excerpt, reproduced for discovery under its MIT license):

neo-agent-skills

The canonical agent skill substrate for the neomjs organization. Consuming repositories depend on this package; they never carry a copy of it.

How it reaches a repository

Then run the materializer from your postinstall:

postinstall materializes two surfaces, both as symlinks into nodemodules, both untracked:

surface shape for --- --- --- .agents/skills one directory symlink at the whole tree harness-neutral discovery — Codex, Antigravity, any fork .claude/skills per-skill links, manifest-projected the Claude façade

The shapes differ on purpose. The manifest may opt a skill out of the Claude façade, and you cannot opt a skill out of a directory symlink — so the neutral surface links the tree and the façade links each skill. Git-ignore both paths; a tracked entry under either is a shadow copy, which is the thing this package exists to make unnecessary.

Maintainer pull requests bump this package's version and publish on merge. Dependabot pull requests retain the package version and run validation without publishing or tagging (see Authority). Consumers update the dependency like any other. Freshness is whatever npm already tells you — npm outdated, dependabot — and there is deliberately no bespoke lag gate anywhere in this contract.

The check that matters

Run it in consumer CI. It answers the questions this transport leaves open: did both projections happen, and does every link point where it should? Existence is not correctness — a link resolving to the wrong skill resolves.

It can silently not happen. npm ci --ignore-scripts skips postinstall and prepare, and is already deliberate practice in several neomjs workflows — that yields a resolved dependency and zero reachable skills. A dependency resolving is not the same as skills…