presentation-hook
Creates engaging opening statements and powerful closings for medical.
23
4%
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 and appears truncated ('for medical.' ends abruptly), making it unclear what specific domain or document type it targets. It lacks a 'Use when...' clause, natural trigger terms, and sufficient specificity to distinguish it from other writing or medical skills.
Suggestions
Complete the truncated phrase—specify what type of medical content (e.g., 'medical presentations', 'medical research papers', 'medical sales pitches') to clarify the domain.
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user needs help writing introductions or conclusions for medical presentations, speeches, or proposals.'
Include natural trigger terms users would say, such as 'medical presentation intro', 'clinical talk opening', 'healthcare pitch closing', or specific document types.
| 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 only partially addresses 'what' (and even that is unclear due to the truncated sentence 'for medical.'), and completely lacks any 'when' clause or explicit trigger guidance. | 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 countless medical-related skills, and 'opening statements and closings' could conflict with general writing or presentation skills. The truncated phrasing adds further ambiguity. | 1 / 3 |
Total | 5 / 12 Passed |
Implementation
0%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 virtually no task-specific content about crafting medical presentation hooks. The actual domain knowledge—what makes a good opening hook, closing statement, or audience-specific approach for medical presentations—is completely absent. The document is bloated with template sections (risk assessment, security checklist, lifecycle status) that provide no actionable guidance for the stated purpose.
Suggestions
Replace boilerplate sections with concrete examples of medical presentation hooks (e.g., 'For a cardiology audience: [example opening]' → '[example output JSON]') showing actual input/output pairs.
Add specific techniques and patterns for crafting hooks (e.g., statistical shock openers, patient story frameworks, call-to-action closings) with medical domain examples.
Remove generic sections like Risk Assessment, Security Checklist, Lifecycle Status, and Evaluation Criteria that add no task-specific value and consume token budget.
Consolidate the redundant workflow/implementation/example usage sections into a single clear workflow with domain-specific steps like 'identify audience expertise level → select hook type → apply storytelling framework → generate alternatives'.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely verbose and padded with boilerplate sections that add no value. Sections like 'Risk Assessment', 'Security Checklist', 'Lifecycle Status', 'Evaluation Criteria' are generic filler. Multiple sections reference each other circularly ('See ## Features above', 'See ## Prerequisites above'). The actual task-specific content (creating presentation hooks) is buried under massive amounts of template boilerplate that Claude already knows. | 1 / 3 |
Actionability | Despite the length, there is no concrete guidance on how to actually craft presentation hooks. The skill describes running a script (`scripts/main.py`) but provides no example of what a good hook looks like, no prompt patterns, no concrete examples of input/output pairs for medical presentation openings or closings. The 'Example Usage' just shows how to run a Python script, not how to create hooks. | 1 / 3 |
Workflow Clarity | The workflow section is entirely generic ('Confirm the user objective', 'Validate that the request matches the documented scope') with no task-specific steps for crafting presentation hooks. There are no validation checkpoints specific to the domain. The 'Example run plan' is also generic boilerplate about running scripts rather than a meaningful workflow for the stated purpose. | 1 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with many sections that are redundant or circular. References like 'See ## Features above' and 'See ## Prerequisites above' point to sections within the same document that appear later, creating confusing navigation. The document has no meaningful hierarchy—everything is dumped at the same level with no clear separation between essential and supplementary content. | 1 / 3 |
Total | 4 / 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
8277276
- 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.