Agent skill · software engineering · vercel
update-harness-dependencies
Update the primary SDK dependencies of harness packages. Use when asked to update the harness SDKs or harness adapter dependencies.
Why this skill is useful
Adds specific commands for updating harness SDK dependencies that the AI wouldn't reliably generate on its own.
What it needs
Requires pnpm installed locally. About 2k tokens when loaded. Last updated 2026-08-07. 26,057 stars on the source repository.
What this skill does
Update the harness packages The harness adapters are all the packages/harness- packages. They each rely on one or more third-party packages for the respective harness's primary SDK. It is crucial to keep those dependencies up to date. Below you find the instructions on how to update those packages to their latest versions, while adhering to the minimum release age defined in pnpm-workspace.yaml. Update the harness dependency packages Run the following commands to update each harness's primary SDK packages. For bridge harnesses (e.g. Claude Code), this will update the packages in devDependencies, while the actual package versions used as dependencies are only relevant to the harness's bridge itself. For non-bridge harnesses (e.g. Pi), this will update the packages in dependencies. Run these commands exactly as below: For the bridge dependencies of bridge harnesses, you must additionally run the following commands. It is important to specify the config.minimumReleaseAge flag in accordance with what pnpm-workspace.yaml defines, because for these commands the --ignore-workspace flag is needed. Run these commands exactly as below: For bridge CLI packages that require install scripts, also update the exact version in the bridge's pnpm-workspace.yaml allowBuilds entry to match the new version in its package.json: packages/harness-claude-code/src/bridge/pnpm-workspace.yaml packages/harness-github-copilot/src/bridge/pnpm-workspace.yaml packages/harness-grok-build/src/bridge/pnpm-workspace.yaml packages/harness-opencode/src/bridge/pnpm-workspace.yaml The following harness adapters use an unversioned installer script instead of an NPM package for their SDK / CLI and therefore can be ignored: packages/harness-cursor packages/harness-fx Example dependencies Check the package.json files in examples/harness-e2e-next and examples/harness-e2e-tui for any of the above SDKs they depend on. Those dependencies need to be updated to match the exact version used in the packages as well. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills vercel/update-harness-dependencies