CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

notion-meeting-intelligence

Prepare meeting materials with Notion context and supplemental research; use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees.

65

Quality

82%

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

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 lean, operationally rich instruction-only skill: exact tool names, parameter shapes, and an explicit tool-unavailability recovery path make it highly actionable. Its main weaknesses are duplicated flow/template listings, absence of any literal example call payloads, and references to bundle files that are not present in the actual bundle.

Suggestions

progressive_disclosure: Ship the referenced `reference/` and `examples/` files in the bundle (or remove the dangling references) so the body's pointers to `reference/template-selection-guide.md`, the seven templates, and `examples/*.md` resolve to real files.

conciseness: Drop either the 'Quick start' or the 'Workflow' section (they repeat the same five steps at two granularities) and list the template names once, cutting the template enumeration duplicated between Workflow step 2 and 'References and examples'.

actionability: Add one or two literal example calls (e.g., a sample `Notion:search` query payload and a minimal `Notion:notion-create-pages` request with `parent` and `pages`) so the guardrails become copy-paste ready.

DimensionReasoningScore

Conciseness

The body is dense and operational (tool-call guardrails, exact tool names, argument shapes) with no re-teaching of concepts Claude already knows, but the 'Quick start' substantially duplicates the 'Workflow' section and the template list appears twice (Workflow step 2 and the References section). Anchor 5 ('every token earns its place') is blocked by this redundancy, while it is clearly above the 'mostly efficient with some unnecessary explanation' midpoint.

4 / 5

Actionability

Guidance is highly concrete — exact tool names (`Notion:search`, `Notion:notion-create-pages`, `Notion:notion-update-page`) and argument shapes (`filters: {}`, `parent` + `pages` array, `content_updates: []`, `collection://...` URLs as table names) — but it contains no literal example calls or payloads (e.g., a sample search query or create-pages request), so it is not fully copy-paste ready per the anchor-5 example.

4 / 5

Workflow Clarity

A clear 0→5 sequence exists with an explicit error-recovery path (tool-unavailable pause-and-ask, and the 'Tool <name> not found → treat as unavailable, do not retry' guardrail), but there is no checkpoint verifying that a created/updated page succeeded or that fetched content was correctly applied — 'most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

References are clearly signaled and one level deep (`reference/template-selection-guide.md`, named templates, `examples/`), but scored against the actual bundle structure: the referenced `reference/` and `examples/` directories do not exist in the bundle (only `assets/` images are present), so the navigation paths dangle and the structure is not verifiable. This sits between anchor 4 (good structure, minor gaps) and anchor 2 (broken/buried references) but is closer to 'could be better organized' with a real defect.

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 in third person with explicit what and when clauses, concrete actions, and a distinctive Notion-meeting-prep niche. It could gain a few natural trigger synonyms ('meeting prep', 'briefing', '1:1', 'retro') and slightly broader action coverage to reach top marks on trigger quality and specificity.

DimensionReasoningScore

Specificity

Quotes several concrete actions — 'Prepare meeting materials with Notion context and supplemental research', 'gathering context, drafting agendas/pre-reads, and tailoring materials to attendees' — but coverage has minor gaps relative to the skill's full surface (creating/updating Notion pages, task follow-ups), matching anchor 4 ('several specific actions; minor gaps') rather than the comprehensive anchor 5.

4 / 5

Completeness

Clearly answers both: what — 'Prepare meeting materials with Notion context and supplemental research' — and when, with an explicit trigger clause — 'use when gathering context, drafting agendas/pre-reads, and tailoring materials to attendees'. This matches the anchor-5 exemplar structure of explicit what + explicit 'use when' with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ('meeting materials', 'agendas', 'pre-reads', 'attendees', 'Notion'), giving good keyword coverage, but common variations users naturally say are missing — 'meeting prep', 'briefing', '1:1', 'retrospective', 'sprint planning' — which the body shows are core use cases. Fits anchor 4, not 5's 'comprehensive coverage including synonyms'.

4 / 5

Distinctiveness Conflict Risk

A clear niche (Notion-backed meeting preparation) with distinct triggers ('Notion context', 'agendas/pre-reads') and minimal conflict risk against generic document or note-taking skills; the 'Notion' qualifier sharply delimits it.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

openai/plugins

Path

plugins/notion/skills/notion-meeting-intelligence/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.