bel-crm-db

Safe CRM data operations use a two-step pattern: execute a single write_query to insert the record, then execute a separate read_query to retrieve the generated ID. This approach respects MCP SQL constraints and allows you to link related records across sales_opportunity, person, and company_site entities without forbidden constructs.

The bel-crm-sql-rules define schema-aware patterns for CRM tables including company_site, person, sales_opportunity, and event. Key rules: use single-statement write_query and read_query calls, avoid RETURNING and ON CONFLICT clauses, and sequence insert-then-read operations to obtain IDs and maintain historical activity across related records.

Yes. The Skill manages activity tracking across company_site, person, and sales_opportunity by enforcing schema-aware insert and query patterns. Two-step write-then-read operations let you create linked records with proper ID sequencing while maintaining a complete audit trail.

MCP SQL constraints prohibit RETURNING clauses and ON CONFLICT syntax. These limitations require the two-step insert-and-read pattern instead of standard single-query approaches. Plan your workflow accordingly and always reference bel-crm-sql-rules before executing writes to avoid common errors.

After inserting a company_site with write_query, use a separate read_query to retrieve its ID. Then reference that ID in subsequent insert or update queries for related person and sales_opportunity records, maintaining relational integrity across your CRM schema.

Yes. The Skill handles CRM entities including data_files, enabling you to store and query file attachments alongside sales_opportunity, person, company_site, and event records using the same schema-aware, MCP-compliant SQL patterns.