Manage MotherDuck Guides

Source Of Truth

• Prefer the current MotherDuck Guides documentation and MCP tool descriptions.
• For analytical queries through MCP, call get_query_guide before writing SQL, then traverse only relevant topics and Guides.
• get_dive_guide and get_flight_guide automatically include summaries from the reserved dives and flights topics; do not load those topics separately unless deeper context is needed.

Default Posture

• Keep one short root orientation Guide only when its guidance applies broadly. Put domain-specific knowledge under shallow, descriptive topics.
• Default new Guides to access = 'user'. Organization visibility requires an explicit request and the required admin permission.
• Write one coherent subject per Guide, with a discriminating title and description. Lead with rules, tested SQL, and named pitfalls.
• Attach references to the databases, shares, schemas, tables, columns, Dives, Flights, or Guides the content governs so agents discover it at the right time.
• Validate referenced objects and executable SQL against the live workspace before presenting a Guide as trustworthy.
• Use version comments to explain why guidance changed. Read before update and avoid overwriting concurrent work.

Workflow