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

conventional-non-oncology-hub-gene-research-planner

Index entry for an upstream research Skill intended for research work involving conventional non oncology hub gene research planner. Maintained upstream by aipoch; source files are not included in this package.

personAuthor: OpenScientificSkillshubOpenAPI

conventional-non-oncology-hub-gene-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 conventional non oncology hub gene 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 conventional non-oncology bioinformatics research designs from a user-provided disease context, process-related gene family or biological theme, and validation direction. Use when a study centers on multi-dataset bulk transcriptome integration, DEG analysis, process-gene intersection, enrichment analysis, GSEA, PPI hub-gene prioritization, TF/miRNA regulatory networks, ROC-based biomarker evalua...

Canonical source

  • Upstream author or maintainer: aipoch
  • Repository: https://github.com/aipoch/awesome-medical-research-skills
  • Upstream Skill path: conventional-non-oncology-hub-gene-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.