返回 Skill 列表
extension
分类: 效率与办公无需 API Key

bidirectional-multi-phenotype-mr-research-planner

Index entry for an upstream research Skill intended for research work involving bidirectional multi phenotype mr research planner. Maintained upstream by aipoch; source files are not included in this package.

person作者: OpenScientificSkillshubOpenAPI

bidirectional-multi-phenotype-mr-research-planner — upstream index

This is an index-only record created by OpenScientificSkills. It contains an attributed catalog summary, but does not bundle, mirror, or redistribute the upstream Skill instructions, code, or assets.

What this Skill is for

This indexed Skill is intended for research work involving bidirectional multi phenotype mr research planner. It helps researchers discover the upstream project that may provide instructions, templates, scripts, or workflow guidance for that task. Exact capabilities, requirements, and behavior must be confirmed in the canonical repository because they can change upstream.

Attributed upstream catalog summary:

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

Canonical source

  • Upstream author or maintainer: aipoch
  • Repository: https://github.com/aipoch/awesome-medical-research-skills
  • Upstream Skill path: bidirectional-multi-phenotype-mr-research-planner/SKILL.md
  • Upstream license status: not verified

The CC0-1.0 value on this ModelScope entry applies only to the newly written index structure and explanatory text. It does not apply to the attributed upstream summary and does not grant any license to the upstream repository.

Before use

Open the canonical repository, review its current license, security posture, dependencies, and instructions, and obtain any permission required by the upstream author. Always treat the upstream repository as the source of truth.