CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

presentation-hook

Creates engaging opening statements and powerful closings for medical.

Quality

56%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Academic Writing/presentation-hook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

42%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is dominated by generic governance boilerplate that adds no task-specific knowledge, while the genuinely useful sections (Input Parameters, Output Format, Workflow) are undermined by mismatches with the packaged script and a references file with no real content. Documentation of script invocation is incorrect (--help is not supported), which undermines both actionability and trust in the workflow.

Suggestions

Remove or drastically compress the boilerplate sections (Risk Assessment, Security Checklist, Evaluation Criteria, Lifecycle Status, Output Requirements, Response Template) and the circular 'See ## X above' filler; keep only sections that carry task-specific guidance.

Fix the script documentation: either add argparse to scripts/main.py so `--help` and the documented topic/audience/type parameters actually work, or correct the Example Usage to match the script's real behavior.

Replace or expand references/guidelines.md (currently an empty stub) with real hook-crafting guidance (storytelling patterns, audience adaptation, medical-context framing) and link to it explicitly by name from the body.

DimensionReasoningScore

Conciseness

The body is heavily padded with generic template sections ("Risk Assessment", "Security Checklist", "Evaluation Criteria", "Lifecycle Status", "Response Template") and circular filler like "See `## Features` above for related details" and "See `## Prerequisites` above for related details", matching 'Noticeably verbose; several unnecessary explanations or padded sections'. It is not a 3 because the padding is extensive rather than occasional; not a 1 because sections like Input Parameters and Output Format carry real, task-specific content.

2 / 5

Actionability

Concrete commands exist ("python -m py_compile scripts/main.py", "python scripts/main.py") and there is an Input Parameters table and Output Format spec, but the documented usage does not match the actual script: "python scripts/main.py --help" fails because main() accepts no arguments, and the parameters (topic, audience, type) are never wired to a CLI. This fits 'Some concrete guidance but incomplete... missing key details'.

3 / 5

Workflow Clarity

The Workflow section lists a sequenced 5-step process with a Quick Check (py_compile) and a fallback path ("If execution fails or inputs are incomplete, switch to the fallback path"), but checkpoints are generic confirm-the-inputs boilerplate rather than concrete output validation, fitting 'Steps listed but validation gaps; sequence present but checkpoints missing or implicit'. Not a 4 because no step validates the actual generated hook output.

3 / 5

Progressive Disclosure

The bundle provides references/guidelines.md and scripts/main.py, and the body is well sectioned, but references are never named or linked — the body only says "Reference guidance: `references/` contains supporting rules, prompts, or checklists" — and the actual guidelines.md is a content-free stub of bullet headings. This fits 'Some structure but could be better organized; references present but not clearly signaled'.

3 / 5

Total

11

/

20

Passed

Description

50%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description communicates a clear core capability but reads as a truncated, template-generated sentence ('for medical' is grammatically incomplete). It lacks any 'Use when...' trigger guidance and the natural vocabulary users would employ (presentation, speech, hook), leaving it mediocre across all dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when preparing medical presentations, speeches, or talks and the user needs a strong opening or closing line.'

Include natural trigger terms and synonyms users would actually say: 'presentation', 'speech', 'talk', 'hook', 'audience engagement', 'medical conference'.

Fix the truncated phrase 'for medical' to a concrete domain like 'for medical and healthcare presentations' and enumerate what is produced (e.g., hooks plus alternative variants).

DimensionReasoningScore

Specificity

"Creates engaging opening statements and powerful closings for medical" names the domain and 1-2 concrete actions (creating openings, creating closings) but coverage is not comprehensive, matching the 'Names domain and 1-2 concrete actions' anchor. It is not a 4 because it does not list several specific actions, and not a 2 because the actions given are concrete rather than generic.

3 / 5

Completeness

The description has a clear 'what' (creates opening statements and closings) but no 'Use when...' clause or equivalent trigger guidance, so completeness is capped at 3 per the judging guidelines. It is not a 2 because the 'what' is clearly stated, not vague.

3 / 5

Trigger Term Quality

Terms like "opening statements", "closings", and "medical" are relevant, but the most natural user phrasings ("presentation", "speech", "talk", "hook") are missing, fitting 'Some relevant keywords but missing common variations or synonyms'. A 4 would require broader natural-term coverage.

3 / 5

Distinctiveness Conflict Risk

"for medical" provides a partial niche, but the truncated domain qualifier and absence of explicit triggers mean it could still overlap with general presentation-writing or speech-craft skills, matching 'Somewhat specific but could still overlap with similar skills'. A 4 would require a clearer niche boundary.

3 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Academic Writing/presentation-hook/SKILL.md

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.