notion-knowledge-management

Creates Notion pages and databases, applies templates for research docs, ADRs, and specs, and manages team knowledge bases. Use when creating Notion pages, structuring databases, documenting decisions, or capturing research findings.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%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.

An exemplary lean skill body: it packs genuinely non-obvious gotchas, executable JSON examples, and precise per-document-type conventions into ~34 lines with no filler. The gaps are the absence of a complete create_page payload and the workflow being implied through gotchas rather than laid out as a sequence.

Suggestions

Add a minimal end-to-end create_page example (parent from search + rich-text title properties) so the most common operation is copy-paste ready.

Promote the create-then-verify flow (search parent → create → retry search after ~30s → confirm parent) into a short numbered workflow so the checkpoints are sequenced explicitly.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding: it skips anything Claude already knows and spends every line on non-obvious operational knowledge ("Notion's index lags writes... ~30s", titles are a "rich-text array, not a string"), matching the 'every token earns its place' anchor.	5 / 5
Actionability	Tool names, a complete query_database JSON payload, an exact title-properties snippet, and concrete verification steps ("searching its exact title and confirming parent matches") are present, but the most common operation — create_page — has no full example payload, matching 4 (mostly executable, minor gaps) rather than 5 (copy-paste ready for common cases).	4 / 5
Workflow Clarity	Validation checkpoints and feedback loops are explicit (search for the parent before creating, verify the created page by title and parent, retry on the ~30s index lag, ask the user to share rather than duplicate), but the sequence is distributed across gotcha bullets rather than presented as an ordered workflow, fitting 4 (clear sequence with most checkpoints, minor gaps) rather than 5.	4 / 5
Progressive Disclosure	There are no bundle files (references/, scripts/, assets/ are absent) and the body is well under 50 lines with no content that needs external references; sections (MCP info, Gotchas, Document conventions) are well-organized, which scores 5 under the rubric's simple-skill guideline.	5 / 5
	Total	18 / 20 Passed

Description

88%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.

A strong description: third-person voice, concrete multi-action capability statement, and an explicit Use-when trigger clause. Its only weaknesses are missing natural synonyms (ADR, meeting notes) in the triggers and a couple of Notion-less triggers that slightly raise conflict risk.

Suggestions

Add natural synonyms to the Use-when clause, e.g. "writing ADRs (architecture decision records) or meeting notes", to match terms users actually say and lift trigger coverage to 5.

Scope the broader triggers to Notion (e.g. "documenting decisions in Notion") to reduce overlap with generic documentation skills.

Dimension	Reasoning	Score
Specificity	"Creates Notion pages and databases, applies templates for research docs, ADRs, and specs, and manages team knowledge bases" lists multiple concrete actions (create pages, create databases, apply templates) across named document types, matching the comprehensive-coverage anchor; only "manages team knowledge bases" is mildly generic, which is not enough to fall to 4.	5 / 5
Completeness	It explicitly answers 'what' (creates pages/databases, applies templates, manages knowledge bases) and 'when' via a concrete "Use when..." clause with specific trigger phrases, exactly matching the 5 anchor.	5 / 5
Trigger Term Quality	"Use when creating Notion pages, structuring databases, documenting decisions, or capturing research findings" has good natural phrasing, but misses synonyms the body itself uses (ADR / architecture decision records, meeting notes, specs), so it matches 'good keyword coverage; a few natural terms missing' rather than the comprehensive-synonym 5 anchor.	4 / 5
Distinctiveness Conflict Risk	"Notion" carves a clear niche, but two of the four triggers ("documenting decisions", "capturing research findings") do not mention Notion and could fire for non-Notion documentation contexts, giving minor overlap risk that fits the 4 anchor rather than 5's 'minimal conflict risk'.	4 / 5
	Total	18 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: monkilabs/opencastle
Path: src/orchestrator/plugins/notion/SKILL.md
Commit: c0f4566

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.