What problem does it solve?
This skill ensures every CRM entry has a connected, human-readable Markdown document that acts as the primary long-form record and audit trail, and it keeps that document synchronized with the entry's metadata in DuckDB via the documents table and mutation logs.
Core Features & Use Cases
- Automatically creates or repairs a connected entry document when an entry is created or mutated, ensuring a registered file path, appropriate title, and linkage to the entry_id and parent_object_id.
- Keeps an activity log within the entry document to record mutations and changes for an auditable history.
- Enforces naming conventions and cross-nesting rules so documents live under the correct object directory while remaining discoverable and human-readable.
- Supports standalone object-level documents in addition to entry documents, with clear distinction in the documents table.
- Synchronizes Markdown content with metadata in DuckDB, updating or creating the relevant documents row as needed to maintain consistency.
Quick Start
Create or update an entry and automatically generate or repair its connected Markdown document, register it in DuckDB, and append an activity log.