meeting-notes

Turn raw notes or a transcript into a clean summary with decisions and action items.

Quality

73%

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 ./apps/desktop/electron/default-skills/meeting-notes/SKILL.md

Quality

Content

85%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 a well-structured, lean instruction-only skill with a concrete sequenced workflow and an explicit re-check validation step. The only gap is the absence of a worked example or output template, which keeps actionability and conciseness at 4 rather than 5.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence with tight principles ("Signal over transcript", "Never invent"), but the opening paragraph's rhetorical framing ("The value isn't a transcript; it's the decisions...") and lines like "An action with no owner is a wish" are minor instances that could be trimmed, placing it at anchor 4 rather than 5.	4 / 5
Actionability	The "How to work" section gives a concrete 4-step process and the output format specifies exact sections (Summary, Decisions, Action items, Open questions), but there is no worked example or template showing a sample recap, leaving it at anchor 4 rather than fully executable anchor 5.	4 / 5
Workflow Clarity	The workflow is a clear 4-step sequence with an explicit validation checkpoint (step 4: "Re-check every owner, date, and decision against the source; flag anything you had to infer"); as a simple, non-destructive summarization skill, the simple-skill exception applies and feedback loops are not applicable, so anchor 5 fits.	5 / 5
Progressive Disclosure	The skill is under 50 lines with no bundle files and no need for external references, yet is organized into clear sections (When to use, What a good recap captures, Principles, How to work, Output format), satisfying the under-50-lines exception for anchor 5.	5 / 5
	Total	18 / 20 Passed

Description

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

The description states clearly what the skill does and uses natural trigger terms, but omits any explicit "Use when..." guidance, capping completeness and slightly weakening distinctiveness. Adding a trigger clause and a few synonyms would lift the weaker dimensions.

Suggestions

Add an explicit "Use when..." clause (e.g., "Use when turning meeting notes, a transcript, or a recording summary into a recap of decisions and action items.") to answer the "when" and raise completeness above 3.

Include natural synonyms such as "meeting minutes" and "recap" to broaden trigger-term coverage toward anchor 5.

Frame the distinct outputs (decisions, action items, open questions) as separate concrete actions to increase specificity beyond a single transformation.

Dimension	Reasoning	Score
Specificity	Names the domain ("raw notes or a transcript") and one concrete transformation ("Turn ... into a clean summary with decisions and action items"), but lists only a single action rather than several specific ones, matching anchor 3.	3 / 5
Completeness	The "what" is clear (produce a summary with decisions and action items) but there is no "Use when..." clause or equivalent trigger guidance, so completeness is capped at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Includes natural terms a user would say — "raw notes", "transcript", "summary", "decisions", "action items" — giving good keyword coverage, though synonyms like "meeting minutes" or "recap" are missing, so it falls at anchor 4 rather than 5.	4 / 5
Distinctiveness Conflict Risk	The meeting-recap framing (notes/transcript into decisions and action items) carves a recognizable niche with only minor overlap risk against a generic summarizer, matching anchor 4; not 5 because the generic word "summary" and absence of an explicit trigger clause leave some ambiguity.	4 / 5
	Total	14 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: holaboss-ai/holaOS
Path: apps/desktop/electron/default-skills/meeting-notes/SKILL.md
Commit: 4684714

Reviewed: 4 days 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.