Favicon of npm-publish

npm-publish Skill

AI Agent SkillJavaScriptOpen source

Publishing duroxide-node to npm. Use when releasing a new version, building platform binaries, or publishing to the npm registry. Published by microsoft in duroxide-node.

Decision snapshot

Is this a fit?

Best for

Testing, Documentation, Includes SKILL.md, Reusable instructions

Works with

Compatibility not yet detected.

Access

Permission behavior not yet detected.

Setup

Copy skill directory

Project health

3 months ago · MIT license

Considerations

No specific cautions were detected. Review the source and requested permissions before installing.

What is npm-publish Skill?

Publishing duroxide-node to npm. Use when releasing a new version, building platform binaries, or publishing to the npm registry. Published by microsoft in duroxide-node. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.

Trust signal
95/100
Maintenance signal
90/100
Adoption signal
38/100

Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.

Key capabilities

  • Includes SKILL.md support
  • Reusable instructions support
  • Testing
  • Documentation
  • Testing use cases
  • Documentation use cases

Declared skill metadata

  • Source file: .agents/skills/npm-publish/SKILL.md

These fields retain source and confidence evidence from the indexed SKILL.md.

Compatibility and setup

Copy skill directory
  • Install or run with Copy skill directory

When to use npm-publish Skill

  • Use it for testing.
  • Use it for documentation.

Built with

JavaScriptCopy skill directory

Editorial notes

Source

  • Creator: microsoft
  • Repository: microsoft/duroxide-node
  • Skill file: .agents/skills/npm-publish/SKILL.md

What it does

Publishing duroxide-node to npm. Use when releasing a new version, building platform binaries, or publishing to the npm registry.

Skill instructions

Publishing duroxide-node to npm Pre-Publish Checklist Before publishing, verify ALL of the following: 1. Clean Build bash cd duroxide-node Clippy — must pass with zero warnings cargo clippy --all-targets Release build via napi npx napi build --platform --release 2. Tests Pass bash All tests must pass (requires DATABASEURL in .env) npm run test:all 3. Changelog Updated - CHANGELOG.md must have an entry for the new version - Follow Keep a Changelog format - Include all Added/Changed/Fixed/Removed sections as applicable 4. README Points to Changelog Verify README.md contains a link to CHANGELOG.md: markdown See CHANGELOG.md for release notes. 5. Version Bumped Update version in package.json and all platform package.json files: bash Bump version (also updates npm/npm//package.json) npx napi version Or manually update package.json version field and ensure optionalDependencies versions match. Build Platform Binaries Five platform packages are supported: darwin-arm64 (macOS Apple Silicon) — n

Verified compatibility and discovery

Frequently asked questions

What is npm-publish?

npm-publish is a open-source AI agent skill with Copy skill directory. Publishing duroxide-node to npm. Use when releasing a new version, building platform binaries, or publishing to the npm registry.

Who is npm-publish best for?

npm-publish is best for reusing agent instructions, scripts, and references, testing workflows, documentation workflows.

How do I install npm-publish?

Install or run npm-publish using Copy skill directory. Check npm-publish for the latest setup command.

Is npm-publish actively maintained?

npm-publish may need a closer maintenance check before production use.

Share:

Stars
33
Forks
19
Last commit
3 months ago
Last verified
Aug 31, 2026
Metadata fetched
Aug 31, 2026
Repository age
7 months
License
MIT

Project health auto-fetched from the source repository.

Maintain this resource?

Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.

Alternatives to npm-publish