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

comparative-network-toxicology-shared-index-3d4e7c

Index entry for comparative-network-toxicology-shared-index-3d4e7c, an upstream research Skill maintained by aipoch. Source files are not included; see the canonical repository.

person作者: OpenScientificSkillshubOpenAPI

comparative-network-toxicology-shared-mechanism-reference-grounded — 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 comparative network toxicology shared mechanism reference grounded. 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 comparative network-toxicology research designs from a user-provided exposure pair, shared toxic phenotype, and validation direction. Use when a study centers on two related exposures under one outcome and needs target collection, shared-vs-specific target decomposition, enrichment, PPI hub prioritization, docking, optional transcriptomic cross-checks, and conservative mechanistic synthesis. Cov...

Canonical source

  • Upstream author or maintainer: aipoch
  • Repository: https://github.com/aipoch/awesome-medical-research-skills
  • Upstream Skill path: comparative-network-toxicology-shared-mechanism-reference-grounded/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.