This skill provides comprehensive instructions for interacting with the Notion API via REST calls. This skill should be used whenever the user asks to interact with Notion, including reading, creating, updating, or deleting pages, databases, blocks, comments, or any other Notion content. The skill covers authentication, all available endpoints, pagination, error handling, and best practices.
SkillScore100Maintained
Automatic
◆Knowledge Management pack
Last verified 8/21/2026
What it changes
Passed 23 of 23 test cases with the skill, and 13 of 23 without it.
Without skill57%
With skill100%
Checks it passed that the model alone missed
Sets parent type to database_id
Uses $NOTION_API_TOKEN for authorization
Uses the header Notion-Version: 2025-09-03
and 10 more in the full report
10 fixed13 passed either way0 still failing0 broke
Pass-rate lift
+43 pp
Tokens
+232%
Agent turns
0%
Response time
-41%
Model gemini-3.6-flashMeasured 8/21/2026v123 of 23 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
Look up any accessible workspace pages containing 'Q3 Roadmap' in Notion using a terminal curl command. Provide the API request snippet formatted to pipe into jq.
What was checked, without and with the skill
Checked
Without skill
With skill
Includes the header Notion-Version: 2025-09-03
Missed
Passed
Uses $NOTION_API_TOKEN for the Bearer authorization header
Missed
Passed
case-01 · gemini-3.6-flash · 8/21/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md432 linessingle file
|-------|
| Maximum block elements per payload | 1000 |
| Maximum payload size | 500KB |
| Rich text content | 2000 characters |
| URLs | 2000 characters |
| Equations | 1000 characters |
| Email addresses | 200 characters |
| Phone numbers | 200 characters |
| Multi-select options | 100 items |
| Relations | 100 related pages |
| People mentions | 100 users |
| Block arrays per request | 100 elements |
Confirmation for Destructive Operations
IMPORTANT: Before executing any operation that modifies or deletes data, ask the user for confirmation. This includes:
Updating pages or blocks
Deleting/archiving pages or blocks
Modifying database schemas
Creating pages (if multiple or in batch)
Any bulk operations
For a logical group of related operations, a single confirmation is sufficient.
When the user wants to optimize post-signup onboarding, user activation, first-run experience, or time-to-value. Also use when the user mentions "onboarding flow," "activation rate," "user activation," "first-run experience," "empty states," "onboarding checklist," "aha moment," "new user experience," "users aren't activating," "nobody completes setup," "low activation rate," "users sign up but don't use the product," "time to value," or "first session experience." Use this whenever users are si