notion

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

1.57x

Quality

71%

Does it follow best practices?

Impact

99%

1.57x

Average score across 3 eval scenarios

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./openclaw/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 content is highly actionable with executable examples throughout and is efficiently written, but it lacks validation/feedback checkpoints around its destructive and batch database operations, and inlines reference material that would benefit from separation.

Suggestions

Add an explicit verify/validate step after create/update/query operations (e.g., re-fetch the page or check the response status) and an error-recovery note for failed writes.

Move the Property Types catalog and Key Differences reference into separate reference files, leaving SKILL.md as an overview with one-level-deep links.

Add a short troubleshooting note for common Notion API failure modes (rate limiting, invalid_version, integration not shared) to close the feedback loop.

Dimension	Reasoning	Score
Conciseness	The body is lean and jumps straight into setup and executable curl commands without padding concepts Claude already knows, with only minor tightening possible in the Notes section.	4 / 5
Actionability	Every common operation has a fully executable, copy-paste curl example, and property-type formats are concrete, covering the common cases completely.	5 / 5
Workflow Clarity	Setup is a clear numbered sequence, but the create/update/Query operations are destructive or batch database operations with no validation or error-recovery checkpoints, which the rubric caps at 3.	3 / 5
Progressive Disclosure	Sections are well-organized with no nested references (no bundle files exist), but the ~155-line body inlines a sizable API reference and property-type catalog that could live in separate files.	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 concise and names a clear, distinctive niche with concrete resource types, but it omits any explicit "when to use" trigger guidance. Adding a Use-when clause would lift completeness and distinctiveness.

Suggestions

Append a 'Use when...' clause naming natural triggers (e.g., 'Use when the user asks to read, create, or update Notion pages, databases, or blocks').

Mention the 2025 'data sources' terminology or common synonyms ('Notion pages', 'Notion docs') to broaden trigger coverage.

Add a couple more concrete verbs (read, query, update) to round out the action list toward full coverage.

Dimension	Reasoning	Score
Specificity	"creating and managing pages, databases, and blocks" names the Notion domain plus several concrete resource types and verbs, with minor gaps in action variety versus a fully comprehensive list.	4 / 5
Completeness	It gives a clear "what" (creating/managing pages, databases, blocks) but no "Use when..." or equivalent trigger guidance, which the guideline caps at 3.	3 / 5
Trigger Term Quality	"Notion", "pages", "databases", and "blocks" are natural terms users say, though common synonyms like "notes", "docs", or the 2025 "data sources" term are missing.	4 / 5
Distinctiveness Conflict Risk	"Notion API" is a clear niche with distinct triggers and minimal overlap risk, though no explicit trigger phrases reinforce the niche to push it to 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: trpc-group/trpc-agent-go
Path: openclaw/skills/notion/SKILL.md
Commit: ba4a78e

Reviewed: 1 day 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.