CtrlK
BlogDocsLog inGet started
Tessl Logo

notion-api

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.

89

1.16x
Quality

84%

Does it follow best practices?

Impact

100%

1.16x

Average score across 3 eval scenarios

SecuritybySnyk

High

Do not use without reviewing

The canonical home for this skill is notion-api in intellectronica/agent-skills

SKILL.md
Quality
Evals
Security

Quality

Content

76%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-organized API reference with strong progressive disclosure via real reference files. The main gaps are token-efficient header handling and the absence of explicit error-recovery feedback loops for destructive/batch operations.

Suggestions

Factor the repeated Authorization/Notion-Version/Content-Type headers into a shared snippet or shell variable to cut repetition across the many curl examples and improve conciseness.

Add an explicit validate→fix→retry feedback loop for destructive and batch operations (e.g., retrieve-after-write verification and a re-prompt/retry path on validation failure) to lift workflow clarity above the destructive-op cap.

Consider moving the inline Request Size Limits and Error Handling reference tables into a references file so the SKILL.md body reads as a leaner overview pointing to detail.

DimensionReasoningScore

Conciseness

The body is dense with executable curl examples and avoids explaining concepts Claude already knows, but the three standard request headers are repeated verbatim in every example — tokens that could be factored out. Not a 5 because not every token earns its place.

4 / 5

Actionability

Every endpoint ships a complete, copy-paste-ready curl command with real URLs, required headers, and full JSON bodies covering the common cases (search, pages/blocks/databases CRUD, users, comments).

5 / 5

Workflow Clarity

Auth flow, pagination loop, and a destructive-operation confirmation gate are sequenced, but there is no explicit validate→fix→retry feedback loop for batch/destructive operations, which the rubric caps at 3.

3 / 5

Progressive Disclosure

Four real reference files are one level deep and well-signaled both inline ("See references/filters-and-sorts.md") and in a References section, but the body itself is a full inline endpoint reference rather than a lean overview, keeping it just below the ideal-split anchor.

4 / 5

Total

16

/

20

Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly conveys capability and trigger conditions for Notion API work. Minor improvement possible by adding natural synonyms users might say (e.g., "Notion workspace", "Notion docs").

DimensionReasoningScore

Specificity

Lists multiple concrete CRUD actions ("reading, creating, updating, or deleting") applied to named object types (pages, databases, blocks, comments), matching the comprehensive-coverage anchor.

5 / 5

Completeness

Explicitly states both what it does ("interacting with the Notion API via REST calls", covering auth/endpoints/pagination/error handling) and when to use it ("should be used whenever the user asks to interact with Notion"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good natural-term coverage ("interact with Notion", "Notion API", pages/databases/blocks/comments) but misses common synonyms like "Notion workspace" or "Notion docs", falling just short of the comprehensive-synonym anchor.

4 / 5

Distinctiveness Conflict Risk

Scoped narrowly to the Notion API with distinct triggers, giving it a clear niche with minimal overlap risk against other skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
intellectronica/agent-skills
Reviewed

Table of Contents

Is this your skill?

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.