presentation-hook
Creates engaging opening statements and powerful closings for medical.
28
11%
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
9%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—it appears truncated after 'medical'—making it unclear what specific domain or format it targets. It lacks a 'Use when...' clause, natural trigger terms, and sufficient specificity to distinguish it from other skills. The vagueness would make it very difficult for Claude to correctly select this skill from a pool of alternatives.
Suggestions
Complete the truncated sentence and specify the exact medical context (e.g., 'medical presentations', 'medical research papers', 'medical sales pitches').
Add a 'Use when...' clause with explicit trigger terms, e.g., 'Use when the user asks for help with introductions or conclusions for medical presentations, speeches, or proposals.'
Include more natural keywords users might say, such as 'introduction', 'conclusion', 'hook', 'call to action', along with the specific medical document type.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (medical) and two specific actions (opening statements and closings), but lacks detail on what these entail or additional concrete capabilities. | 2 / 3 |
Completeness | The description partially addresses 'what' but is incomplete (the sentence appears truncated after 'medical'), and there is no 'when' clause or explicit trigger guidance at all. | 1 / 3 |
Trigger Term Quality | The description contains very few natural trigger terms. 'Medical' is extremely broad, and 'opening statements' and 'closings' are vague—it's unclear if this refers to medical presentations, papers, speeches, or something else. Users would not naturally use these terms to find this skill. | 1 / 3 |
Distinctiveness Conflict Risk | The description is too vague to be distinctive—'medical' could overlap with many medical-related skills, and 'opening statements and closings' is ambiguous enough to conflict with presentation, writing, or speech skills. | 1 / 3 |
Total | 5 / 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 overwhelmingly generic boilerplate with almost no domain-specific content about crafting medical presentation hooks. The actual task—creating engaging openings and closings—receives virtually no concrete guidance, examples, or techniques. The vast majority of the content is reusable scaffolding (security checklists, risk assessments, lifecycle status) that wastes tokens without teaching Claude anything useful about the skill's stated purpose.
Suggestions
Replace boilerplate sections with concrete examples of medical presentation hooks: show 2-3 input/output pairs demonstrating different audience types (clinicians, patients, researchers) with actual hook text.
Add specific techniques and patterns for medical presentation openings (e.g., startling statistic, patient story, provocative question) with concrete examples rather than just listing 'Storytelling elements' as a feature.
Remove generic sections that don't contribute to the skill's purpose: Risk Assessment, Security Checklist, Lifecycle Status, and Evaluation Criteria are boilerplate that Claude doesn't need.
Eliminate circular references ('See ## Features above') and consolidate the workflow into a single clear sequence specific to hook generation, not generic script execution.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with boilerplate sections (Risk Assessment, Security Checklist, Lifecycle Status, Evaluation Criteria) that add no actionable value for Claude. Multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above'). The actual domain-specific content (how to craft presentation hooks) is buried under generic scaffolding that Claude already knows. | 1 / 3 |
Actionability | Despite being about crafting presentation openings/closings, there are zero concrete examples of actual hooks, no demonstration of input→output transformation, and no specific guidance on what makes a good medical presentation hook. The 'Example Usage' section only shows how to run a Python script, not how to actually create hooks. The output format JSON schema is minimal and unexplained. | 1 / 3 |
Workflow Clarity | There is a numbered workflow with steps for confirming objectives, validating scope, executing, and returning results, plus error handling guidance. However, the workflow is entirely generic and not specific to creating presentation hooks. There are no validation checkpoints specific to the quality of generated hooks, and no feedback loops for iterating on hook quality. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with many sections that could be consolidated or removed. Circular internal references ('See ## Features above') add confusion rather than navigation. The document references `references/` and `scripts/main.py` but provides no clear signaling of what those contain or when to consult them. | 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
0b96148
- 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.