vault-gap

Scan the vault to classify topic coverage and return a structured payload.

1|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/wtyler2505/ProtoPulse --skill vault-gap
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: vault-gap
Source: https://github.com/wtyler2505/ProtoPulse/tree/main/.claude/skills/vault-gap
Command: npx skills add https://github.com/wtyler2505/ProtoPulse --skill vault-gap

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bash, git, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The vault-gap skill assesses whether Ars Contexta vault coverage exists for a given topic, and if coverage is thin or missing, auto-drafts an inbox stub and queues a gap-stub for extraction, all while respecting the inbox → /extract → knowledge pipeline (never writing directly to knowledge/).

Core Features & Use Cases

  • Coverage assessment: searches the vault to classify coverage as sufficient, thin, or missing and reports a structured payload.
  • Auto-seeding: if coverage is thin or missing, seeds an inbox stub under inbox/YYYY-MM-DD-<slug>.md with research questions to guide extraction.
  • Queueing & integration: appends a structured entry to ops/queue/gap-stubs.md to prioritize extraction and trace provenance back to the originating plan/task.
  • Use Case: plan authors can quickly validate topic coverage before authoring in-depth vault notes and research plans.

Quick Start

Invoke /vault-gap on a topic to evaluate vault coverage and auto-seed a stub when coverage is thin.

Frequently Asked Questions about vault-gap

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

FAQPage Schema
How do I identify knowledge vault coverage gaps for a research topic?

Vault coverage gaps are identified by scanning the vault to classify topic coverage as sufficient, thin, or missing, then returning a structured payload for research logs. This assessment guides whether further extraction is needed.

How does auto-seeding a research inbox stub work for thin vault coverage?

Auto-seeding an inbox stub drafts a file under inbox/YYYY-MM-DD-<slug>.md containing research questions to guide extraction. This automatically happens when vault coverage is classified as thin or missing.

Can I write extracted research notes directly to the knowledge directory?

No, you cannot write directly to the knowledge directory. The process strictly respects the inbox to extract to knowledge pipeline, ensuring all stubs are queued and processed before final integration.

How do I queue missing vault topics for later extraction?

Queueing for extraction appends a structured entry to ops/queue/gap-stubs.md to prioritize extraction and trace provenance back to the originating plan or task. This ensures systematic processing of coverage gaps.

Do I need bash and git to automate vault gap analysis?

Yes, bash and git are required dependencies to run the vault-gap analysis. These tools support the automated scanning of the vault and the file operations needed to seed inbox stubs and queue entries.

What is the best way to validate topic coverage before authoring research plans?

Plan authors use vault-gap to quickly validate topic coverage before authoring in-depth vault notes and research plans. It provides a structured payload that can be pasted directly into a plan's Research log.