nexgo-skills

nexgo-skills is the TypeScript CLI for installing and managing internal Nexus ZIP skills. The published runtime is scoped to new-cli; go-cli remains a non-published reference implementation.

Commands

The public command surface is limited to the internal Nexus ZIP lifecycle:

nexgo-skills search <keyword>
nexgo-skills install <skill> --agent universal --scope project
nexgo-skills update <skill> --agent universal --scope project
nexgo-skills remove <skill> --agent universal --scope project
nexgo-skills check --agent universal --scope project

add, find, init, and list are not supported. The former --skills.sh compatibility mode has been removed and now fails before any network or file operation.

For external Skills, open the selected Skill on https://skills.sh and follow the official installation command shown on its detail page.

Examples:

nexgo-skills install collection <slug> --agent universal --scope project --api-key ns-...
nexgo-skills install <skill> --skills-path ./.custom/skills --scope project
nexgo-skills install private-skill --agent universal --scope project --api-key ns-...

私有 Skill 和集合安装只接受 NEXGO API Key。CLI 会优先读取 NEXGO_SKILLS_API_KEY，未配置时再读取 --api-key 参数。公开 Skill 可匿名安装；私有资源缺少或使用无效 API Key 时，请访问 https://skills.nexgoglobal.com 登录获取。

Development

pnpm install
pnpm test
pnpm type-check
pnpm build

Local Debugging

Build, pack, and install the CLI into an isolated local prefix:

.\scripts\debug-local.ps1

Run optional smoke checks:

.\scripts\debug-local.ps1 -SearchNexus

npmjs Publishing

npmjs publishing uses browser-based login for accounts with 2FA. Running publish-npmjs.ps1 without arguments publishes by default, checks the current npm session, and opens the browser login flow automatically when needed:

pnpm run publish:npmjs:login

You can also run the publish command directly. If npm whoami is not authenticated, the script runs npm login --auth-type web, waits for the browser verification to finish, and verifies the npm account before publishing.

Use -DryRun only when you want checks and package preview without uploading.

Prepare the package without uploading it:

pnpm run publish:npmjs:check

The check script runs the collection install tests, type-checks, builds dist, and runs npm pack --dry-run. It also fails early if the current package.json version already exists on npmjs.

Publish from the package directory after the dry-run succeeds:

npm publish --access public --tag latest --registry https://registry.npmjs.org/

Normally omit --otp; npmjs opens browser-based two-factor verification during npm publish when required. Use an OTP only when explicitly choosing the legacy flow:

npm publish --access public --tag latest --registry https://registry.npmjs.org/ --otp=<six-digit-code>

For a script-driven interactive publish, use:

pnpm run publish:npmjs

The legacy scripts/publish-npm.ps1 flow is only for the internal Nexus npm registry.

The implementation is intentionally scoped to new-cli; go-cli remains a reference source.