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

tooluniverse-cancer-variant-interpretation

Index entry for an upstream research Skill intended for research work involving tooluniverse cancer variant interpretation. Maintained upstream by mims-harvard; source files are not included in this package.

personAuthor: OpenScientificSkillshubOpenAPI
open_in_newRepositorydownloadDownload package

tooluniverse-cancer-variant-interpretation — 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 tooluniverse cancer variant interpretation. 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:

Clinical interpretation of somatic cancer mutations for precision oncology. Transforms a gene + variant + cancer-type input into an actionable report: clinical evidence tier (CIViC, OncoKB), therapeutic options (FDA-approved + investigational), resistance mechanisms, prognosis, and matching clinical trials. Use for tumor-board variant calls, somatic-mutation actionability assessment, and treatment selection. Alway...

Canonical source

  • Upstream author or maintainer: mims-harvard
  • Repository: https://github.com/mims-harvard/ToolUniverse
  • Upstream Skill path: plugin/skills/tooluniverse-cancer-variant-interpretation/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.