harness-import SKILL.md skillB
harness-import from harnessprotocol/harness-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harnessprotocol/harness-kit/harness-import@git:20261022.21ea2eePins git:20261022.21ea2ee in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harnessprotocol/harness-kit
- Path
plugins/harness-share/skills/harness-import/SKILL.md- Versions recorded
- 6
- Latest version
- git:20261022.21ea2ee, committed Oct 22, 2026
- First version recorded
- Mar 10, 2026
- Size
- 17,944 bytes
- Repository stars
- 10
- License
- Apache-2.0
Use when user invokes /harness-import or wants to install plugins from a shared harness.yaml config file. Reads the config, presents each plugin interactively, and generates the Claude Code install commands for the ones the user selects. Handles both Harness Protocol v1 format (version: "1") and the legacy format (version: 1).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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: ``` …
Read the whole file at its exact version.
How to install
mdr add harnessprotocol/harness-kit/harness-import@sha256:0f1ccfd94cb37405The line at the top of this page pins the label git:20261022.21ea2ee, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_tpjyq3ttn54ozn7e)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 6 versions of this file, between Mar 10, 2026 and Oct 22, 2026, about one every 45 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261022.21ea2ee latest | 2026-10-22 | 21ea2ee | 17,944 B | B | view · diff |
| git:20260727.387edcf | 2026-07-27 | 387edcf | 17,933 B | B | view · diff |
| git:20260313.da67736 | 2026-03-13 | da67736 | 14,877 B | B | view · diff |
| git:20260311.d9aed0f | 2026-03-11 | d9aed0f | 7,138 B | B | view · diff |
| git:20260311.6c33c6e | 2026-03-11 | 6c33c6e | 7,108 B | B | view · diff |
| git:20260310.2fcaf7f | 2026-03-10 | 2fcaf7f | 3,899 B | B | view |
Audit of the latest version
- fail: No curl or wget piped into a shell (matched: curl -fsSL https://raw.githubusercontent.com/harnessprotocol/harness-kit/main/harness-restore.sh | b)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (17944 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
harnessprotocol/harness-kit · 10 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_tpjyq3ttn54ozn7e GET https://markdownregistry.com/api/v1/resolve?ref=harnessprotocol/harness-kit/harness-import GET https://markdownregistry.com/api/v1/blob/0f1ccfd94cb37405d69b906039ce6749f375cc2ec3dc607c7df771af8cfac4cc
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.