meeting-minutes
Use meeting minutes for other workflows that need structured execution, explicit assumptions, and clear output boundaries.
33
Quality
17%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./scientific-skills/Academic Writing/meeting-minutes/SKILL.mdQuality
Discovery
0%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 description is extremely weak across all dimensions. It fails to explain what the skill actually does, uses abstract jargon instead of natural language, and provides no guidance on when to use it. The phrase 'other workflows' suggests this is a catch-all description that would cause significant selection conflicts.
Suggestions
Replace vague language with specific actions (e.g., 'Converts meeting minutes into action items, project tasks, or follow-up emails')
Add an explicit 'Use when...' clause with natural trigger terms users would say (e.g., 'Use when the user wants to process meeting notes, create action items from meetings, or generate follow-ups')
Define the specific output types and use cases instead of 'other workflows' to create a distinct niche (e.g., 'task lists, project updates, stakeholder summaries')
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague language like 'other workflows' and 'structured execution' without naming any concrete actions. There are no specific capabilities listed - just abstract concepts. | 1 / 3 |
Completeness | The 'what' is extremely vague (use meeting minutes for workflows) and there is no explicit 'when' clause or trigger guidance. It's unclear what this skill actually does or when Claude should select it. | 1 / 3 |
Trigger Term Quality | The only natural keyword is 'meeting minutes' but the rest is technical jargon ('structured execution', 'explicit assumptions', 'output boundaries') that users would not naturally say when seeking this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'other workflows' is maximally generic and could conflict with virtually any skill. There's no clear niche or distinct trigger that would help Claude choose this over other skills. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill suffers from severe template bloat - it's filled with generic boilerplate sections (Security Checklist, Risk Assessment, Lifecycle Status, Evaluation Criteria) that add no meeting-minutes-specific value. The actual core functionality of transforming medical meeting transcripts into structured minutes is barely addressed, with no concrete examples of input transcripts or expected output minutes. The skill prioritizes process documentation over actionable guidance.
Suggestions
Remove generic boilerplate sections (Security Checklist, Risk Assessment, Lifecycle Status, Evaluation Criteria) that don't provide meeting-minutes-specific guidance - these waste tokens on content Claude doesn't need.
Add a concrete example showing an input transcript snippet and the expected structured output minutes, demonstrating the actual transformation logic.
Include specific guidance for medical/clinical meeting terminology, FDA/ICH E6 compliance requirements mentioned in Features, and how to identify action items vs decisions in medical contexts.
Consolidate the redundant workflow descriptions (Example Usage, Implementation Details, Workflow sections all describe similar steps) into a single, clear sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with excessive boilerplate, redundant sections (e.g., 'See ## Features above' references that add nothing), and template-like content that doesn't provide meeting-minutes-specific value. The skill explains generic workflow concepts Claude already knows. | 1 / 3 |
Actionability | Provides some concrete elements like the output JSON schema, input parameters table, and bash commands, but the actual meeting minutes processing logic is absent. The main.py script is referenced but no actual implementation or transformation logic is shown. | 2 / 3 |
Workflow Clarity | Steps are listed in the Workflow section but lack specificity for meeting minutes processing. No validation checkpoints for the actual transcript-to-minutes transformation, and the workflow is generic rather than tailored to the medical meeting context mentioned. | 2 / 3 |
Progressive Disclosure | References to 'references/' directory and scripts exist, but the skill itself is a monolithic wall of boilerplate. Content that should be in separate files (security checklist, evaluation criteria, lifecycle status) clutters the main skill file instead of being appropriately split. | 2 / 3 |
Total | 7 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- aipoch/medical-research-skills
- Commit
4a48721
- 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.