ns-package

Manage NeuroScript package manifests, dependencies, and Ed25519-signed releases.

Updated Nov 25, 2025
One-click install
npx skills add https://github.com/severeon/neuroscript-rs --skill ns-package
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ns-package
Source: https://github.com/severeon/neuroscript-rs/tree/main/.claude/skills/ns-package
Command: npx skills add https://github.com/severeon/neuroscript-rs --skill ns-package

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill streamlines NeuroScript package management by providing a consistent workflow for initializing packages, declaring dependencies, generating lockfiles, and ensuring integrity through checksums and Ed25519 signatures so packages remain reproducible and verifiable.

Core Features & Use Cases

  • Initialize packages: Create Axon.toml, README.md, .gitignore, and src/ (plus examples/ for binaries).
  • Dependency management: Add version, git, or local path dependencies with validation and rules that prevent conflicting fields.
  • Fetch & lock: Resolve and cache dependencies, generate Axon.lock for reproducible builds, and support CI-friendly fetch/update operations.
  • Signing & verification: Key generation (Ed25519), per-file SHA-256 checksums, aggregate checksum computation, signing on publish, and verification on fetch or explicit verify.
  • Use Case: Prepare a transformer neuron library for publication with pinned dependencies, signed integrity metadata, and CI verification steps.

Quick Start

Initialize a new package, add dependencies, fetch and lock them, generate signing keys, and publish a signed package using the neuroscript CLI.

Frequently Asked Questions about ns-package

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage NeuroScript package dependencies and generate a lockfile?

To manage NeuroScript package dependencies, you declare them in the Axon.toml manifest and fetch them to generate an Axon.lock file, ensuring reproducible builds across local development and CI pipelines. Supported dependency types include version, git, and local path.

How does cryptographic signing and verification work for NeuroScript packages?

Cryptographic signing for NeuroScript packages uses Ed25519 keys to sign releases on publish, computing per-file SHA-256 checksums and an aggregate checksum. Verification occurs automatically on fetch or through an explicit verify command to ensure package integrity.

What is included when initializing a new NeuroScript package?

Initializing a new NeuroScript package creates an Axon.toml manifest, a README.md, a .gitignore file, and a src/ directory. For binary packages, it also generates an examples/ directory to help structure your neuron library.

Can I use local path dependencies alongside git dependencies in Axon.toml?

Yes, you can use local path and git dependencies in Axon.toml, but validation rules prevent conflicting fields within the same dependency declaration. This ensures dependency resolution remains unambiguous when fetching and locking packages.

What is the best way to publish a signed NeuroScript neuron library in CI?

The best way to publish a signed NeuroScript neuron library in CI is to fetch and lock dependencies, generate Ed25519 signing keys, and apply SHA-256 checksums before signing on publish. CI pipelines can then verify the release using the explicit verify command.