hiddink-harness:sauron-watch

Audit multi-agent orchestration harnesses for structural integrity and dependency issues.

1|Updated May 21, 2026
One-click install
npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-sauron-watch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hiddink-harness:sauron-watch
Source: https://github.com/hiddink-ai/hiddink-harness/tree/main/templates/skills/sauron-watch
Command: npx skills add https://github.com/hiddink-ai/hiddink-harness --skill hiddink-harness-sauron-watch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents configuration drift and structural inconsistencies in complex multi-agent environments by performing a rigorous, multi-phase audit of all agents, skills, and documentation.

Core Features & Use Cases

  • Multi-Phase Verification: Executes 5 rounds of manager-level audits and 3 rounds of deep structural reviews to ensure system-wide synchronization.
  • Structural Linting: Automatically detects orphaned skills, circular dependencies, and context fork cap violations to maintain architectural health.
  • Use Case: Before committing changes to the repository, run this skill to ensure that all agent mappings, routing patterns, and documentation counts are perfectly aligned with the project's source of truth.

Quick Start

Execute the sauron-watch skill to perform a complete R017 verification of the current project structure.

Frequently Asked Questions about hiddink-harness:sauron-watch

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

FAQPage Schema
How do I verify multi-agent orchestration harness integrity before committing changes?

To verify multi-agent orchestration harness integrity, you need a full-spectrum structural audit that validates agent-skill mappings and dependency graphs. This process executes multiple manager-level audits and deep structural reviews to enforce architectural invariants and ensure commit readiness.

What is structural linting for multi-agent environments and when do I need it?

Structural linting for multi-agent environments is a verification process that detects configuration drift and structural inconsistencies. You need it to automatically identify orphaned skills, circular dependencies, and context fork cap violations across your repository to maintain architectural health.

How do I detect circular dependencies and orphaned skills in my agent repository?

Detecting circular dependencies and orphaned skills requires comprehensive structural linting of your orchestration harness. This audit automatically flags these architectural violations by validating dependency graphs and agent-skill mappings against the project's source of truth.

Can I audit agent-skill mappings and documentation consistency across an entire repository?

Yes, you can audit agent-skill mappings and documentation consistency across an entire repository using full-spectrum project integrity verification. It performs rigorous multi-phase audits to ensure all routing patterns and documentation counts are perfectly aligned.

Does multi-phase verification work for preventing configuration drift in complex agent setups?

Multi-phase verification works effectively for preventing configuration drift by running 5 rounds of manager-level audits and 3 rounds of deep structural reviews. This rigorous process ensures system-wide synchronization and validates all architectural invariants before commit.