Skill
notion
Every Notion database queryable offline — cross-workspace SQL joins, stale detection, and relation graph traversal...
When to use notion
Choose if
You want SQL-style queries across Notion databases — cross-workspace joins, stale-page detection, relation graph traversal, change diffs since last sync — without burning 30 API calls per agent turn. Local SQLite mirror makes repeated context loads cheap. Pick this over raw Notion API clients when the agent needs to ask many questions in a single session.
Avoid if
You only need a single-call lookup that the Notion API already answers cheaply (the local-mirror setup is overkill), or your integration token hasn't been granted access to the databases — the CLI only sees what's explicitly shared and silently returns empty results otherwise.
Risk Flags
- MEDIUM auth Requires a Notion internal integration token (ntn_... format) and each database must be explicitly shared with that integration. Agents pointed at workspaces they think they can see but haven't been granted will get empty results rather than helpful errors.
- MEDIUM rate_limit Surfaces upstream throttling as exit code 7; the README discloses no concrete thresholds. Initial workspace sync alone takes 30-120 seconds depending on size, so latency-sensitive flows must let the local SQLite mirror warm up first.
- LOW scope Destructive operations (delete/archive) require --yes for confirmation and the README discloses no backup or rollback mechanism. Agents running mutations must handle their own undo.
- LOW runtime npx path needs Node.js; Go-source fallback needs Go 1.26.3+; MCP bundle integration needs Claude Desktop 1.0.0+.
Cost
Type: Unknown
Install
Default
npx -y @mvanhorn/printing-press install notion
Estimated time to first success: ~10 min
Dependencies
Minimum runtime: Node.js 18+ (or Go 1.26.3+; Claude Desktop 1.0.0+ for MCP bundle)
Distribution
- Repository
- https://github.com/mvanhorn/printing-press-library