← Articles

OpenClaw Plugin SDK npm Publish Workflow: Third-Party Plugins Go Public

OpenClaw Plugin SDK Ecosystem March 18, 2026 · Onur Solmaz · PR #47678

About the Contributor

Onur Solmaz is an OpenClaw core contributor focused on build tooling and developer experience. This PR represents weeks of coordinated work across the plugin SDK, contract registry, and CI infrastructure.

Why This Matters

OpenClaw's plugin ecosystem just hit a major milestone: third-party developers can now publish plugins to npm with official tooling support. PR #47678 adds a complete GitHub Actions workflow for plugin authors to version, build, and publish their plugins to the npm registry.

This is the difference between "technically possible" and "actually usable." Before this PR, plugin authors had to manually manage builds, versioning, and publishing. Now it's automated, tested, and consistent with how OpenClaw's own plugins ship.

What Changed

The PR introduces a plugin-publish.yml workflow with:

Automated versioning — semantic version bumps based on commit messages
Declaration validation — ensures plugin manifests pass the SDK schema
Build verification — TypeScript compilation with strict mode, no unresolved imports
npm publishing — authenticated publish to the public registry
Contract registry sync — published plugins appear in OpenClaw's discovery index

Supporting commits this week hardened the pipeline: ea476de adds a seam audit script to catch SDK contract drift, 86e9dcf fails builds on unresolved tsdown imports, and 4157bcd enforces declaration file generation.

            🔧 Technical Details
            Workflow triggers on tag push matching v*
Uses tsdown for bundling with strict unresolved import checks
Contract registry images sync via 13f396b
Setup timeouts extended to handle slower CI environments (5d41fd4)

        

Why Plugin Ecosystems Need This

The difference between a popular open-source project and a thriving ecosystem often comes down to how easy it is for third parties to contribute. OpenClaw already has impressive adoption (319k+ stars), but sustainable growth requires external plugin developers.

Consider what plugin authors needed before this PR:

Figure out the build system (tsdown, TypeScript config, module resolution)
Understand the contract schema and validation requirements
Manually test against the plugin SDK
Handle npm authentication and publishing
Hope the registry picks up their plugin

Now they clone a template, write their plugin logic, and push a tag. The workflow handles the rest.

Ecosystem Implications

This PR is part of a coordinated push visible in related commits:

Plugin SDK hardening — stricter validation, better error messages
Contract registry sync — automatic discovery for published plugins
Build tooling improvements — faster, more reliable builds

The pattern mirrors successful plugin ecosystems like VSCode extensions and Obsidian plugins: official tooling that makes the happy path obvious and well-supported.

What's Next

Open issues suggest the roadmap:

Configurable startup order (#49884) — plugins may need sequenced initialization
Skill setup flow improvements (#49883) — better onboarding for complex plugins
Agent tool error routing (#49882) — plugins need better error handling patterns

The plugin SDK is maturing from "internal use" to "external ecosystem." This workflow is the infrastructure that makes that transition possible.

For Plugin Authors

If you're building an OpenClaw plugin:

Use the official plugin template (coming soon to create-openclaw-plugin)
Follow semantic commit conventions for automatic versioning
Test locally with openclaw plugin test
Push a version tag to trigger the publish workflow

The ecosystem just got significantly more accessible.