notion

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

Quality

73%

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

Quality

Content

80%

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 and token-efficient with executable curl examples and no concept bloat, but it keeps all reference material inline and omits verification checkpoints after mutating API calls.

Suggestions

Move the Property Types table and full operation catalog into a referenced REFERENCE.md so SKILL.md stays a concise overview with one-level-deep navigation.

Add a verification step after mutating calls, e.g. "After creating/updating, GET /v1/pages/{id} to confirm the change took effect."

Dimension	Reasoning	Score
Conciseness	The body is lean curl examples plus terse reference tables, with no explanations of what Notion, an API, or curl is; the repeated headers across examples serve copy-paste executability rather than padding, matching the level-3 lean/efficient anchor.	3 / 3
Actionability	Every operation ships a fully executable curl command with real URLs, required headers, and concrete JSON payloads, plus a property-type cheat sheet, matching the level-3 copy-paste-ready anchor.	3 / 3
Workflow Clarity	Setup is numbered (1-4) and operations are sequenced, but mutating operations (create/update page, create data source) include no verification step (e.g. GET to confirm), so checkpoints are missing per the level-2 anchor.	2 / 3
Progressive Disclosure	The ~160-line body is a well-sectioned but monolithic inline API reference with no bundle files or split-out reference document, matching the level-2 example of API reference content that could live in a separate file.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 Notion-scoped with low conflict risk, but it lacks an explicit "Use when..." trigger clause and offers limited keyword variation, capping completeness and trigger term quality.

Suggestions

Add an explicit trigger clause, e.g. "Use when creating or updating Notion pages, databases (data sources), or blocks."

Broaden trigger keywords with natural variations users say, such as "Notion pages, databases, docs, wiki, or workspace content".

Dimension	Reasoning	Score
Specificity	"creating and managing pages, databases, and blocks" lists multiple concrete objects and operations, matching the anchor that enumerates several specific actions; it is more comprehensive than the level-2 "names domain and some actions" anchor.	3 / 3
Completeness	It clearly states what the skill does (Notion API for creating/managing pages, databases, blocks) but has no "Use when..." trigger clause, so per the judging guidelines completeness is capped at 2 for missing explicit when-guidance.	2 / 3
Trigger Term Quality	"pages, databases, and blocks" are relevant Notion keywords a user might say, but the description offers no common variations (e.g. Notion docs, wiki, notes), fitting the level-2 anchor of having some keywords but missing variations.	2 / 3
Distinctiveness Conflict Risk	"Notion API" names a clear niche with distinct triggers that would not plausibly fire for an unrelated skill, matching the level-3 anchor for a clear niche unlikely to conflict.	3 / 3
	Total	10 / 12 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: e73c717

Reviewed: about 16 hours 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.