notion

Notion CLI/API for pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls.

Quality

81%

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

Quality

Content

87%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 exceptionally lean and actionable, with copy-paste commands and good sectioning. Its one gap is the lack of explicit validation/retry steps for destructive and batch operations.

Suggestions

Add a validation checkpoint after destructive calls (e.g. confirm the page is trashed with `ntn pages get` before declaring success).

Show a validate→fix→retry loop for block children PATCH and workers deploy (e.g. inspect `ntn workers runs logs <run-id>` and redeploy on failure).

Note how to verify `ntn api ls`/`--spec` output before issuing raw mutations, so risky raw-API calls get a preflight check.

Dimension	Reasoning	Score
Conciseness	Lean and command-first with no padding or explanations of concepts Claude already knows; time-sensitive material is isolated in a 'Version notes' section rather than inline.	5 / 5
Actionability	Copy-paste-ready ntn and curl commands with concrete flags, parent-ref syntax, and input-syntax notes cover the common cases end to end.	5 / 5
Workflow Clarity	Sections are well-organized but destructive/batch operations (pages trash, workers deploy, block children PATCH) lack explicit validate-then-retry checkpoints, capping workflow clarity at 3.	3 / 5
Progressive Disclosure	Single SKILL.md with clear, well-organized section headers and no external bundle files — meets the simple-skill exception for full marks.	5 / 5
	Total	18 / 20 Passed

Description

75%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 well-scoped to Notion, with strong trigger nouns and low conflict risk. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Notion pages, databases, files, comments, search, or Workers.'

Include natural synonyms or file extensions (e.g. '.md', 'Notion docs') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls — giving comprehensive coverage of what the skill does.	5 / 5
Completeness	The 'what' is clearly stated but there is no explicit 'Use when...' trigger clause, so completeness caps at 3 per the missing-trigger guideline.	3 / 5
Trigger Term Quality	Good natural keyword coverage (pages, files, comments, search) but leans on technical nouns like 'Workers' and 'data sources' and omits file extensions or synonyms.	4 / 5
Distinctiveness Conflict Risk	'Notion CLI/API' is a clearly defined niche with distinct triggers and minimal overlap with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: OpenBMB/PilotDeck
Path: skills/notion/SKILL.md
Commit: 9a33f4d

Reviewed: 2 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.