CtrlK
BlogDocsLog inGet started
Tessl Logo

notion-automation

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

78

2.08x
Quality

69%

Does it follow best practices?

Impact

98%

2.08x

Average score across 3 eval scenarios

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/all-skills/skills/notion-automation/SKILL.md
SKILL.md
Quality
Evals
Security

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 a well-structured, mostly actionable reference that assumes Claude's competence, but destructive and batch workflows lack explicit validation checkpoints, and the single-file layout has minor redundancy between the workflow sections and Quick Reference table.

Suggestions

Add explicit validation checkpoints to destructive workflows, e.g. "Verify page_id via RETRIEVE_PAGE before ARCHIVE_NOTION_PAGE" and "Confirm row count before REPLACE_PAGE_CONTENT".

Add a verify-after step for batch reads ("stop paginating only when has_more is false; assert expected row count") to satisfy the batch-operation feedback-loop requirement.

Either trim the Quick Reference table to only tools not already detailed in the workflow sequences, or move the full parameter reference to a separate REFERENCE.md to reduce redundancy.

DimensionReasoningScore

Conciseness

Dense and assumes Claude's competence with no concept over-explanation, but the Quick Reference table partly duplicates the per-workflow tool sequences and parameter lists, introducing minor redundancy.

4 / 5

Actionability

Concrete tool sequences with named tools, key parameters, and JSON filter examples are actionable, though there are no complete example tool-call payloads showing a full request/response, leaving minor gaps.

4 / 5

Workflow Clarity

Sequences are clearly numbered with [Prerequisite]/[Optional]/[Required] tags and one setup checkpoint (confirm ACTIVE), but destructive operations (ARCHIVE_PAGE, DELETE_BLOCK, REPLACE_PAGE_CONTENT) and batch database reads lack explicit verify-before/verify-after checkpoints, capping this at 3 per the destructive-operations guideline.

3 / 5

Progressive Disclosure

Well-organized into clearly navigable sections (Prerequisites, Setup, five Core Workflows, Common Patterns, Pitfalls, Quick Reference) with no nested references, though it is a monolithic single file rather than a split overview-plus-reference structure.

4 / 5

Total

15

/

20

Passed

Description

70%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 clearly distinct, naming Notion's main object types, but it omits any explicit "Use when..." trigger guidance, relying on a procedural "search tools first" instruction instead. Adding a concrete trigger clause would lift completeness.

Suggestions

Append an explicit trigger clause, e.g. "Use when the user wants to manage Notion pages, databases, blocks, comments, or workspace users."

Replace the generic "Automate Notion tasks" verb with a few concrete actions per object (e.g., "create and archive pages, query and update databases, append blocks").

Add natural synonyms/file references users say (e.g., "Notion DB", "Notion docs") to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists several specific Notion object categories ("pages, databases, blocks, comments, users") giving broad coverage, though the only action verb is the generic "Automate Notion tasks" rather than per-object actions.

4 / 5

Completeness

The "what" is clear (Automate Notion tasks across pages/databases/blocks/comments/users) but there is no "Use when..." trigger clause; "Always search tools first for current schemas" is a procedural instruction, not usage guidance, so completeness is capped at 3.

3 / 5

Trigger Term Quality

Strong natural keywords users would actually say ("Notion", "pages", "databases", "comments", "users"), but missing common synonyms and explicit trigger phrases.

4 / 5

Distinctiveness Conflict Risk

The Notion-specific framing anchored to Rube MCP (Composio) carves a clear niche with distinct triggers and minimal overlap with other skills.

5 / 5

Total

16

/

20

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
davepoon/buildwithclaude
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.