Tessl • The package manager for agent skills

SkillPublic

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 "会议纪要".

Quality

84%

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

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

The body is admirably lean and structurally concrete about the page to produce, but its single external dependency (DESIGN.md) is missing from the bundle, which weakens actionability, the workflow's first step, and disclosure. Adding the referenced design file or inlining the design tokens would resolve most gaps.

Suggestions

Ship DESIGN.md (or the design-system sections declared in frontmatter) in the bundle, or inline the subdued palette/hierarchy specs, so step 1 of the workflow is actually resolvable.

Add a compact example HTML skeleton of the notes page under the Output contract so the layout guidance is verifiable at a glance.

Add a brief fallback or self-check line (e.g., what to do if DESIGN.md is absent, or a final review that all five sections are present).

Dimension	Reasoning	Score
Conciseness	The ~20-line body is lean and efficient: every line is either a layout requirement or the output contract, with no explanation of concepts Claude already knows, matching anchor 5.	5 / 5
Actionability	The layout spec is concrete ("Header: meeting title, date, time, location/Zoom, attendees row", "Agenda checklist (4–6 items)", table with owner/due date/status) and the output contract gives the exact artifact wrapper, but it delegates all styling to "DESIGN.md", which is not present in the bundle, and offers no example HTML — minor gaps keeping it at anchor 4.	4 / 5
Workflow Clarity	The three-step sequence (read DESIGN.md → layout → palette/hierarchy) is clear and unambiguous for a simple generative task, but step 1 points at a file that does not exist in the bundle with no fallback, and there is no verification step for the produced page — minor validation gaps at anchor 4.	4 / 5
Progressive Disclosure	The body has well-organized sections (Workflow, Output contract) and is under 50 lines, but its only external reference — "Read DESIGN.md" — is a broken/dangling pointer: no references/, scripts/, or assets/ directories and no DESIGN.md exist in the bundle, so navigation fails exactly when followed.	3 / 5
	Total	16 / 20 Passed

Description

83%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, concise, concrete about the deliverable, and with an explicit use-when clause covering natural trigger phrases in two languages. The main room for improvement is broader synonym coverage and slightly sharper scoping of the generic term 'minutes'.

Dimension	Reasoning	Score
Specificity	The description lists several concrete components — "title bar with attendees, agenda checklist, decisions block, action items table with owners + dates, and a 'next meeting' footer" — but they all describe one deliverable (rendering a page) rather than multiple distinct actions, matching anchor 4's 'several specific actions; minor gaps'.	4 / 5
Completeness	It explicitly answers both what (a single-screen meeting notes page with the listed components) and when ("Use when the brief mentions 'meeting notes', 'minutes', '1:1 notes', 'all-hands recap', or '会议纪要'"), matching anchor 5's clear what-and-when with concrete trigger phrases.	5 / 5
Trigger Term Quality	"meeting notes", "minutes", "1:1 notes", "all-hands recap", and "会议纪要" are natural phrases a user would say, giving good coverage; a few common variants like "meeting summary" or "notes from the meeting" are missing, so it sits at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	Meeting-notes pages are a clear niche with distinct triggers, but the standalone term "minutes" could fire on duration mentions (e.g., 'a 60-minute meeting'), creating minor overlap risk consistent with anchor 4.	4 / 5
	Total	17 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: design-templates/meeting-notes/SKILL.md
Revision: 78d5637

Reviewed: 17 days ago

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.

meeting-notes

Table of Contents

Is this your skill?