presentation-hook
Creates engaging opening statements and powerful closings for medical.
31
Quality
14%
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/presentation-hook/SKILL.mdQuality
Discovery
17%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 incomplete and vague - it appears truncated ('medical.' ends abruptly) and fails to specify what type of medical content (presentations, papers, reports, patient communications). It lacks any trigger guidance for when Claude should select this skill, and provides minimal keywords for matching user requests.
Suggestions
Complete the truncated description and specify the medical content types (e.g., 'medical presentations', 'clinical reports', 'patient education materials')
Add a 'Use when...' clause with explicit triggers like 'Use when creating medical presentations, writing healthcare introductions, or drafting clinical document openings'
Include natural keyword variations users might say: 'introduction', 'conclusion', 'healthcare', 'clinical writing', 'medical presentation', 'patient communication'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (medical) and some actions ('opening statements' and 'closings'), but lacks comprehensive detail about what specific types of medical content, formats, or concrete deliverables are produced. | 2 / 3 |
Completeness | Only partially answers 'what' (creates openings/closings for medical) and completely missing 'when' - no 'Use when...' clause or explicit trigger guidance exists. | 1 / 3 |
Trigger Term Quality | Very few natural keywords - 'opening statements', 'closings', and 'medical' are present but missing common variations users might say like 'introduction', 'conclusion', 'healthcare', 'clinical', or specific document types. | 1 / 3 |
Distinctiveness Conflict Risk | Somewhat specific to medical content writing, but 'opening statements' and 'closings' could overlap with legal skills, presentation skills, or general writing skills. The truncated 'medical.' suggests incomplete specification. | 2 / 3 |
Total | 6 / 12 Passed |
Implementation
12%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is almost entirely generic boilerplate with minimal content specific to creating presentation hooks and closings. The actual useful information (features, input parameters, output format) comprises perhaps 10% of the document and is buried under repetitive scaffolding. The skill fails to provide any concrete examples, templates, or actionable guidance for the creative task it claims to support.
Suggestions
Remove all generic boilerplate and focus on the actual skill: provide 2-3 concrete examples of effective opening hooks and closing statements for medical presentations
Add actionable templates or patterns for different hook types (statistics, questions, stories, quotes) with medical-specific examples
Either provide the actual implementation of scripts/main.py or remove all references to it - currently it's referenced but never shown
Consolidate the scattered feature/parameter information into a single clear section at the top, removing the circular 'See above' references
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose with excessive boilerplate, redundant sections (multiple 'See above' references that point nowhere useful), and template-like content that doesn't add value. The actual skill purpose (creating presentation hooks) is buried under generic scaffolding. | 1 / 3 |
Actionability | Despite referencing `scripts/main.py` repeatedly, no actual implementation or concrete examples of hooks/closings are provided. The skill describes what it does abstractly but never shows how to actually craft an opening or closing statement. | 1 / 3 |
Workflow Clarity | There is a numbered workflow section with steps, but it's generic boilerplate applicable to any skill. No specific guidance on the actual creative process of crafting hooks or closings, and validation steps are vague ('review the generated output'). | 2 / 3 |
Progressive Disclosure | Contains circular references ('See ## Features above', 'See ## Prerequisites above') that don't provide useful navigation. The document is a monolithic wall of boilerplate with poor organization - the actual features list is buried near the bottom. | 1 / 3 |
Total | 5 / 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.