harness-audit

Audit OpenClaw harness configurations for health issues across workspaces.

Updated Feb 6, 2026
One-click install
npx skills add https://github.com/glfruit/gorin-skills --skill harness-audit-glfruit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: harness-audit
Source: https://github.com/glfruit/gorin-skills/tree/main/openclaw/harness-audit
Command: npx skills add https://github.com/glfruit/gorin-skills --skill harness-audit-glfruit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps maintain healthy OpenClaw harness configurations by detecting bloated workspaces, stale references, duplicated rules, and hard-coded payloads across all agent workspaces.

Core Features & Use Cases

  • Periodic health audits across SOUL.md, AGENTS.md, SKILL.md, and cron jobs to surface P0–P3 findings.
  • Trend tracking across audits to identify drift and improvement.
  • Non-destructive, read-only checks that guide remediation steps.

Quick Start

Schedule regular scans with the harness-audit tool to obtain an up-to-date health report.

Frequently Asked Questions about harness-audit

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

FAQPage Schema
Why do I need to check SOUL.md and AGENTS.md for workspace bloat?

Checking SOUL.md and AGENTS.md identifies stale references and duplicated rules that degrade workspace health, using read-only checks that guide remediation without making prohibited changes without user confirmation.

Can I schedule periodic health audits for OpenClaw agent workspaces?

Periodic health audits can be scheduled via cron to generate up-to-date reports, tracking trend data over time to identify configuration drift and improvement across all agent workspaces.

Does the OpenClaw audit tool modify workspace configurations during scanning?

The OpenClaw audit tool performs non-destructive, read-only checks that guide remediation steps, strictly prohibiting configuration changes without explicit user confirmation.

What is the best way to track configuration drift in OpenClaw harnesses?

The best way to track configuration drift is by running regular health audits that compare trend data over time, surfacing P0–P3 severity findings across all workspaces to identify drift and improvement.

How do I detect hard-coded payloads in OpenClaw SKILL.md files?

You detect hard-coded payloads by running the harness-audit script to parse and report findings across SKILL.md files, classifying issues by severity to guide targeted remediation actions.