notion-automation

Automate Notion tasks via Rube MCP (Composio): pages, databases, blocks, comments, users. Always search tools first for current schemas.

2.08x

Quality

—

Does it follow best practices?

Impact

98%

2.08x

Average score across 3 eval scenarios

Securityby

Advisory

Suggest reviewing before use

Quality

Content

65%

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 concrete tool slugs, parameters, and filter examples, and workflows are clearly sequenced. It is held back by redundancy between sections and the absence of explicit validation feedback loops for destructive and batch operations.

Suggestions

Add explicit validate->fix->retry checkpoints for destructive and batch operations (archive page, delete block, replace content, database inserts/updates) to lift workflow_clarity.

De-duplicate content between the per-workflow Pitfalls, the Known Pitfalls section, and the Quick Reference table so each fact lives in one place.

Split the large Quick Reference table and detailed parameter lists into a bundled reference file and link to it from SKILL.md to improve progressive_disclosure.

Dimension	Reasoning	Score
Conciseness	It assumes Claude's competence (no "what is Notion" padding) and sections are lean, but the Quick Reference table and Known Pitfalls repeat tool slugs, params, and pitfalls already covered in the per-workflow sections, so it could be tightened.	2 / 3
Actionability	It provides exact tool slugs, precise parameter names (content_blocks vs child_blocks, database_id), concrete JSON filter examples, and a copy-paste-ready quick reference, all matching the level-3 anchor for fully executable guidance.	3 / 3
Workflow Clarity	Tool sequences are clearly ordered with Prerequisite/Required/Optional markers and the Setup step gates on ACTIVE status, but destructive/batch operations (archive, delete block, replace content, database updates) lack explicit validate->fix->retry feedback loops, which the rubric caps at 2.	2 / 3
Progressive Disclosure	The body is well-organized into clear one-level sections with no dead or nested references, but no bundle files exist and the ~213-line monolithic content (20-row reference table plus detailed per-workflow tool sequences) keeps material inline that could be split, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

72%

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 concrete and clearly niche-scoped with good natural trigger terms, but it omits an explicit "Use when..." clause, capping its completeness. Adding when-to-use trigger guidance and explicit action verbs would raise specificity and completeness.

Suggestions

Add an explicit "Use when..." trigger clause (e.g. "Use when the user wants to automate Notion pages, databases, comments, or workspace users") to raise completeness to 3.

Replace object-noun lists with concrete action verbs (e.g. "create, query, update, archive pages and databases") to strengthen specificity.

Include a few more natural user phrasings (e.g. "Notion database rows", "comments on a page") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	It names the Notion domain and lists multiple concrete object types ("pages, databases, blocks, comments, users") but states them as nouns rather than enumerating specific actions (e.g. create, query, archive), so it sits just below the level-3 anchor's explicit verb list.	2 / 3
Completeness	It clearly answers "what" (automate Notion tasks) but lacks any "Use when..." or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural terms a user would say when needing Notion automation ("Notion tasks", "pages", "databases", "blocks", "comments", "users") give good coverage, matching the level-3 anchor's breadth of natural vocabulary.	3 / 3
Distinctiveness Conflict Risk	It is scoped to a specific niche (Notion automation via Rube MCP/Composio) with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	10 / 12 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: davepoon/buildwithclaude
Commit: 366e45b

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.