CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

72

Quality

89%

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

SKILL.md
Quality
Evals
Security

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.

A tight, expert-oriented skill body: dense gotchas, executable JSON snippets, validation/retry guidance, and per-document-type checklists. The main gap is the absence of a complete create_page example and a single explicit numbered workflow, which keep actionability and workflow_clarity at 4.

Suggestions

Add a complete create_page JSON example (with parent and title rich-text array) so the create flow is fully copy-paste ready alongside the query_database example.

Consolidate the page-creation procedure into one explicit numbered sequence (search parent → create → verify by re-searching title + confirming parent → retry on index lag) rather than leaving it distributed across gotchas.

Optionally show the append_block_children call shape for ordinary pages to mirror the query_database example and round out coverage.

DimensionReasoningScore

Conciseness

The body is lean and dense with practical gotchas and conventions; it never explains what Notion or an ADR is and assumes Claude's competence, so every token earns its place.

5 / 5

Actionability

Concrete, executable JSON examples (the rich-text title array and the query_database filter/sorts call) plus exact field names give mostly executable guidance, but a full create_page call example is missing — a minor gap.

4 / 5

Workflow Clarity

Explicit checkpoints are present (search for the parent first, then verify the new page by searching its exact title and confirming parent matches; retry on index lag) with a retry feedback loop and per-type section checklists, but the workflow is spread across gotchas rather than one numbered sequence, leaving a minor gap versus a fully sequenced procedure.

4 / 5

Progressive Disclosure

Under 50 lines with no external references needed and clean section organization (Gotchas, Document conventions); per the simple-skill guidance, well-organized sections earn a 5 with no bundle files present.

5 / 5

Total

18

/

20

Passed

Description

92%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, third-person description that pairs concrete capabilities with explicit "Use when" trigger guidance and a clearly distinctive Notion niche. Minor room for synonym/variant coverage in the trigger terms keeps it just shy of perfect on that one dimension.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — "Creates Notion pages and databases, applies templates for research docs, ADRs, and specs, and manages team knowledge bases" — giving comprehensive coverage of the domain rather than generic phrasing.

5 / 5

Completeness

It explicitly answers both what ("Creates Notion pages and databases, applies templates...") and when ("Use when creating Notion pages, structuring databases, documenting decisions, or capturing research findings") with concrete trigger phrases.

5 / 5

Trigger Term Quality

"Use when creating Notion pages, structuring databases, documenting decisions, or capturing research findings" gives good natural-term coverage, but it lacks synonyms and file-extension-style variants, stopping just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

The Notion-specific framing (pages, databases, ADR/spec templates) carves a clear niche with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
monkilabs/opencastle
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.