ambaba/meeting-notes
Capture and organize business meeting notes into durable decisions, action items, and takeaways.
98
100%
Does it follow best practices?
Impact
93%
1.20xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong, well-crafted skill description. It concisely states what the skill does with specific outputs (decisions, action items, takeaways), uses third person voice correctly, and includes an explicit 'Use when' clause with natural trigger terms. The description is focused and distinctive enough to avoid conflicts with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'capture and organize business meeting notes into durable decisions, action items, and takeaways.' These are concrete, well-defined outputs. | 3 / 3 |
Completeness | Clearly answers both 'what' (capture and organize business meeting notes into decisions, action items, and takeaways) and 'when' (explicit 'Use when' clause with specific trigger phrases). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would actually say: 'meeting notes', 'taking notes', 'capture notes', 'note-taking mode'. These are common, natural phrases a user would use when requesting this functionality. | 3 / 3 |
Distinctiveness Conflict Risk | The description carves out a clear niche around business meeting notes specifically, with distinct triggers like 'meeting notes' and 'note-taking mode' that are unlikely to conflict with general document or note-taking skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that is concise, actionable, and clearly structured. The workflow has an appropriate confirmation checkpoint before writing, trigger words are explicit, and the capture/skip criteria provide useful decision boundaries. The entry schema format and file path are concrete and copy-paste ready.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what meetings are or how note-taking works. The 'what to capture' and 'what to skip' lists are crisp filters, not verbose descriptions. | 3 / 3 |
Actionability | Provides concrete steps with exact phrases to say, specific trigger words, a precise file path, and an explicit entry schema format. The guidance is specific enough to execute without ambiguity. | 3 / 3 |
Workflow Clarity | Clear 5-step sequence with an explicit confirmation checkpoint (step 4) before the destructive write operation (step 5). Trigger words for transitions ('done', 'end notes', 'that's it') are specified, and the mode entry/exit is unambiguous. | 3 / 3 |
Progressive Disclosure | For a skill under 50 lines with no need for external references, the content is well-organized into logical sections (steps, what to capture, what to skip, rules) that are easy to scan and navigate. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
Reviewed
Table of Contents