notion

Define canonical Notion database schemas and read/write operations for SalesSidekick.

1|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/chieflatif/SalesSidekick-Claude-CoWork --skill notion-chieflatif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: notion
Source: https://github.com/chieflatif/SalesSidekick-Claude-CoWork/tree/main/skills/notion
Command: npx skills add https://github.com/chieflatif/SalesSidekick-Claude-CoWork --skill notion-chieflatif

SYSTEM DOCUMENTATION & REQUIREMENTS

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.

Frequently Asked Questions about notion

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I prevent Notion schema drift and inconsistent field mappings?

Notion schema drift is prevented by centralizing canonical schemas and field mappings. This enforces consistent validation across six databases to eliminate data loss and confusing account resolution.

How does account resolution work when matching company mentions in Notion databases?

Account resolution uses prioritized matching logic including exact, starts-with, and contains rules. It provides disambiguation prompts to reliably map user mentions to the correct company and deal records.

How do I handle Notion write failures and transient API errors?

Notion write failures are handled using non-silent failure reporting, retry on transient errors, diagnostic suggestions, and manual fallback presentation. Failures are logged for later audit purposes.

What is the best way to set up Notion databases with correct relations and selects?

The best way to set up Notion databases is by running a setup command that enforces dependency ordering for database creation. This ensures correct relations and selects are populated consistently.

Can I use this to synchronize call notes and forecast updates across multiple Notion databases?

Yes, you can use deterministic read/write patterns to synchronize call notes and forecast updates. The command-level mappings ensure /forecast-update reads stage probabilities and /closeout writes to multiple databases consistently.