vault-inbox

Convert vault note gaps into structured inbox stubs with queue entries.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Vault notes can be missing or result in a 404 on VaultHoverCard; this Skill turns such gaps into actionable inbox stubs and a queued process for extraction.

Core Features & Use Cases

  • Creates inbox stubs for user-submitted vault-note suggestions with deterministic slug derivation and collision handling.
  • Writes a record to ops/queue for downstream extraction and moderation reviews, enabling a structured, traceable pipeline.
  • Provides CLI helper and protocol documentation to guide UI integration and ensure consistent processing.

Quick Start

Submit a vault note suggestion via the VaultInbox UI or CLI; the system derives a slug, writes an inbox stub, and appends a queue entry for review.

Frequently Asked Questions about vault-inbox

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

FAQPage Schema
How do I automate inbox stub creation for missing vault notes?

To create inbox stubs from vault note gaps, submit descriptive input via UI or CLI. The system derives a deduplicated slug, writes a stub to the inbox, and appends a queue row for downstream extraction.

What is the process for routing user-submitted vault note suggestions?

Routing user-submitted vault note suggestions involves converting descriptive input into structured stubs using deterministic slug derivation with collision handling. The stub is written to the inbox with an appended queue entry for moderation.

How do I handle 404 errors on VaultHoverCard for missing notes?

Handling 404 errors on VaultHoverCard involves turning vault gaps into actionable inbox stubs. The system processes user-submitted suggestions, derives a slug, and queues the stub for downstream extraction and review.

Does the vault inbox queue support server-side sanitization and authentication?

Yes, the vault inbox queue enforces server-side sanitization, authentication, and moderation controls. These measures prevent abuse and maintain data hygiene during the slug derivation and stub creation process.

How do I integrate vault note suggestion submission into my UI?

You can integrate vault note suggestion submission using the provided CLI helper and protocol documentation. Submit suggestions via the VaultInbox UI or CLI, and the system automatically processes the input into a structured stub.

What's the best way to prevent duplicate entries in a vault inbox?

The best way to prevent duplicate entries in a vault inbox is using deterministic slug derivation with collision handling. The system automatically deduplicates slugs during the stub creation process to maintain data hygiene.