knowledge-router

Knowledge Router — Vault First, Skills Second

Core behavioral contract for every substantive question from a Clickeon teammate.

The rule

Before answering ANY question about clients, sites, decisions, past work, research findings, or Daniel's stated opinions:

1. Search the vault first via mcp__gw-vault__search_vault. Use terms the teammate mentioned. Narrow by folder when you can:
   • folder: "Clients" — client history, past audits, proposals, account health
   • folder: "Sites" — deploy history, incidents, site ops, fixes
   • folder: "Intel" — industry news, competitor moves, algorithm updates
   • folder: "Decisions" — architectural / strategic decisions and reasoning
   • folder: "Daily" — Daniel's session logs (recent work)
   • folder: "Research" — methodologies, standards, playbooks
   • folder: "Strategy" — content plans, topical maps
2. Read the relevant notes via mcp__gw-vault__read_vault_note (pass the path from search_vault results). Cite the note titles you used in your answer.
3. Only if the question is a TASK (write content, audit a site, do keyword research, create something), check the skill catalog via mcp__gw-skills__list_skills with the teammate's role, then match their task against skill triggers.
4. Fall back to general knowledge only when vault + skills both come up empty. Say so explicitly: "No vault notes match; no skill matches; here is general knowledge."

Order is non-negotiable: vault → skills → general.

Why vault first

A teammate asking "what did we decide about broker verification for WikiFX?" does not need a skill. The answer lives in Decisions/ or Clients/. Skill-first routing wastes tokens and misses the obvious answer. Vault-first routing treats the skill catalog as one possible answer, not the default frame.

Tools available

gw-vault (Priority #1 — always try first)

Tool	Input	What it does
search_vault	query, optional folder, optional max_results	Full-text grep with context lines around matches
read_vault_note	path (relative to vault root)	Reads the full note, truncated at 50K chars
list_vault_folder	optional folder, optional recursive	Lists files with name/type/size/modified

gw-skills (Priority #2 — only for task requests)

Tool	Input	What it does
list_skills	optional role	Returns skill catalog filtered by role
get_skill_detail	skill_name, optional include_references	Returns the full SKILL.md for a named skill

Concrete routing examples

Teammate asks	Correct routing
"What did we decide about AI citation strategy?"	search_vault(query: "AI citation", folder: "Decisions") → cite note
"What client work have we done on forex broker reviews?"	search_vault(query: "forex broker review", folder: "Clients") + Sites/
"What did Daniel log yesterday about the gateway?"	search_vault(query: "gateway", folder: "Daily") → recent-first
"Summarize the Paperclip attribution bug fix"	search_vault(query: "Paperclip attribution", folder: "Sites") → read + summarize
"Write me an article about USDJPY"	search_vault(query: "USDJPY") first for past context → THEN list_skills → route to content-create
"What skills do I have access to?"	list_skills(role: <caller role>) directly — no vault needed

Hard rules

• Never skip the vault search on a substantive question. Even if a skill looks like an obvious fit, vault first.
• Never invent note paths. Always call search_vault to get the real path, THEN read_vault_note.
• Never claim "no vault context" without searching. If a search returns zero hits, try a broader term or different folder before giving up.
• Cite note titles when you pull content from the vault. Teammates need the trail.
• The vault is read-only for teammates. No write tools are exposed; do not attempt to create or edit vault notes from this plugin.

Escape hatches

Three slash commands are available for manual browsing:

• /vault <query> — direct vault search
• /logs <query> — filter to Daily/ only (recent-first)
• /skills — show the role-filtered skill catalog

Gotchas

• Vault sync lag: the VPS vault copy pulls from GitHub on a cron. Notes written in the last ~5 minutes may not be searchable yet. If the teammate explicitly mentions very recent work, say so.
• Search is grep-based, not semantic. Use multiple term variants if the first query misses. Example: "broker verification" AND "verify broker" AND "verification process".
• 50K-char truncation on read_vault_note. Long notes are cut off — follow up with more targeted searches if you need the tail.
• Role filtering on list_skills: pass the teammate's role (qa, content, sales, team, founder) to narrow the catalog. Omitting it returns everything the caller can see, which may include skills not relevant to them.
• No LightRAG access yet. LightRAG is a Daniel-only semantic index; it is not exposed via the gateway. Text-grep via search_vault is all the plugin offers today.
• Gateway key is personal. If gw-vault or gw-skills returns 401, the teammate's gateway_key userConfig value is wrong. Ask them to re-run the plugin install flow and paste the key Daniel gave them.