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.
86
78%
Does it follow best practices?
Impact
100%
1.16xAverage score across 3 eval scenarios
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/notion-api/SKILL.mdPagination and rate-limit handling
Uses curl for requests
100%
100%
Uses jq for JSON parsing
0%
100%
Correct API version header
0%
100%
Authorization header pattern
50%
100%
Token not echoed or logged
100%
100%
Pagination loop uses has_more
100%
100%
Uses next_cursor as start_cursor
100%
100%
Loops until has_more is false
100%
100%
Exponential backoff on 429
100%
100%
Backoff documented
100%
100%
Pagination described
100%
100%
Structured page creation with block limits
Uses curl for API calls
100%
100%
Uses jq for JSON processing
100%
100%
Correct API version header
0%
100%
Content-Type header present
100%
100%
Token not exposed
100%
100%
Page parent uses page_id key
100%
100%
Max 100 blocks per append call
100%
100%
Stores returned page ID
100%
100%
Content retrieved via blocks endpoint
100%
100%
Blocks split if needed, documented
100%
100%
Parent type documented
100%
100%
Code block uses correct type
100%
100%
Confirmation before destructive bulk operations
Confirmation before archiving
100%
100%
Single confirmation for batch
100%
100%
No changes if declined
100%
100%
Confirmation documented
100%
100%
Uses curl for API calls
100%
100%
Correct API version header
0%
100%
Token not exposed
100%
100%
Archive via archived flag
100%
100%
Uses jq for JSON
100%
100%
Logs archive operations
100%
100%
Preview before confirmation
100%
100%
9f7f750
Table of Contents
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.