CtrlK
BlogDocsLog inGet started
Tessl Logo

meeting-notes

Meeting notes page — title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer. Use when the brief mentions "meeting notes", "minutes", "1:1 notes", "all-hands recap", or "会议纪要".

74

Quality

93%

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 concise, well-structured single-screen skill with clear sequencing and a clean output contract. The main gap is the absence of an explicit verification checkpoint and a starter template, leaving actionability and workflow_clarity just shy of full marks.

Suggestions

Add a brief validation step in the workflow (e.g. confirm the artifact renders all required sections before returning) to raise workflow_clarity.

Include a minimal starter HTML skeleton or concrete element markup in the output contract so the guidance is copy-paste ready.

Clarify how DESIGN.md maps to the 'subdued colour palette' step so the palette choice is concrete rather than implied.

DimensionReasoningScore

Conciseness

The ~20-line body is lean and assumes Claude's competence: a brief workflow, layout spec, and output contract with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

Provides concrete structural layout guidance and an explicit output-contract artifact block, but stops short of a copy-paste starter HTML template; the layout spec is actionable yet not fully executable.

4 / 5

Workflow Clarity

A clear numbered sequence (Read DESIGN.md → layout steps → palette) for a generative single-screen task, but no explicit validation/checkpoint for the produced artifact.

4 / 5

Progressive Disclosure

A well-organized, single-screen skill under 50 lines with a clearly signaled one-level reference (DESIGN.md); per the simple-skill guideline this is appropriately structured.

5 / 5

Total

18

/

20

Passed

Description

100%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 tight, specific description that names concrete page components and pairs them with a comprehensive, natural-language trigger list. It cleanly answers both what the skill produces and when to invoke it.

DimensionReasoningScore

Specificity

Lists multiple concrete structural components — 'title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a "next meeting" footer' — giving comprehensive coverage of what the page produces.

5 / 5

Completeness

Explicitly answers both 'what' (the named page components) and 'when' via a 'Use when the brief mentions...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Comprehensive natural trigger terms including synonyms and a non-English variant: 'meeting notes', 'minutes', '1:1 notes', 'all-hands recap', and '会议纪要'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — a single-screen meeting notes page — with distinct triggers unlikely to fire for unrelated artifact skills.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
nexu-io/open-design
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.