CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bio-causal-genomics-pleiotropy-detection

Detect and correct for horizontal pleiotropy in Mendelian randomization analyses using MR-PRESSO for outlier removal, MR-Egger regression for directional pleiotropy, and Steiger filtering for variant directionality. Use when validating MR results, detecting pleiotropic instrum...

Quality

79%

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/Data Analysis/bio-causal-genomics-pleiotropy-detection/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, highly actionable skill body: method-by-method executable R code with interpretation thresholds and a consolidated sensitivity framework. Its weaknesses are the absence of any progressive disclosure (everything is inlined in one long SKILL.md with no reference files) and a few small correctness/organization blemishes such as the contamination-mixture/MR-RAPS label mix-up and the vignette-deferred multivariable section.

Suggestions

Split the long tail into one-level-deep reference files (e.g. references/sensitivity-framework.md for the run_sensitivity/summarize functions, references/strobe-mr-reporting.md for the checklist) so SKILL.md stays a lean overview.

Fix the mislabeled block in Additional Sensitivity Methods: the '# Contamination mixture' comment is followed by mr_raps code; either show the actual contamination-mixture call or correct the label.

Add a short decision guide for combining the tests (e.g. if Egger intercept is significant but PRESSO global is not, prefer Egger-adjusted estimates; if distortion test is significant, report corrected IVW) to make the workflow across methods explicit.

DimensionReasoningScore

Conciseness

The body is dominated by executable R code with terse, decision-relevant comments; the pleiotropy-type taxonomy is domain knowledge that maps directly to the tests rather than padding. Minor trimmables (repeated MR-PRESSO setup in the framework function, the boilerplate Version Compatibility block) fit the 4 anchor; not 5 due to that redundancy, not 3 since no section extensively re-teaches known concepts.

4 / 5

Actionability

Each method ships concrete, near copy-paste R code with named functions, parameters, and exact result-field access (e.g. 'presso_result$`MR-PRESSO results`$`Global Test`$Pvalue'). Minor gaps keep it at 4 rather than 5: the multivariable MR block defers to 'See TwoSampleMR vignette' without code, and the 'Contamination mixture' comment mislabels a code path that actually calls mr_raps.

4 / 5

Workflow Clarity

Each section pairs a Goal/Approach header with embedded interpretation checkpoints (I^2 > 0.9 warning, p < 0.05 outlier cutoff, distortion-test meaning), and the comprehensive framework sequences eight analyses into one function with a summary step. It sits at 4 rather than 5 because there is no explicit ordering or decision guidance across methods (e.g. what to do when the Egger intercept is significant but the PRESSO global test is not).

4 / 5

Progressive Disclosure

The ~300-line body is entirely inline with no reference files at all; the comprehensive sensitivity framework, STROBE-MR checklist, and multivariable MR section are candidates for separate reference documents. Clear section headers keep it above the 2 anchor's unstructured inline dump, but nothing is offloaded to navigable references, matching the 3 anchor.

3 / 5

Total

15

/

20

Passed

Description

80%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, specific description that clearly names the three methods and their roles, with an explicit 'Use when' clause. Its main defect is that the description is literally truncated mid-word in the frontmatter ('instrum...'), cutting the trigger list short and costing it top marks on trigger quality and completeness.

Suggestions

Restore the complete 'Use when...' clause — the description is cut off mid-word at 'detecting pleiotropic instrum...', truncating the trigger-term list.

Add common synonyms users would naturally say, e.g. 'MR sensitivity analysis', 'instrument validity', or 'pleiotropy-robust MR', to broaden natural trigger coverage.

Sharpen the 'when' clause to emphasize sensitivity/pleiotropy checking specifically (e.g. 'Use when checking MR results for pleiotropic bias or running sensitivity analyses') to reduce overlap with a general MR-analysis skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions mapped to named tools: 'using MR-PRESSO for outlier removal, MR-Egger regression for directional pleiotropy, and Steiger filtering for variant directionality', matching the comprehensive-coverage anchor. No gaps in what the skill does, so it sits above the 4 anchor.

5 / 5

Completeness

Both 'what' (three named detection/correction methods) and 'when' ('Use when validating MR results, detecting pleiotropic instrum...') are present, but the when-clause is cut off mid-word, so it 'could be more explicit'. This is the 4 anchor; not 5 because the trigger clause is incomplete, not 3 because when is present and substantive.

4 / 5

Trigger Term Quality

Natural terms like 'Mendelian randomization', 'MR results', 'MR-PRESSO', 'Steiger', and 'MR assumptions' are present, but the 'Use when' clause is literally truncated mid-word ('detecting pleiotropic instrum...') and synonyms like 'sensitivity analysis' are absent. Good but incomplete coverage fits the 4 anchor, not the 5 anchor's comprehensive synonym set.

4 / 5

Distinctiveness Conflict Risk

A clear niche (pleiotropy detection/correction in MR) with distinct method-level triggers, but 'Use when validating MR results' overlaps with a general MR-analysis skill's territory. Mostly distinct with minor overlap risk matches the 4 anchor; not 5 because of that shared trigger, not 3 because the niche is well carved.

4 / 5

Total

17

/

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/Data Analysis/bio-causal-genomics-pleiotropy-detection/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.