harness-status

Aggregate Harness configuration, blocking events, and pending decisions from repository files.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/cano721/ai-harness --skill harness-status-cano721
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: harness-status
Source: https://github.com/cano721/ai-harness/tree/main/skills/harness-status
Command: npx skills add https://github.com/cano721/ai-harness --skill harness-status-cano721

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Quickly surface the current Harness configuration, block events, and any pending decisions to keep projects compliant and healthy.

Core Features & Use Cases

  • Configuration overview: reads .ai-harness/config.yaml and .claude/settings.json to display team/project and registered hooks.
  • Blocking visibility: aggregates today's block events from .ai-harness/logs and shows per-hook counts.
  • Pending decisions: lists items from .ai-harness/pending-decisions.yaml and flags unresolved items.
  • Diagnostics: checks config parseability, hook file presence and execute permissions, and CLAUDE harness registrations.

Quick Start

Use harness-status to generate a consolidated health snapshot of the project.

Frequently Asked Questions about harness-status

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

FAQPage Schema
How do I check my project's AI harness configuration and health status?▼

To check your project's AI harness configuration and health status, you can surface the current settings by reading .ai-harness/config.yaml and .claude/settings.json to display team configurations and registered hooks.

How does blocking visibility work for project hook events?▼

Blocking visibility for project hook events works by aggregating today's block events from .ai-harness/logs and showing per-hook counts to identify which specific hooks are actively blocking operations.

How do I list pending decisions and flag unresolved governance items in my repository?▼

To list pending decisions and flag unresolved governance items, you read items from .ai-harness/pending-decisions.yaml and automatically flag any unresolved entries for team review.

Can I validate hook file presence and execute permissions using a diagnostics check?▼

Yes, you can validate hook file presence and execute permissions by running a diagnostics check that verifies config parseability, hook file existence, execute permissions, and CLAUDE harness registrations.

What is the best way to monitor configuration health and hook activity for a given project?▼

The best way to monitor configuration health and hook activity is to generate a consolidated health snapshot that aggregates configuration overviews, blocking events, and pending decisions into actionable insights.

Why does my harness diagnostics check fail when reading config files?▼

Your harness diagnostics check may fail when reading config files if the .ai-harness/config.yaml is not parseable, if hook files are missing, or if execute permissions are incorrectly set on the registered hook scripts.