neomjs

Neo Agent Skills — AI skill for Claude Code

AI community

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.

How to install Neo Agent Skills

This entry records only its repository, not the path inside it, so there is no exact command to give. Open neomjs/neo-agent-skills and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Neo Agent Skills does

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.

Alternatives in AI

Pilotfish — Multi-model orchestration layer for Claude Code — the frontier model plans, cheaper models execute, verificati 688 ★
Openase — Ticket-Driven Automated Software Engineering 265 ★
Mnem — Git for AI Agent Knowledge 144 ★

README

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

npm install --save-dev neo-agent-skills

Then run the materializer from your `postinstall`:

{
  "scripts": { "postinstall": "neo-agent-skills-materialize" },
  "devDependencies": { "neo-agent-skills": "^0.1.0" }
}

`postinstall` materializes **two surfaces**, both as symlinks into `node_modules`, 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.

**Skill changes bump this package's version.** 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

npx neo-agent-skills-materialize --check

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 being reachable, and only this check t