CtrlK
BlogDocsLog inGet started
Tessl Logo

notion

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

64

Quality

77%

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

87%

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

The content is a lean, highly actionable command reference with clean sectioning, but destructive and batch operations lack explicit validation feedback loops.

Suggestions

Add a brief validate/verify step after destructive and batch operations (e.g., confirm a trashed page is gone with `ntn pages get` before proceeding).

For bulk block insertion, show how to confirm the appended blocks succeeded before relying on them.

DimensionReasoningScore

Conciseness

The body is lean and command-first, assuming Claude's competence; it avoids explaining concepts Claude already knows and every section earns its place.

3 / 3

Actionability

It provides fully executable `ntn` and curl commands with concrete flags and copy-paste-ready examples across pages, data sources, files, and workers.

3 / 3

Workflow Clarity

Operations are grouped by command area, but destructive or batch operations like `pages trash`, file uploads, and bulk block PATCHes lack explicit validate-then-verify feedback loops, capping clarity at 2.

2 / 3

Progressive Disclosure

With no bundle files present, the single well-organized file with clearly labeled sections (Setup, Pages, Data sources, Raw API, etc.) meets the bar for a simple, self-contained skill.

3 / 3

Total

11

/

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 anchored to Notion, but lacks an explicit 'Use when...' trigger clause, which limits its completeness and natural trigger coverage.

Suggestions

Add an explicit 'Use when...' clause naming natural user phrasings, e.g. 'Use when the user asks to read or edit Notion pages, query Notion databases, or search Notion.'

Include common user-facing terms like 'Notion docs', 'Notion database', and 'search Notion' to broaden trigger coverage.

DimensionReasoningScore

Specificity

"pages, Markdown content, data sources, files, comments, search, Workers, and raw API calls" enumerates multiple specific concrete capabilities rather than vague language.

3 / 3

Completeness

The 'what' is explicit, but there is no 'Use when...' clause or equivalent trigger, which caps completeness at 2 per the judging guidelines.

2 / 3

Trigger Term Quality

Terms like pages, comments, search, and files are natural, but it leans on domain nouns and omits common user phrasings such as 'Notion docs' or 'search Notion'.

2 / 3

Distinctiveness Conflict Risk

It describes a clear Notion-specific niche with distinct terms, making it unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
OpenBMB/PilotDeck
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.