Package Publishing
Share your agent capabilities with your team or publish them globally to the public registry.
Publishing Workflow
Publishing a skill to SPM compiles your source files, validates parameter formats against the JSON schema, and securely pushes the bundle to the central index registry.
Follow these sequential stages to publish your local package:
1. Prepare & Validate
Before building the package, verify that all configurations declared in spm.yaml comply with SPM registry rules. Run validation:
If any schema configurations (such as an undefined required input property or invalid kebab-case namespace) violate parameters, the CLI will return exact line-number warnings.
2. Compile Source Assets
Ensure that your TypeScript/JavaScript files are compiled into the targeted entry folder mapped in your manifest (e.g. "./dist").
3. Pushing to the Registry
Once your package passes local validations, execute the publish trigger. Ensure you are signed in (via spm login) or have configured the SPM_TOKEN environment variable:
The CLI will compress the code, upload the bundle to our secure storage registry, register the new version index, and automatically make it available under spm install @your-namespace/package-name.
Semantic Versioning Guidelines
To ensure agent runtimes operate reliably without unexpected failures, we strictly enforce standard NPM-style Semantic Versioning (MAJOR.MINOR.PATCH):
Use for standard internal bug fixes, dependency updates, and logic changes. Does NOT change input or output schemas.
Use when introducing new optional tool parameters, improved performance, or supplementary outputs. Schema remains backward compatible.
Use when modifying required input parameters, deleting properties, changing output shapes, or migrating runtimes.