Agent coordination
Coordination protocol for agents accessing the knowledge base. Use when any agent needs to fetch prior notes, templates, or reference documents from the vault. Triggers: fetch prior notes, access templates, find reference docs, get the template, find a prior document, previous work on, standing document, how did we handle this beforeFrom its SKILL.md
npx -y skills add Elnora-AI/knowledge-vault --skill agent-coordinationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.4 KB, as published. Nobody here has run it
Agent Coordination
The Rule
Call knowledge-base UNLESS you already have all context to finalize the task.
Default: proactive checking. Not reactive.
When to Call
| Category | Trigger Phrases |
|---|---|
| Reference docs | "the reference doc on", "our standard process for", "the how-to for" |
| Templates | "get the template", "our standard [document]", "find a template for" |
| Standing docs | "the standing document on", "our conventions for", "the runbook for" |
| Procedures | "how do we handle", "our process for", "the steps for" |
| Prior Work | "previous note on", "how did we handle [X] before", "prior agreement with" |
Skip When
- Pure code generation (no vault context)
- General knowledge (not vault-specific)
- Context already fetched this task
- Facts already covered by your project instructions (use CLAUDE.md / README)
Vault Path
Read .claude/knowledge-base.local.md for vault_path and vault_dir. Never hardcode paths. See the vault-access skill for tool selection and patterns.