meeting-notes

Paste raw meeting notes and get a clean summary with key decisions and action items.

Quality

82%

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

92%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, actionable, and presents an unambiguous single-step workflow; its main gap is that the provided bundle files are not referenced or explained in the body, so the file structure is not clearly signaled.

Suggestions

Add a brief note explaining that run_js renders scripts/index.html (which loads assets/webview.html) so the bundle relationship is discoverable.

Optionally link the bundle files inline (e.g., 'See scripts/index.html for the renderer entry point') so the structure is clearly signaled.

Dimension	Reasoning	Score
Conciseness	The body is lean, adds no basic-concept explanations, assumes Claude's competence, and every section (brief intro, examples, field spec) earns its place.	3 / 3
Actionability	'You MUST use the run_js tool with the following exact parameters' followed by a precise per-field spec (names, types, 'or empty string' guidance) gives concrete, specific, copy-paste-ready guidance.	3 / 3
Workflow Clarity	This is a simple single-task skill with one unambiguous action (invoke run_js with the data JSON), satisfying the rubric's simple-skill allowance for a top score.	3 / 3
Progressive Disclosure	Sections are well-organized, but the provided bundle files (scripts/index.html and assets/webview.html) are not referenced or navigated from the body, leaving the rendering mechanism undiscoverable; per the bundle-structure guideline this caps the score.	2 / 3
	Total	11 / 12 Passed

Description

72%Weight 40%Scale 1-3

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 is concrete and uses natural trigger terms within a distinct niche, but it is written in second person and omits an explicit 'Use when' trigger clause, which together cap specificity and completeness.

Suggestions

Rewrite in third person (e.g., 'Processes raw meeting notes into a clean summary with key decisions and action items.') to avoid the voice penalty and lift specificity.

Add an explicit trigger clause such as 'Use when the user pastes meeting notes or asks to summarize a meeting and extract action items.' to reach full completeness.

Dimension	Reasoning	Score
Specificity	The phrase 'get a clean summary with key decisions and action items' names the domain and several concrete outputs, but the second-person voice ('Paste...get') triggers the rubric's 1-point specificity penalty, dropping it from 3 to 2.	2 / 3
Completeness	It clearly states what the skill does but lacks any 'Use when...' or equivalent explicit trigger clause, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	'meeting notes', 'summary', 'key decisions', and 'action items' are natural terms a user would actually say when needing this skill, giving good coverage.	3 / 3
Distinctiveness Conflict Risk	'meeting notes' is a clear, distinct niche with specific triggers that is unlikely to conflict with other skills.	3 / 3
	Total	10 / 12 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: mergisi/awesome-openclaw-agents
Path: skills/gemma/meeting-notes/SKILL.md
Commit: 05820c5

Reviewed: 8 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.