// Generate a pre-meeting agenda with context gathered from the knowledge base
Run a quality audit on the knowledge base
Log a daily work check-in — records what was accomplished and syncs to task board
Manually refresh the knowledge base dashboard
Audit and clean up knowledge base state — archive completed work, fix inconsistencies
Classify raw content and route it to the appropriate knowledge base location
Process a meeting transcript — extract decisions, action items, and key discussion points into structured vault entries
| name | vault-prep |
| description | Generate a pre-meeting agenda with context gathered from the knowledge base |
| allowed-tools | ["vault_create_entry","vault_update_entry","vault_search","vault_kanban","vault_dashboard","ask_user"] |
Create or update a meeting prep file with topics and auto-gathered context.
Who is adding topics? Look for @mentions or ask.
vault_search(query: "prep", entry_type: "meeting") filtered to today's date.
vault_search(query: "*", entry_type: "meeting") last 3
vault_kanban(action: "list") filtered to items with meeting sourcesvault_search(query: "*", entry_type: "checkin") since last meeting
vault_search(query: "*", tags: ["okr"]) — check frontmatter for statusvault_search(query: "milestone", tags: ["in-progress"])From user input, extract:
CREATE: vault_create_entry(entry_type: "meeting", ...) with prep content, include prep_generated: true and contributors: ["{person}"] in extra_frontmatter
APPEND: vault_update_entry(append: "{person}'s topics:\n- [ ] Topic 1\n- [ ] Topic 2")
Also update contributors list in frontmatter.
Check for duplicate topics across contributors — note "(Also raised by {other person})" if similar.
CREATE: Topics added, context gathered (follow-ups count, async updates, at-risk items) APPEND: Topics added, existing agenda summary, current contributors list