CtrlK
BlogDocsLog inGet started
Tessl Logo

notion

Notion API for creating and managing pages, databases, and blocks.

56

Quality

64%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/notion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%

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

The content is highly actionable with concrete, executable curl examples and clean section organization, but it stops short on workflow rigor by omitting validation/feedback checkpoints for database operations and carries minor redundancy. Adding verify steps for risky writes would push workflow clarity higher.

Suggestions

Add a validation step after create/update/query operations, e.g. re-fetch the page or database to confirm the change applied, to satisfy the feedback-loop expectation for database operations.

Remove the redundant "(databases)" parentheticals and consolidate the Notion-Version note into the API Basics section to tighten conciseness toward 3.

Clarify the database_id vs data_source_id workflow as an explicit sequenced procedure (search -> resolve data_source_id -> query) with a checkpoint confirming the correct ID was used.

DimensionReasoningScore

Conciseness

The body is mostly lean copy-paste curl examples, but carries minor redundancy such as the repeated parenthetical "(databases)" and a Note block restating the Notion-Version header, so it is efficient yet could be tightened to the lean level-3 anchor.

2 / 3

Actionability

Every common operation is given as a complete, executable curl command with correct headers and full JSON payloads (e.g. create-page properties, database query filters), matching the copy-paste-ready level-3 anchor.

3 / 3

Workflow Clarity

Setup is a clear numbered sequence and operations are grouped, but database create/query workflows lack validation or feedback checkpoints, and the scoring notes cap workflow_clarity at 2 for database operations without validate-fix-retry loops.

2 / 3

Progressive Disclosure

The single SKILL.md is well organized into clear sections (Setup, API Basics, Common Operations, Property Types, Key Differences, Notes) with no bundle files needed, satisfying the simple-skill allowance for a 3.

3 / 3

Total

10

/

12

Passed

Description

57%

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

The description cleanly identifies a specific, low-conflict niche and names the core API surfaces, but it lacks an explicit use-when trigger and stops short of enumerating multiple concrete actions. Adding a "Use when..." clause with natural user phrasing would raise completeness and trigger-term quality.

Suggestions

Append a 'Use when...' clause naming natural user phrasings, e.g. 'Use when creating or updating Notion pages, databases, or blocks via the Notion API.'

Expand the action list beyond the generic 'managing' to concrete verbs like 'create, read, update, query, and search' to lift specificity to 3.

Include common user-facing terms such as 'Notion page', 'Notion database', and '.csv export' equivalents to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain and concrete objects ("creating and managing pages, databases, and blocks") but "managing" is generic and does not enumerate multiple distinct specific actions, matching the level-2 anchor rather than the level-3 multi-action examples.

2 / 3

Completeness

It clearly states what the skill does but includes no "Use when..." clause or equivalent trigger guidance, which the guidelines explicitly cap at 2.

2 / 3

Trigger Term Quality

Relevant keywords ("Notion API", "pages", "databases", "blocks") are present but common natural variations a user would say (e.g. "Notion page", "create Notion database") are missing, placing it at the some-relevant-keywords level rather than full coverage.

2 / 3

Distinctiveness Conflict Risk

"Notion API" is a clearly specific niche tied to a single product, making it unlikely to trigger for or conflict with other skills.

3 / 3

Total

9

/

12

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

13

/

16

Passed

Repository
wanikua/danghuangshang
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.