CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bidirectional-multi-phenotype-mr-research-planner

Generates complete bidirectional multi-phenotype Mendelian randomization research designs from a user-provided exposure family and outcome family. Always use this skill whenever a user wants to design, plan, or build a genome-wide causal-inference study based on publicly available GWAS summary statistics, especially when the article logic includes multiple exposures, multiple outcomes or subtypes, bidirectional MR, IV filtering, IVW as the main estimator, weighted median / MR-Egger / MR-PRESSO sensitivity analyses, leave-one-out testing, heterogeneity / pleiotropy checks, and multiple-testing control with FDR. Covers five study patterns (single-family bidirectional MR, multi-phenotype screening MR, subtype-resolved MR, phenome-style bidirectional causal map, mechanism-prioritized MR follow-up) and always outputs four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version...

Quality

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

73%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-sequenced, validation-rich planning workflow with proper one-level-deep reference structure and real bundle files behind every link. The dominant cost is redundancy — the Hard Rules section and the A–J section contracts restate step-level requirements repeatedly, inflating token cost without adding instruction.

Suggestions

Collapse Hard Rules 15–23 into a short 'Mandatory outputs' checklist or reference, since they verbatim restate requirements already stated in Steps 3–7 and Sections C.5, D, G, I, and J (e.g. rules 22 and 23 duplicate Section D's disclaimer and Section J's mandate).

Merge the 'Execution — 7 Steps' section with 'Mandatory Output Sections (A–J)' so each step states once what it must produce, instead of describing the deliverable twice (Step 4 = Section C, Step 4.5 = Section I, Step 6 = Section D).

Inline a one-line summary of the 8-field workflow template (the core deliverable format) next to the reference link in Step 6, so the most important output contract is visible without opening references/workflow-step-template.md.

DimensionReasoningScore

Conciseness

The body never explains MR concepts Claude already knows (good), but it is noticeably padded by restatement: Hard Rules 15–23 restate requirements already given verbatim in Steps 3–7 and Sections C.5/G/I/J (e.g. rule 22 repeats the Dataset Disclaimer rule from Section D, rule 23 repeats Section J's mandate), and the Steps section and the Mandatory Output Sections A–J re-cover the same ground (Step 3 = Section B, Step 4 = Section C, Step 4.5 = Section I). This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the noticeably-verbose level 2, since the padding is rule duplication, not concept explanation.

3 / 5

Actionability

Guidance is concrete for an instruction-only skill: verbatim redirect script ('This skill designs ... use an appropriate clinical or epidemiology framework'), exact dependency formulas ('exposure GWAS + outcome GWAS + IVW + sensitivity consistency'), pattern-selection tables, and a fully enumerated output contract (Sections A–J with per-section requirements). Per the rubric's code-vs-instruction note, absent code is not penalized. Not a 5: the pivotal 8-field workflow template is entirely deferred to references/workflow-step-template.md, so the core deliverable format is not visible in the body, and rule numbering skips 10, a small internal-consistency slip.

4 / 5

Workflow Clarity

Seven steps that 'always run in order', with an explicit validation checkpoint: Step 5 'Dependency Consistency Check (mandatory before output)' is a checklist ('Does bidirectional design appear without separate IV construction in both directions?') with a feedback loop ('If any dependency inconsistency is found, revise the plan before outputting'). Input validation with a stop-and-redirect, stated-default fallback in Step 1, and the Section J self-critical review add further checkpoints — this matches the top anchor (clear sequence, explicit validation, feedback loops, checklists).

5 / 5

Progressive Disclosure

The body is a genuine overview with eight clearly signaled one-level-deep links ('→ Detailed pattern logic: [references/study-patterns.md]'); all eight referenced files exist, and the reference files contain no further nested links. Not a 5: the main body carries substantial detail (23 Hard Rules and full per-section output contracts) that partly duplicates step content and could be consolidated, so placement is good but not fully clean.

4 / 5

Total

16

/

20

Passed

Description

87%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 highly specific, explicitly triggered description with an unambiguous what/when pair and minimal conflict risk. Its main weakness is bloat: the method-name enumeration is keyword-stuffed and the sentence ends mid-list with an ellipsis, suggesting the description ran past a sensible length.

DimensionReasoningScore

Specificity

Concrete actions are named — 'Generates complete bidirectional multi-phenotype Mendelian randomization research designs' and 'always outputs four workload configs (Lite / Standard / Advanced / Publication+) with recommended primary plan, step-by-step workflow, figure plan, validation strategy, minimal executable version' — with comprehensive method-level specifics (IVW, weighted median / MR-Egger / MR-PRESSO, FDR). Not a 5 because the long enumerated list of estimator names pads the description with keyword material rather than distinct actions; per the guidelines verbosity is not rewarded.

4 / 5

Completeness

Explicitly answers both parts: what — 'Generates complete ... research designs from a user-provided exposure family and outcome family'; when — 'Always use this skill whenever a user wants to design, plan, or build a genome-wide causal-inference study based on publicly available GWAS summary statistics, especially when ...'. Concrete trigger phrases are present, matching the top anchor; the trailing 'minimal executable version...' ellipsis looks truncated but both what and when are fully stated.

5 / 5

Trigger Term Quality

Good natural-term coverage a researcher would actually say — 'Mendelian randomization', 'bidirectional MR', 'GWAS summary statistics', 'causal-inference study', 'sensitivity analyses', 'FDR', 'subtypes'. Not a 5: common variations like 'two-sample MR', 'instrumental variables', or 'causal effects of' are missing, and the middle sentence reads as keyword stuffing (a dozen method names in one list), which the verbosity guideline penalizes.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinct triggers — 'bidirectional multi-phenotype Mendelian randomization' with 'GWAS summary statistics', IVW, and MR-PRESSO is highly unlikely to collide with any other skill category. It explicitly bounds the niche (study design from public GWAS summary data), matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

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

awesome-med-research-skills/Protocol Design/bidirectional-multi-phenotype-mr-research-planner/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.