knowledge-gate

Query team-verified Knowledge Vault constraints through the knowledge-gate CLI before code planning.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/ether-moon/knowledge-distillery --skill knowledge-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: knowledge-gate
Source: https://github.com/ether-moon/knowledge-distillery/tree/main/plugins/knowledge-distillery/skills/knowledge-gate
Command: npx skills add https://github.com/ether-moon/knowledge-distillery --skill knowledge-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the risk of unsafe code changes by surfacing team-verified constraints stored in the Knowledge Vault before planning edits.

Core Features & Use Cases

  • Hooks a UserPromptSubmit event to remind you to consult the vault when active entries exist.
  • Enforces vault access through the knowledge-gate CLI for read operations.
  • Helps surface conflicts, scope gaps, and guided decisions to keep changes compliant with team rules.

Quick Start

Enable the knowledge-gate hook and query relevant vault entries before planning code changes.

Frequently Asked Questions about knowledge-gate

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

FAQPage Schema
How do I surface team-verified constraints before planning code edits?

To surface team-verified constraints before planning code edits, enable a hook that triggers a pre-change query of relevant paths or domains. This identifies existing vault entries to guide your modifications and ensure safer edits.

What is a Knowledge Vault and how does it guide code planning?

A Knowledge Vault is a repository of team-verified constraints that guides code planning by surfacing conflicts and scope gaps. Querying it before modifications ensures your changes remain compliant with established team rules.

How do I query the Knowledge Vault using the CLI for pre-change validation?

Query the Knowledge Vault using the dedicated CLI for pre-change validation to enforce read operations. The system hooks your prompt submission, reminding you to consult relevant vault entries before you begin editing code.

Can I use a hook to remind developers to check team rules before coding?

Yes, you can use a UserPromptSubmit hook to remind developers to check team rules before coding. It automatically triggers when active vault entries exist, ensuring developers query relevant constraints for guided decisions.

Why does the system record usage when vault entries influence code decisions?

The system records usage when vault entries influence code decisions to maintain an audit trail of team-verified constraint consultations. This tracking ensures accountability and confirms that pre-change queries actively guided your edits.

What are the limitations of relying on a Knowledge Vault for code planning?

A limitation of relying on a Knowledge Vault for code planning is that guidance applies only where active vault entries exist. If constraints are missing from the vault, the hook cannot surface conflicts or scope gaps for those specific edits.