Back to skills
extension
Category: Productivity & OfficeNo API key required

bulk-omics-integrative-planner

Index entry for an upstream research Skill intended for research work involving bulk omics integrative planner. Maintained upstream by aipoch; source files are not included in this package.

personAuthor: OpenScientificSkillshubOpenAPI

bulk-omics-integrative-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 bulk omics integrative 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:

Designs complete integrated research plans for bulk transcriptomics, proteomics, metabolomics, and related omics from a user-provided biomedical direction. Always use this skill whenever a user wants to design, scope, or structure a bulk multi-omics or single-omics-plus-clinical study — including disease-focused, mechanism-focused, biomarker-focused, stratification-oriented, or translational projects. It should de...

Canonical source

  • Upstream author or maintainer: aipoch
  • Repository: https://github.com/aipoch/awesome-medical-research-skills
  • Upstream Skill path: bulk-omics-integrative-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.