notion

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/notion/SKILL.md

The canonical home for this skill is notion in Hung-Reo/hungreo-openclaw

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.

The body is a tight, copy-paste-ready Notion API cookbook with strong actionability and clean organization. Its main weakness is the absence of validation/verification steps for create and update operations, which caps workflow clarity.

Suggestions

Add a verification step after create/update operations (e.g., re-fetch the page to confirm the change applied).

Consider moving the Property Types reference and full endpoint catalog into a separate REFERENCE.md to improve progressive disclosure.

Factor the common curl headers (Authorization, Notion-Version, Content-Type) into a single documented snippet to reduce repetition and token weight.

Dimension	Reasoning	Score
Conciseness	Lean, executable curl cookbook that assumes Claude's competence and avoids explaining Notion basics; the repeated Notion-Version header across nine examples is mildly token-heavy but functionally required.	4 / 5
Actionability	Fully executable, copy-paste-ready curl commands cover the common cases (search, get page, get blocks, create/query data sources, update, add blocks) plus a concrete property-type reference.	5 / 5
Workflow Clarity	Setup is a clear numbered sequence, but create/update database operations lack any validation or verification step, so workflow clarity is capped at 3 per the feedback-loops guidance for database/destructive operations.	3 / 5
Progressive Disclosure	Well-organized with clear section headers and self-contained navigation; at ~160 lines it exceeds the 50-line simple-skill exception and could split the property/reference material into a separate file, so it is not a 5.	4 / 5
	Total	16 / 20 Passed

Description

66%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.

The description is specific and clearly tied to the distinct Notion niche, but it omits any 'Use when' trigger guidance, which caps completeness and limits trigger-term quality. Adding an explicit usage trigger would lift the weaker dimensions.

Suggestions

Add an explicit 'Use when ...' clause naming natural triggers (e.g., 'Use when creating or managing Notion pages, databases, or blocks').

Broaden action coverage to mention querying/updating (e.g., 'create, read, update, and query') for more comprehensive specificity.

Include common synonyms/extensions users say (e.g., 'Notion pages', 'Notion databases', 'Notion blocks') to improve trigger-term quality.

Dimension	Reasoning	Score
Specificity	Names the domain ('Notion API') and several concrete actions ('creating and managing') across enumerated object types ('pages, databases, and blocks'), with minor gaps such as querying, updating, or deleting.	4 / 5
Completeness	Provides a clear 'what' but no 'when' / explicit trigger guidance, so completeness is capped at 3 per the judging guidelines.	3 / 5
Trigger Term Quality	Good natural keyword coverage ('Notion API', 'pages', 'databases', 'blocks') that users would say, but missing synonyms, file extensions, or an explicit 'Use when' trigger phrase.	4 / 5
Distinctiveness Conflict Risk	'Notion API' is a clearly distinct niche with minimal conflict risk, but the absence of explicit trigger phrases keeps it just below a 5.	4 / 5
	Total	15 / 20 Passed

Validation

81%

Warnings & errors only

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

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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: Bitterbot-AI/bitterbot-desktop
Path: skills/notion/SKILL.md
Commit: 017761f

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.