Notion Sync

**Judgement:** A feature-rich, well-documented Notion–Markdown sync and database management skill that is highly suitable for scripted and agent-driven workflows, provided you are comfortable granting it write access to your Notion workspace. **What it does well** - Supports both Markdown → Notion and Notion → Markdown with reasonable formatting preservation. - Strong database tooling: search, filtered queries, property and batch updates, schema inspection, and page archival. - Designed for automation: consistent CLI interface, `--json` mode for machine-readable output, and rate-limit-aware batching. - Good operational safeguards: path-safety defaults, `--dry-run` for batch updates, non-destructive "archive" instead of hard delete, and safer token handling. **Key risks / limitations** - Write operations are powerful: batch updates and archival can affect many pages; misconfigured filters or IDs can cause broad unintended changes. - Formatting fidelity is good but not perfect (complex tables, deeply nested lists may degrade), so round-trips may need manual review for complex documents. - Large documents (>1000 blocks) can be slow to sync due to inherent Notion API rate limits. - Some database property interactions (especially inline databases) can be temperamental per the Notion API. **Recommended scenarios** - Teams or agents that maintain Markdown-first content but need Notion as the shared collaboration or review surface. - Research, writing, or project-management agents that must query/update Notion databases and keep statuses/tags in sync. - Automated pipelines (cron, CI, orchestrators) that publish generated reports to Notion, watch for edits, and pull changes back into a local repo. - Power users who want a CLI-first way to manage Notion content safely, with JSON outputs suitable for integration into larger systems.