CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

notion-integration

Integração completa com Notion usando MCP customizado (notion-automation-suite)

Quality

60%

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/integration/notion/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 delivers highly actionable, domain-specific operational knowledge — exact MCP tool signatures, database schemas, status enums, and formatting rules — with concrete examples for all four databases. Its weaknesses are structural: significant duplication across overlapping validation sections and repeated examples, no post-execution verification loop for batch card creation, and a monolithic inline structure with no reference files despite its size.

Suggestions

Deduplicate: the youtuber_create_series/episode and study_create_course/class example blocks appear twice nearly verbatim, and the GMT-3/emoji/relation-field rules are restated in Regras Críticas, Validações Obrigatórias, Checklist de Validação, and Erros Comuns — merge these into one rules section plus one error table.

Add a post-execution verification and failure-recovery step for batch operations (e.g. after study_create_course_complete, query the created hierarchy via study_query_schedule to confirm counts and fix/retry any missing cards).

Move the per-base schema details (properties, statuses, activity lists, emoji tables) into reference files (e.g. references/work.md, references/studies.md) and keep SKILL.md as an overview with per-base pointers.

DimensionReasoningScore

Conciseness

The body is information-dense with genuinely novel operational data (database schemas, status enums, field mappings, MCP tool signatures) and explains nothing Claude already knows. However, it could be tightened substantially: the youtuber_create_series/episode and study_create_course/class examples appear nearly verbatim twice, and the timezone/emoji/relation rules are restated across four overlapping sections (Regras Críticas, Validações Obrigatórias, Checklist, Erros Comuns). This is anchor 3 ('mostly efficient but could be tightened') rather than 2 because the padding is duplication, not concept explanation.

3 / 5

Actionability

Fully executable guidance: exact MCP tool names with parameters (work_create_project(title=..., cliente=..., ...)), property names, valid status values per base, ISO-8601 date formats with GMT-3 offsets, Docker run commands, and copy-paste Python snippets covering the common cases for all four databases. Matches anchor 5 ('fully executable; copy-paste ready code or commands; specific examples cover the common cases').

5 / 5

Workflow Clarity

Creation sequences are clear (parent first, then children via parent_id; the 'Execução Completa' rule; pre-creation checklist; hierarchy diagrams), but the skill's core workflows are batch operations (study_create_course_complete, youtuber_create_series auto-generating episodes) with no post-execution verification or failure-recovery loop — no step confirms a card was created correctly or what to do when an MCP call fails. Per the rubric's cap for batch operations without feedback loops, this is capped at 3 ('steps listed but validation gaps').

3 / 5

Progressive Disclosure

The body is well-organized with per-base sections, tables, and clearly named referenced paths (notion-automation-suite/config/README.md, docs/mcp/SETUP_CURSOR.md, config/CONTEXTO_GERAL.md), but no bundle files exist and all ~700 lines are inlined in SKILL.md — including ~250 lines of per-base schema/status reference that clearly belongs in separate files. Fits anchor 3 ('some structure but could be better organized; content that should be separate is inline') rather than 4, since the bulk schema reference is not offloaded anywhere.

3 / 5

Total

14

/

20

Passed

Description

40%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 identifies the domain (Notion via the notion-automation-suite MCP) but says nothing concrete about what the skill does or when to invoke it. "Integração completa" is generic filler with no actionable capability and no 'use when' guidance, so it would rarely be selected on its own merits.

Suggestions

Add concrete capabilities to the description, e.g. 'Create, update, and query cards across Notion work/studies/personal/YouTube databases via the notion-automation-suite MCP (projects, course hierarchies, series and episodes)'.

Append an explicit trigger clause such as 'Use when the user mentions Notion, cards, cursos, aulas, séries, tarefas, or asks to create/update project, study, or YouTube structures in Notion'.

Fold the natural trigger terms from the frontmatter triggers field into the description itself so the description carries its own trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Integração completa com Notion usando MCP customizado (notion-automation-suite)") but "Integração completa" states no concrete action — it never says what the integration does (create/update/query cards, courses, tasks). This matches anchor 2 ('names the domain but actions are minimal or generic'); it is not anchor 3 because no concrete capability is listed.

2 / 5

Completeness

The 'what' is vague ('Integração completa') and the 'when' is entirely missing — no 'Use when...' clause or equivalent trigger guidance in the description. This exactly matches anchor 2 ('has a vague what and no when'); it is not anchor 3 because the what fails to state any concrete actions.

2 / 5

Trigger Term Quality

"Notion" is a natural keyword a user would say, but the description misses the common terms users actually use for this skill (cards, tarefas, cursos, séries, aulas), which only appear in the separate frontmatter triggers field. Fits anchor 3 ('some relevant keywords but missing common variations or synonyms') rather than 4, since several natural trigger phrases are absent from the description itself.

3 / 5

Distinctiveness Conflict Risk

The description is scoped to a specific product (Notion) via a named custom MCP (notion-automation-suite), giving it a clear niche with overlap risk only against other Notion skills — matching anchor 4 ('mostly distinct; minor overlap risk with closely related skills'). It is not anchor 5 because the description adds no distinguishing capability detail beyond the product name.

4 / 5

Total

11

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (710 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/integration/notion/SKILL.md

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.