harness-portability

Export and install the global OpenCode harness configuration on another PC.

Updated Jul 29, 2026
One-click install
npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-portability-maicongambini
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-portability
Source: https://github.com/MaiconGambini/opencode-harness-guide/tree/main/skills/harness-portability
Command: npx skills add https://github.com/MaiconGambini/opencode-harness-guide --skill harness-portability-maicongambini

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Moving an OpenCode harness setup (configuration, skills, plugins, templates, and scripts) to a new PC is error-prone when done manually, risking copied secrets, stale absolute paths, and bloated transfers with node_modules or caches. ## Core Features & Use Cases - Harness Export: Runs a PowerShell script that packages opencode.jsonc, skills/, plugins/, templates/, scripts/, package.json, and package-lock.json into a portable archive. - Clean Install on a New PC: Extracts the zip and installs the harness into the target OpenCode config directory, followed by npm install to restore dependencies. - Safety Rules: Excludes node_modules, caches, logs, and secrets, and reminds users to review opencode.jsonc for old absolute paths after installation. - Use Case: You configured OpenCode on your work machine and want the identical harness on a laptop; export the harness, copy the zip, and run the install script to reproduce the setup. ## Quick Start Export my OpenCode harness from this PC and give me the steps to install it on my new machine.

Frequently Asked Questions about harness-portability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I move my OpenCode harness to another PC?

Run the export-opencode-harness.ps1 script from your OpenCode config directory to create a zip, then extract it on the new PC and run install-opencode-harness.ps1 with the target root set to the new config path, followed by npm install.

What files are included in the OpenCode harness export?

The export includes opencode.jsonc, the skills/, plugins/, templates/, and scripts/ directories, plus package.json and package-lock.json. It excludes node_modules, caches, logs, and secrets.

Can I copy node_modules between PCs when migrating OpenCode?

No, node_modules should not be copied between PCs. The export explicitly excludes it; instead run npm install in the target config directory after installation to rebuild dependencies from package-lock.json.

Why does my OpenCode harness break after installing on a new machine?

The most common cause is stale absolute paths in opencode.jsonc pointing to the old machine's directories. Review and update those paths after install, and confirm no machine-specific secrets were carried over in templates.

Does the harness export include secrets or credentials?

No, the export explicitly excludes secrets along with caches and logs. You should still keep machine-specific secrets out of templates so they are never packaged into the portable archive.