hiddink-harness:update-docs

Validate agent files, skill modules, and guide references against the directory structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill resolves documentation drift by ensuring that agent configurations, skill references, and project metadata remain perfectly aligned with the actual file structure of the harness.

Core Features & Use Cases

  • Consistency Validation: Automatically detects missing agent files, orphaned skills, or broken guide references across the project.
  • Automated Syncing: Updates the central CLAUDE.md file and inter-agent references to reflect the current state of the repository.
  • Use Case: After adding a new specialist agent or refactoring skill categories, run this tool to verify that all cross-references are updated and the project summary is accurate.

Quick Start

Run the update-docs skill to scan the project structure and automatically synchronize all documentation files.

Frequently Asked Questions about hiddink-harness:update-docs

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

FAQPage Schema
How do I prevent documentation drift after refactoring agent files and skill modules?

Synchronizing project documentation validates the consistency of agent files, skill modules, and guide references against the actual directory structure. It operates within the harness environment to maintain organic integration between agents and their assigned capabilities.

How do I update CLAUDE.md and cross-references after adding a new specialist agent?

Updating CLAUDE.md and cross-references requires running an automated syncing process that scans the project structure. This process detects missing agent files and updates the central project summary to reflect the current repository state accurately.

What is the best way to validate project documentation consistency in a harness environment?

The best way to validate documentation consistency in a harness environment is to perform automated verification of internal cross-references. This detects orphaned skills or broken guide references and updates the documentation to ensure architectural integrity.

Does this documentation validation tool work without external dependencies?

Yes, this documentation validation operates entirely within the harness environment and requires no external dependencies. It autonomously scans the project structure to detect missing agent files and synchronize all documentation files.

Why does my project summary show broken guide references after modifying skill categories?

Broken guide references occur because of documentation drift when skill categories are modified. Running an automated consistency validation synchronizes the project documentation by checking agent files and skill references against the actual directory structure.