CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hypothesis-generation

Structured scientific hypothesis formulation from observations; use when you have experimental observations or preliminary data and need testable hypotheses with predictions, mechanisms, and validation experiments.

Quality

65%

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/Protocol Design/hypothesis-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

38%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 core skill content (sections 1-5) is genuinely good — a concrete 8-step scientific workflow with executable LaTeX/bash examples and thoughtful formatting constraints — but it is buried in a large auto-generated boilerplate wrapper with duplicated sections, contradictory statements about packaged scripts, and references to bundle files (references/, assets/, scripts/) that are entirely absent from the package. As shipped, the skill's detailed guidance cannot actually be followed end-to-end.

Suggestions

Remove the auto-generated boilerplate wrapper (the first 'When to Use'/'Key Features'/'Dependencies'/'Example Usage'/'Implementation Details' block plus 'Required Inputs', 'Recommended Workflow', 'Output Contract', 'Validation and Safety Rules', 'Failure Handling', and the empty 'Quick Validation' no-op) so only the real sections 1-5 remain.

Ship the referenced bundle files (references/hypothesis_quality_criteria.md, references/experimental_design_patterns.md, references/literature_search_strategies.md, assets/hypothesis_report_template.tex, assets/hypothesis_generation.sty, assets/FORMATTING_GUIDE.md, scripts/generate_schematic.py) or rewrite the body to not depend on them, and resolve the 'No packaged executable script was detected' contradiction with the generate_schematic.py example.

Replace the generic 'Run a final validation pass' language with explicit checkpoints tied to this skill, e.g., verify the compiled PDF is ≤ 4 pages, each hypothesis box fits one page, and the 1-2 required schematics are present before returning the report.

DimensionReasoningScore

Conciseness

Roughly half the body is padded boilerplate that adds nothing Claude does not already know: 'Use this skill when the request matches its documented task boundary', 'Execution model: validate the request, choose the packaged workflow, and produce a bounded deliverable', and a code block containing only 'No local script validation step is required for this skill.' Whole sections (When to Use, Key Features, Dependencies, Example Usage, Implementation Details) are duplicated verbatim in intent, matching 'noticeably verbose; several unnecessary explanations or padded sections' rather than the mostly-efficient level-3 anchor.

2 / 5

Actionability

The real content (sections 1-5) does provide concrete bash commands and a copy-paste-ready LaTeX skeleton, but the commands reference files that do not exist in the bundle (`scripts/generate_schematic.py`, `assets/hypothesis_report_template.tex`, `assets/hypothesis_generation.sty`), and the body itself states 'No packaged executable script was detected', contradicting the example. Guidance is present but incomplete/broken as shipped, fitting 'some concrete guidance but incomplete... missing key details' rather than 'mostly executable... minor gaps'.

3 / 5

Workflow Clarity

Section 5.1 gives a clear 8-step sequence and the LaTeX compile path is explicit (xelatex → bibtex → xelatex ×2), but validation checkpoints are only implicit or generic ('Run a final validation pass', 'Keep the output safe and reproducible'), the 'Quick Validation' section is a no-op, and a second contradictory generic 'Recommended Workflow' competes with the real one. This fits 'steps listed but validation gaps; checkpoints missing or implicit' rather than the level-4 anchor.

3 / 5

Progressive Disclosure

The body promises well-signaled one-level-deep references (`references/hypothesis_quality_criteria.md`, `references/experimental_design_patterns.md`, `references/literature_search_strategies.md`, three `assets/` files, `scripts/generate_schematic.py`), but none of these files exist in the bundle — every reference is dangling — and the generic wrapper content is inlined instead of being split out. This matches 'minimal structure; content that clearly belongs in separate files is inlined; or references are buried' rather than the level-3 anchor, where referenced material would at least be present.

2 / 5

Total

10

/

20

Passed

Description

78%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.

A strong description that clearly and concisely states both the capability and explicit 'use when' triggers with natural keywords. Its main limitation is that it describes a single formulation action with enumerated outputs rather than the skill's fuller range of actions (literature search, experiment design, LaTeX report generation).

DimensionReasoningScore

Specificity

The description names one concrete action ('Structured scientific hypothesis formulation from observations') and enumerates the deliverables ('testable hypotheses with predictions, mechanisms, and validation experiments'), but unlike the level-4/5 anchors it does not list several distinct actions (e.g., literature search, experiment design, report generation), so it matches 'names domain and 1-2 concrete actions'.

3 / 5

Completeness

It explicitly answers both questions: what ('Structured scientific hypothesis formulation from observations... testable hypotheses with predictions, mechanisms, and validation experiments') and when ('use when you have experimental observations or preliminary data and need testable hypotheses...'), with concrete trigger phrases, matching the level-5 anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say are present: 'experimental observations', 'preliminary data', 'testable hypotheses', 'predictions', 'validation experiments'. A few natural variants are missing (e.g., 'generate hypotheses', 'research question', 'experiment design'), fitting the 'good keyword coverage; a few natural terms missing' anchor rather than the comprehensive level-5 one.

4 / 5

Distinctiveness Conflict Risk

The scientific-hypothesis niche with triggers like 'experimental observations' and 'testable hypotheses' is mostly distinct, but it could overlap with closely related experiment-design or literature-review skills, fitting 'mostly distinct; minor overlap risk' rather than the clear-niche level-5 anchor.

4 / 5

Total

16

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

referenced_paths_exist

Referenced path issues: 24 missing

Warning

Total

14

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Protocol Design/hypothesis-generation/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.