openwork-orchestrator-npm-publish
$
npx mdskill add different-ai/openwork/openwork-orchestrator-npm-publishPublishes openwork-orchestrator npm package with clean git hygiene
- Solves the task of publishing the openwork-orchestrator npm package
- Uses pnpm, GitHub Actions, and npm for versioning and publishing
- Triggers based on user commands like 'npm publish' or 'bump version'
- Delivers results by publishing packages and verifying versions
SKILL.md
.github/skills/openwork-orchestrator-npm-publishView on GitHub ↗
--- name: openwork-orchestrator-npm-publish description: | Publish the openwork-orchestrator npm package with clean git hygiene. Triggers when user mentions: - "openwork-orchestrator npm publish" - "publish openwork-orchestrator" - "bump openwork-orchestrator" --- ## Quick usage (already configured) 1. Ensure you are on the default branch and the tree is clean. 2. Bump versions via the shared release bump (this keeps `openwork-orchestrator` aligned with the app/desktop release). ```bash pnpm bump:patch # or: pnpm bump:minor # or: pnpm bump:major # or: pnpm bump:set -- X.Y.Z ``` 3. Commit the bump. 4. Preferred: publish via the "Release App" GitHub Actions workflow by tagging `vX.Y.Z`. Manual recovery path (sidecars + npm) below. ```bash pnpm --filter openwork-orchestrator build:sidecars gh release create openwork-orchestrator-vX.Y.Z packages/orchestrator/dist/sidecars/* \ --repo different-ai/openwork \ --title "openwork-orchestrator vX.Y.Z sidecars" \ --notes "Sidecar binaries and manifest for openwork-orchestrator vX.Y.Z" ``` 5. Build openwork-orchestrator binaries for all supported platforms. ```bash pnpm --filter openwork-orchestrator build:bin:all ``` 6. Publish `openwork-orchestrator` as a meta package + platform packages (optionalDependencies). ```bash node packages/orchestrator/scripts/publish-npm.mjs ``` 7. Verify the published version. ```bash npm view openwork-orchestrator version ``` --- ## Scripted publish ```bash ./.opencode/skills/openwork-orchestrator-npm-publish/scripts/publish-openwork-orchestrator.sh ``` --- ## First-time setup (if not configured) Authenticate with npm before publishing. ```bash npm login ``` Alternatively, export an npm token in your environment (see `.env.example`). --- ## Notes - `openwork-orchestrator` is published as: - `openwork-orchestrator` (wrapper + optionalDependencies) - `openwork-orchestrator-darwin-arm64`, `openwork-orchestrator-darwin-x64`, `openwork-orchestrator-linux-arm64`, `openwork-orchestrator-linux-x64`, `openwork-orchestrator-windows-x64` (platform binaries) - `openwork-orchestrator` is versioned in lockstep with OpenWork app/desktop releases. - openwork-orchestrator downloads sidecars from `openwork-orchestrator-vX.Y.Z` release assets by default.
More from different-ai/openwork
- browser-setup-devtoolsGuide users through browser automation setup using Chrome DevTools MCP only. Use when the user asks to set up browser automation, Chrome DevTools MCP, browser MCP, or runs the browser-setup command.
- daytona-electron-testTest the real Electron app on Daytona: create sandbox, start services, connect via CDP, create workspaces, drive sessions, and verify settings. Use when the user says 'test on Daytona', 'run the app on Daytona', 'Daytona dry run', 'test Electron remotely', or 'reproduce on Daytona'.
- get-startedGuide users through the get started setup and Chrome DevTools demo.
- opencode-bridgeBridge between OpenWork UI and OpenCode runtime
- opencode-mirrorMaintain the local OpenCode mirror for self-reference
- opencode-primitivesReference OpenCode docs when implementing skills, plugins, MCPs, or config-driven behavior.
- openwork-coreCore context and guardrails for OpenWork native app
- openwork-debugDebug OpenWork sidecars, config, and audit trail
- run-evalsRun OpenWork UI evals on a Daytona sandbox or local Electron instance. Handles sandbox creation, service startup, and eval execution via CDP browser tools.
- shadcnManages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".