gap-surfacer

Name: gap-surfacer
Availability: InStock
Author: ZekaiSuni

Track regulatory compliance policy gaps with YAML tracker files and user-approved notifications.

100|16|Updated May 13, 2026

Search Tags:#deadline management #status reporting #compliance workflow #regulatory gaps #policy tracking #approval controls

Ready to run

npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill gap-surfacer-zekaisuni

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: gap-surfacer
Source: https://github.com/ZekaiSuni/claude-for-legal-turkish/tree/main/regulatory-legal/skills/gap-surfacer
Command: npx skills add https://github.com/ZekaiSuni/claude-for-legal-turkish --skill gap-surfacer-zekaisuni

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It organizes regulatory-change driven policy/procedure gaps so compliance teams can track ownership, due dates, verification status, and the required next action for each gap.

Core Features & Use Cases

Unified gap tracker for regulatory diffs: Maintains an append-only style registry for gaps created from regulatory feed/diff inputs, including partial/full/new-policy/watch/comment-decision types.
Structured status reporting: Produces a role-based report listing open, due soon, overdue (only when verified), and watch/comment-decision items.
Guardrailed communication workflow: Enforces a “show preview → get explicit yes → send only with controlled conditions” rule to prevent unauthorized or unverified notifications.

Quick Start

Use the gap-surfacer skill to add and report regulatory gaps from /regulatory-legal:gaps and /regulatory-legal:comments, then review the generated status report before any notifications.

Frequently Asked Questions about gap-surfacer

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

FAQPage Schema

How do I track regulatory gaps and manage approvals for compliance policies?▼

A regulatory gap tracker organizes compliance policy and procedure gaps by maintaining YAML tracker files. These files record requirements, affected policies, owners, deadlines, and notification status to enforce user-approved communication workflows.

What is the best way to report on open and overdue compliance workflow items?▼

Structured status reporting lists open, due soon, verified overdue, watch, and comment-decision items from your regulatory tracker. This role-based report provides visibility into ongoing policy gaps without triggering unauthorized notifications.

How do I enforce approval controls before sending compliance status notifications?▼

You enforce approval controls by following a guardrailed workflow: show a preview, get explicit yes, and send only with controlled conditions. This prevents unauthorized or unverified notifications in your regulatory compliance workflow.

Can I track partial or new policy gaps created from regulatory diffs?▼

Yes, you can track partial, full, new-policy, watch, and comment-decision gap types. The system maintains an append-only style registry for gaps created from regulatory feed or diff inputs to support ongoing legal operations.

Why does the compliance tracker separate verified vs non-verified overdue items?▼

The compliance tracker separates verified vs non-verified overdue handling to ensure only verified overdue items appear in status reports. This distinction enforces non-automatic, user-approved notification rules and prevents inaccurate deadline management alerts.

Do I need to maintain YAML files to use a regulatory gap tracking workflow?▼

Yes, you need to maintain YAML tracker files to use this regulatory gap tracking workflow. These files store the registry of compliance requirements, affected policies, owners, and deadlines required for structured status reporting.