harness-doctor

Diagnose installed autoharness harness integrity and apply low-risk repairs.

1|Updated Oct 17, 2025
One-click install
npx skills add https://github.com/softwaresalt/csv-managed --skill harness-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-doctor
Source: https://github.com/softwaresalt/csv-managed/tree/main/.github/skills/harness-doctor
Command: npx skills add https://github.com/softwaresalt/csv-managed --skill harness-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly determine why an installed autoharness harness is broken, out of sync, incomplete, or unavailable, so you can restore reliable agent execution.

Core Features & Use Cases

  • Integrity and completeness checks: Verifies the installed manifest exists, artifact directories are present, and all manifest-declared artifacts are still on disk.
  • Compatibility and drift detection: Compares the harness-installed version in the manifest against the expected autoharness version.
  • Reference and prerequisite validation: Detects broken internal cross-references across harness Markdown files and checks that declared MCP tools are reachable.
  • Installation residue detection: Flags unresolved template variables to catch incomplete or failed installation runs.
  • Optional low-risk repairs: In fix mode, creates missing empty artifact directories and quarantines orphaned .tmpl files accidentally copied into .github.

Quick Start

Run harness-doctor in report mode to get an immediate, graded health report of the installed harness and any required operator actions.

Frequently Asked Questions about harness-doctor

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

FAQPage Schema
How do I run a health check on an installed autoharness harness?

A health check validates an autoharness harness by inspecting the filesystem to verify manifest integrity, artifact completeness, and internal cross-references. It detects version drift against the expected autoharness version and flags unresolved template variables from failed installations.

Why does my autoharness manifest validation fail after manual edits?

Manifest validation fails after manual edits when internal cross-references across Markdown files break or manifest-declared artifacts are missing from disk. Running a diagnostic health check detects these broken references and flags unresolved template variables from incomplete installations.

Can I automatically repair missing artifact directories and orphaned template files?

You can repair missing artifact directories and orphaned template files by running fix mode. This low-risk recovery action creates missing empty artifact directories and quarantines orphaned .tmpl files accidentally copied into .github, avoiding any application or template source modification.

How do I verify MCP tool availability before running my agent harness?

You verify MCP tool availability by running a pre-flight readiness check that validates declared MCP tools are reachable. This ensures reliable agent execution when tool availability is uncertain and captures a baseline health snapshot before running tune-harness.

Does harness diagnostics modify my application or template source code?

No, harness diagnostics does not modify application or template source code. It performs deterministic filesystem inspection for graded per-phase reporting, and its optional fix mode only creates empty artifact directories and quarantines orphaned template residue.