Name: notion
Rating: 58.4 (1 reviews)
Author: membranedev

notion

Notion integration. Manage project management and document management data, records, and workflows. Use when the user wants to interact with Notion data.

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

68%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 highly actionable with executable commands and a strong connection workflow, and it is reasonably well-structured. The main weaknesses are some conceptual padding up front and a lack of validation checkpoints around destructive actions.

Suggestions

Remove or condense the opening paragraph explaining what Notion is, since Claude already knows this.

Add a validation/verification step before destructive actions (e.g. recommend fetching and confirming the target page/block before running delete-block or archive-page).

Consider moving the 'Popular actions' table into a separate ACTIONS.md reference file linked from the body to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is mostly command-focused and efficient, but opens with a paragraph explaining what Notion is ('an all-in-one workspace that combines note-taking, project management, and wiki functionalities') that Claude already knows, and includes some explanatory padding that could be trimmed.	3 / 5
Actionability	It provides copy-paste-ready, fully executable commands for every core operation (connection ensure, action list, action run, request) with flag tables and concrete JSON input examples covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence with feedback loops (poll until READY, handle CLIENT_ACTION_REQUIRED then re-poll), but the skill exposes destructive/batch actions (delete-block, archive-page, append-block-children) with no validation or verification checkpoint before executing them, capping this dimension at 3.	3 / 5
Progressive Disclosure	The single SKILL.md is well-organized into clear sections (install, auth, connecting, searching, running, proxy, best practices) with no nested references, but the large inline 'Popular actions' table is content that could live in a separate reference file, leaving a minor organization gap.	4 / 5
	Total	15 / 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 third-person, names a distinct niche (Notion), and includes an explicit 'Use when' trigger clause. Its weakness is generic action verbs and limited trigger-term variety, which keep specificity and trigger quality at mid-range.

Suggestions

Replace generic verbs with specific Notion actions, e.g. 'Query databases, create and update pages, append blocks, and search workspaces.'

Broaden the trigger phrase to include natural user terms, e.g. 'Use when the user wants to query, edit, or search Notion pages, databases, or blocks.'

Dimension	Reasoning	Score
Specificity	Names the domain ('project management and document management data, records, and workflows') with a few concrete actions, but the actions ('Manage... data, records, and workflows') are generic rather than specific verbs like query, create, or update, so coverage is not comprehensive.	3 / 5
Completeness	Both a 'what' (manage project/document management data, records, workflows) and an explicit 'when' ('Use when the user wants to interact with Notion data') are present, though the 'when' clause is somewhat generic and could name more concrete triggers.	4 / 5
Trigger Term Quality	It surfaces the natural keyword 'Notion' and 'Notion data', but offers no synonyms, file extensions, or common user phrasings beyond the app name, missing common variations.	3 / 5
Distinctiveness Conflict Risk	'Notion integration' names a specific third-party app with a distinct trigger ('interact with Notion data'), giving it a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	15 / 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: membranedev/application-skills
Path: skills/notion/SKILL.md
Commit: f484c82

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