notion-knowledge-capture

Capture conversations and decisions into structured Notion pages; use when turning chats/notes into wiki entries, how-tos, decisions, or FAQs with proper linking.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./plugins/notion/skills/notion-knowledge-capture/SKILL.md

Quality

Content

71%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 well-structured, actionable skill body with clear sequencing and strong tool-call guardrails. Its main weakness is progressive disclosure: the body depends on reference/ and examples/ files that are absent from the bundle, breaking the navigation it advertises.

Suggestions

Ship the referenced reference/*-database.md and examples/*.md files (or add a reference/ and examples/ directory), since the body's Step 2 and References sections depend on them but they are missing from the bundle.

Add one concrete example payload for Notion:notion-create-pages (showing the parent, pages array, and a properties object) so the create step is copy-paste ready rather than inferred.

Add an explicit validation checkpoint after page creation/update (e.g., fetch the created page to confirm properties/links resolved) to close the workflow_clarity validation gap for write operations.

Dimension	Reasoning	Score
Conciseness	Lean, assumes Claude's competence (no 'Notion is a...' fluff), and uses dense bullets, but the Quick start and Workflow sections overlap notably in sequencing the same five phases, which is minor redundancy that could be tightened.	4 / 5
Actionability	Names exact tools and parameters (Notion:search, notion-create-pages with parent/pages, notion-update-page with command/old_str/new_str, collection:// data_source_id) — highly actionable for an instruction skill, but lacks concrete example call payloads showing the properties object shape, leaving minor gaps.	4 / 5
Workflow Clarity	Clear numbered sequence (Workflow 0–5) with a tool-unavailability branch and a read-before-write pattern, plus an error-recovery feedback loop in the guardrails; however explicit post-creation/output validation is missing, so it stops at 'most checkpoints present'.	4 / 5
Progressive Disclosure	Sections are well-organized and references are clearly signaled (explicit file list under reference/ and examples/), but those referenced directories and files do not exist in the actual bundle — navigation leads nowhere, and per-database schema guidance the skill leans on is neither inlined nor present as files.	3 / 5
	Total	15 / 20 Passed

Description

87%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: concise, third-person, with an explicit 'use when' trigger and concrete content-type variants. It clearly answers both what and when with natural trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('structured Notion pages') and several concrete actions — capture, structure/convert into wiki entries/how-tos/decisions/FAQs, and linking — but the verbs ('capture', 'turning into') are slightly more abstract than the anchor-5 example's concrete operations, leaving minor coverage gaps.	4 / 5
Completeness	Clearly states what it does ('Capture conversations and decisions into structured Notion pages') and gives an explicit 'use when' clause with concrete trigger phrases (turning chats/notes into wiki entries, how-tos, decisions, or FAQs), matching the anchor-5 example pattern.	5 / 5
Trigger Term Quality	Good natural-term coverage ('conversations', 'chats/notes', 'wiki entries', 'how-tos', 'decisions', 'FAQs', 'linking') with synonyms, but a few common variants a user might say ('knowledge base', 'documentation') are absent; no file extensions apply to this service-based skill.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Notion knowledge capture from conversations) with distinct triggers and minimal conflict risk; the capture-from-chat framing is specific enough to avoid overlapping with generic note or documentation skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	14 / 16 Passed

Repository: openai/plugins
Path: plugins/notion/skills/notion-knowledge-capture/SKILL.md
Commit: 1dc1958

Reviewed: 9 hours 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.