harness-import

Import a Harness Configuration

You are helping the user install plugins from a harness.yaml file — either all of them or a subset they choose.

This skill handles both format versions:

• v1 protocol format (version: "1" string) — uses source: owner/repo per plugin, may include mcp-servers, env, and instructions sections
• Legacy format (version: 1 integer) — uses marketplace: key per plugin with a marketplaces: section

Workflow Order (MANDATORY)

Follow these steps in order. Do not skip any step.

---

Step 1: Find and read the config

Check for harness.yaml in this order:

1. A path provided by the user after /harness-import (e.g., /harness-import ~/dotfiles/harness.yaml)
2. ./harness.yaml in the current directory

If no file is found at either location, tell the user:

"No harness.yaml found. Get one from a teammate or generate your own with /harness-export."

Read and parse the file. Detect which format version it uses:

• version: "1" (string) → Protocol v1 format
• version: 1 (integer) → Legacy format

---

Step 2: Show what's available

Display the plugin list clearly before asking anything:

Plugins in this config:

  1. explain (harnessprotocol/harness-kit) — Layered explanations of files, functions, directories, or concepts
  2. research (harnessprotocol/harness-kit) — Process any source into a structured, compounding knowledge base
  3. superpowers (obra/superpowers-marketplace) — Structured dev workflows — TDD, systematic debugging, subagent delegation

For legacy format, resolve the source by looking up plugins[].marketplace → marketplaces[key].

Then, if the file contains any of the following sections, mention them briefly:

• mcp-servers: — "This config also declares MCP servers. I'll ask about those after plugins."
• env: — "This config declares environment variables. I'll surface those after plugins."
• instructions: — "This config includes harness instructions. I'll offer to apply those after plugins."