Identify vocabulary gaps between pattern wording and PreToolUse hook queries.
npx skills add https://github.com/attila/lore --skill coverage-check-attila
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
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.
Run coverage-check on a single pattern file path to generate a surface-queries report.
High-intent search queries and answers about installing and using this skill.
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.
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.
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.
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.
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.
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.
pavelkraleuGenerate GLB-backed IKEA METOD cabinet instances with parametric scene JSON.
xotongRestrict file edits to a user-specified directory for the current session.
attilaQuery the Lore index via MCP to retrieve coding conventions and patterns.
marius-bughiuGenerate data-driven prep briefings for weekly forecast calls from pipeline snapshots.
