CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

hypogenic

Automated LLM-driven hypothesis generation and testing for tabular datasets; use when you need systematic exploration of empirical patterns (e.g., fraud detection, content analysis) and want to combine literature insights with data-driven hypothesis evaluation.

Quality

73%

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/hypogenic/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 delivers genuinely useful, library-specific guidance with executable CLI and Python examples organized in a clear numbered workflow. It loses points for redundancy (Key Features duplicating Implementation Details), missing validation checkpoints in a batch-LLM workflow, and failing to link the bundled references/config_template.yaml while inlining a competing config example.

Suggestions

Reference the bundled template (e.g., 'See [references/config_template.yaml](references/config_template.yaml) for the complete configuration including model, caching, and evaluation settings') and trim the inline config.yaml to the minimal working example, removing the duplication.

Merge 'Key Features' into 'Implementation Details' (or vice versa) — the HypoGeniC/HypoRefine/Union descriptions currently appear twice.

Add validation checkpoints between steps, e.g., verify hypotheses.json exists and spot-check extracted labels against the dataset's label values before running full inference.

DimensionReasoningScore

Conciseness

The technical content (config schema, CLI commands, Python API) is library-specific knowledge Claude does not already have, but there is real redundancy: the 'Key Features' bullets (HypoGeniC, HypoRefine, Union) duplicate the 'Implementation Details' methods section, 'When to Use' reiterates the description, and a ~30-line inline config.yaml overlaps with the bundled references/config_template.yaml. This fits anchor 3 — mostly efficient but could be tightened — better than anchor 4, where only minor trimming would be needed.

3 / 5

Actionability

Concrete, mostly executable guidance throughout: exact file paths, a JSON schema example, a full config.yaml, CLI commands with flags ('hypogenic_generation --config ... --method hypogenic --num_hypotheses 20'), and a copy-paste Python API example including a working extract_label implementation. Not anchor 5 because only the 'hypogenic' method is demonstrated — HypoRefine and Union are described but have no invocation examples — and no sample output or result interpretation is shown; not anchor 3 because the provided code is real and complete, not pseudocode.

4 / 5

Workflow Clarity

The workflow has a clear numbered sequence ('1) Prepare a dataset', '2) Create config.yaml', '3) Run generation + inference', '4) Python API') with concrete commands per step. However, there are no validation checkpoints — nothing verifying hypotheses.json was produced correctly before inference, and the label-matching caveat ('must exactly match the dataset's label values') is stated as a warning rather than a verify step. Since this workflow involves batch LLM operations over datasets with no validation steps, the guideline caps workflow clarity at 3.

3 / 5

Progressive Disclosure

The body is well-sectioned with clear headers, but the one bundle file (references/config_template.yaml) is never referenced — the body inlines its own ~30-line partial config instead of pointing to the fuller template — so references are present but not signaled and content that belongs in the reference file is inline. This matches anchor 3; not anchor 2 because internal structure and sectioning are good and nothing is deeply nested.

3 / 5

Total

13

/

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 with an explicit 'what' and 'use when' clause, concrete trigger phrases, and good keyword coverage. Main weaknesses are the second-person phrasing ('use when you need'), which triggers the voice penalty, and action coverage that stops short of the full capability set (union/merge, hypothesis bank evaluation).

Suggestions

Rewrite the trigger clause in third person, e.g., 'use when the user needs systematic exploration of empirical patterns' — the second-person 'use when you need' costs a specificity point under the voice guideline.

Add one or two more concrete actions to round out coverage, e.g., 'merges and deduplicates literature-derived and data-derived hypothesis banks (Union workflows)'.

Include dataset file formats users would mention (e.g., JSON/CSV tabular datasets) as natural trigger terms.

DimensionReasoningScore

Specificity

The description names concrete actions — 'hypothesis generation and testing' and 'combine literature insights with data-driven hypothesis evaluation' — plus a clear domain ('tabular datasets', 'empirical patterns'), which would fit anchor 4 (several specific actions, minor gaps such as merging/deduplicating hypothesis banks). However, the trigger clause uses second person voice ('use when you need systematic exploration'), which the judging guidelines penalize by reducing specificity by 1, bringing it to anchor 3.

3 / 5

Completeness

It explicitly answers both: what ('Automated LLM-driven hypothesis generation and testing for tabular datasets') and when ('use when you need systematic exploration of empirical patterns (e.g., fraud detection, content analysis) and want to combine literature insights with data-driven hypothesis evaluation'), matching the anchor-5 example pattern of a clear what followed by concrete 'use when' trigger phrases.

5 / 5

Trigger Term Quality

Good natural keyword coverage: 'hypothesis generation', 'hypothesis testing', 'tabular datasets', 'empirical patterns', 'literature insights', and example domains ('fraud detection', 'content analysis') that users would plausibly say. Not anchor 5 because synonyms (e.g., 'hypothesis discovery', 'generate hypotheses from data') and dataset file formats (JSON, CSV) are missing; not anchor 3 because coverage clearly exceeds a single generic keyword.

4 / 5

Distinctiveness Conflict Risk

The LLM-driven hypothesis-generation niche is fairly distinct with specific triggers, fitting anchor 4 (mostly distinct, minor overlap risk). Not 5 because 'systematic exploration of empirical patterns' and the 'fraud detection' example could overlap with general EDA/data-analysis or fraud-specific skills; not 3 because 'LLM-driven hypothesis generation and testing' is a clearly specific, non-generic capability.

4 / 5

Total

16

/

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/Protocol Design/hypogenic/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.