What problem does it solve?
Notion schema drift, inconsistent field mappings, and unreliable writes cause data loss, broken automations, and confusing account resolution across SalesSidekick workflows. This Skill centralizes the canonical schemas, account resolution rules, and read/write patterns so every command reads and writes Notion consistently and predictably.
Core Features & Use Cases
- Canonical Schemas: Defines all six Notion databases (70 fields total) so commands can validate fields and populate selects consistently.
- Account Resolution: Prioritized matching logic (exact, starts-with, contains) and disambiguation prompts to reliably map user mentions to the correct company and deal.
- Read/Write Patterns: Command-level read/write mappings (e.g., /closeout writes to multiple DBs, /forecast-update reads stage probabilities) and dependency ordering for database creation during setup.
- Write Failure Handling: Non-silent failure reporting, retry on transient errors, diagnostic suggestions, manual fallback presentation, and failure logging for /audit.
- Use Cases: Running /setup to create DBs with correct relations and selects, using /add-company and /add-deal to create records without schema errors, and using /prep, /strategy, /closeout, and /forecast-update with consistent data.
Quick Start
Run the SalesSidekick setup and then ask the assistant to prepare a company briefing for Acme Corporation using Notion database data.