coverage-check

Identify vocabulary gaps between pattern wording and PreToolUse hook queries.

7|Updated Mar 24, 2026

Search Tags:#lore #qa #vocabulary #patterns #mcp #coverage #tool-calls

Ready to run

npx skills add https://github.com/attila/lore --skill coverage-check-attila

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: coverage-check
Source: https://github.com/attila/lore/tree/main/integrations/claude-code/skills/coverage-check
Command: npx skills add https://github.com/attila/lore --skill coverage-check-attila

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Coverage Check identifies vocabulary gaps between a pattern's wording and the queries the lore PreToolUse hook would generate, enabling authors to surface and close gaps before ingestion.

Core Features & Use Cases

Automates deriving candidate queries by simulating 3-6 tool calls that a real agent would issue for the pattern.
Ingests the target file, validates structure and location, and reports which queries surface in the index with actionable edits.
Use Case: a pattern author ensures terms and concepts appear in both the prose and metadata so the PreToolUse hook can surface the right results during automated checks.

Quick Start

Run coverage-check on a single pattern file path to generate a surface-queries report.

Frequently Asked Questions about coverage-check

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

FAQPage Schema

How do I check if my pattern's vocabulary matches generated lore queries?▼

To check pattern vocabulary coverage, this Skill simulates 3-6 tool calls to identify vocabulary gaps between your pattern's wording and the queries the PreToolUse hook generates. It operates on a single pattern file and reports surface coverage gaps with actionable edits.

What is pattern coverage gap analysis in a lore installation?▼

Pattern coverage gap analysis identifies missing terms between a pattern's wording and generated PreToolUse queries. It simulates tool-call extractions on a single pattern file, ingests the file, and reports which queries surface in the index with suggested edits.

Do I need a configured knowledge_dir to run pattern coverage checks?▼

Yes, running pattern coverage checks requires a configured lore installation, a valid knowledge_dir, and strict quoting rules for all tool inputs and arguments. These prerequisites ensure the simulated tool calls can accurately validate structure and location.

How do I audit pattern coverage for PreToolUse hook queries?▼

You audit pattern coverage by running the coverage-check on a single pattern file path. It simulates 3-6 tool-call extractions that a real agent would issue, ingests the target file, and generates a surface-queries report to highlight vocabulary gaps.

Why does my pattern not surface in automated lore checks?▼

Your pattern may not surface in automated lore checks due to vocabulary gaps between its prose and metadata. This Skill simulates tool calls to identify these gaps, ensuring terms and concepts appear in both so the PreToolUse hook surfaces the right results.

Can I validate multiple pattern files at once for vocabulary gaps?▼

No, you cannot validate multiple pattern files at once. The coverage check operates on a single pattern file path, simulating 3-6 tool-call extractions to ingest the target file and report surface coverage gaps with actionable edits for that specific pattern.