gap-audit

Enforce explicit dispositions for each observability gap in a central registry.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/RawleySM/rlm-adk --skill gap-audit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gap-audit
Source: https://github.com/RawleySM/rlm-adk/tree/main/.claude/obsolete/gap-audit
Command: npx skills add https://github.com/RawleySM/rlm-adk --skill gap-audit

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires jsonschema, and includes scripts (resource) components.

What problem does it solve?

Manage observability gap registry to enforce explicit dispositions for each gap.

Core Features & Use Cases

  • Enforces explicit dispositions (pending/closed/dismissed/deferred) for each gap in a central registry.
  • Provides commands and prompts to view status, close gaps with evidence, dismiss, or defer gaps, and to run the gap guard in strict mode.
  • Emits delegation prompts in strict mode when pending gaps exist, preventing silent blocking.

Quick Start

Activate GAP_AUDIT_ACTIVE by setting it to 1 in .claude/settings.local.json, then run /gap-audit status to view progress and use /gap-audit close|dismiss|defer <gap-id> to manage gaps.

Frequently Asked Questions about gap-audit

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

FAQPage Schema
How do I track and close observability gaps in my registry?

Observability gaps are managed by enforcing explicit dispositions like pending, closed, dismissed, or deferred. You can view status and close gaps with evidence using commands such as /gap-audit close to manage the registry.

What happens when a stop hook reports pending gaps in strict mode?

In strict mode, pending gaps trigger a delegation prompt to prevent silent blocking. The system validates the registry schema and enforces evidence requirements per tier before allowing you to proceed.

How do I dismiss or defer observability gaps instead of closing them?

You can dismiss or defer observability gaps by running /gap-audit dismiss or /gap-audit defer with the specific gap ID. This enforces an explicit disposition for each tracked gap in the central registry.

Do I need jsonschema to validate the observability gap registry?

Yes, jsonschema is required to validate the gap registry schema and enforce evidence requirements per tier, ensuring all dispositions and counts are correctly structured before applying changes.

How do I activate observability gap tracking in my local settings?

To activate gap tracking, set GAP_AUDIT_ACTIVE to 1 in the .claude/settings.local.json file. Once activated, run /gap-audit status to view progress and begin managing gaps.

Why does strict mode emit a delegation prompt for pending gaps?

Strict mode emits a delegation prompt for pending gaps to prevent silent blocking during the stop hook process. This ensures every observability gap receives an explicit disposition before the workflow continues.