harness-audit

Name: harness-audit
Availability: InStock
Author: kanno321-create

Aggregate drift, context-compressor, and progressive-disclosure metrics into a structured studio health report.

Updated Aug 23, 2026

Search Tags:#audit #drift-detection #health #progressive-disclosure #studio #context-compressor

Ready to run

npx skills add https://github.com/kanno321-create/shorts_studio --skill harness-audit-kanno321-create

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: harness-audit
Source: https://github.com/kanno321-create/shorts_studio/tree/main/.claude/skills/harness-audit
Command: npx skills add https://github.com/kanno321-create/shorts_studio --skill harness-audit-kanno321-create

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

이 스킬은 드리프트 탐지, 컨텍스트 컴프레서(context-compressor), 그리고 스킬 슬림(progressive-disclosure)을 포함한 다중 진단을 통합하여 스튜디오의 전반적인 건강 상태를 자동으로 평가하고 포괄적인 리포트를 제공합니다.

Core Features & Use Cases

Drift 탐지 및 충돌 지표를 자동으로 수집하고 이상치를 식별합니다.
Context Load를 최적화하고 초기 로드 비용을 줄이는 실행 가능한 인사이트를 제공합니다.
SKILL Slim 관리: 500줄 초과 SKILL를 식별하고 정리하는 루프를 지원합니다.
Hook 설치 상태를 점검하고 모든 필수 훅의 배치를 확인합니다.
CLAUDE.md 품질을 평가하고 구조/원칙 준수 여부를 리포트에 반영합니다.
Use Case: 스튜디오 전반의 건강 진단을 주기적으로 수행하고 이력과 개선점을 관리합니다.

Quick Start

Run the harness-audit to generate a comprehensive studio health report.

Frequently Asked Questions about harness-audit

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

FAQPage Schema

How do I run a comprehensive studio health audit for drift detection and context load metrics?▼

A studio health audit aggregates drift-detection, context-compressor, and progressive-disclosure metrics to evaluate overall project health. It collects domain scores, measures context load, and verifies hook registrations to produce a structured diagnostic report.

What is included in a studio health check report for project monitoring?▼

A studio health check report includes domain scores, detected drift anomalies, context load measurements, counts of long SKILLs exceeding 500 lines, hook registration statuses, and CLAUDE.md quality assessments to provide a comprehensive health overview.

How do I identify and manage long SKILLs that exceed 500 lines in my project?▼

To manage long SKILLs, the audit identifies any SKILL exceeding 500 lines and supports a cleanup loop to streamline them. This progressive-disclosure management reduces initial context load and optimizes overall studio performance.

Does the health audit automatically verify hook registrations and CLAUDE.md quality?▼

Yes, the health audit automatically verifies hook installation statuses to ensure all required hooks are placed correctly. It also evaluates CLAUDE.md quality, reporting on structural and principle compliance within the final diagnostic output.

When do I need to perform a project health check for drift and context optimization?▼

You need a project health check when ongoing monitoring is required, such as on session start. It proactively detects configuration drift, identifies context load bottlenecks, and assesses CLAUDE.md structure to maintain studio hygiene.

What is the best way to consolidate multiple diagnostic metrics into a single studio health report?▼

The best way to consolidate diagnostics is through a unified audit that aggregates drift-detection, context-compressor, and progressive-disclosure metrics. This approach evaluates load, counts long SKILLs, and verifies hooks to generate a single structured report.