Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

biomedical-imaging-pathology

Estrellas1

Forks0

Actualizado1 de julio de 2026 a las 23:09

Plan biomedical imaging workflows across DICOM, pathology slides, PACS metadata, PathML/histolab-style tiling, image QC, cohort metadata, and privacy-safe reporting.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

BaranziniLab

BaranziniLab/biorouter-skills

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Científicos biológicos, todos los demásCiencias de la vida, físicas y sociales·SOC 19-1029

SKILL.md

readonly

name	biomedical-imaging-pathology
description	Plan biomedical imaging workflows across DICOM, pathology slides, PACS metadata, PathML/histolab-style tiling, image QC, cohort metadata, and privacy-safe reporting.
user-invocable	true
license	Apache-2.0

Biomedical Imaging and Pathology

Source adaptation: BioRouter-original synthesis inspired by broad Scientific Agent Skills and Auto-Empirical Research Skills capability patterns, rewritten under Apache-2.0. Do not copy upstream text; use this as a native BioRouter routing and quality-control checklist.

When to Use

Use this skill when the user asks for Imaging. Load more specific BioSkills, BRXT extensions, or language skills when the task touches a concrete dataset, file format, package, or platform.

Intake

Collect the minimum context before acting:

Research question or operational goal.
Data source, file format, platform, package, or API involved.
Unit of analysis and expected output.
Privacy, credential, licensing, and compute constraints.
Whether the user wants a plan, executable code, review, or installed-tool workflow.

Native BioRouter Routing

Prefer these BioRouter-native routes before writing new glue code:

Use relevant BRXT extensions when platform/API access is needed.
Use scientific-research for broad research orchestration.
Use citation-temporal-integrity and claim-evidence-integrity for evidence-heavy deliverables.
Use replication-package-audit when outputs must be reproducible.
Use python-scripting, r-scripting, or BioSkills for package-specific code style.

Quality Gates

Before presenting results as final:

State the data provenance and tool/package versions.
Separate exploratory output from confirmatory evidence.
Check that identifiers, coordinates, sample ids, citations, or run ids are preserved.
Identify assumptions that could change the conclusion.
Provide a rerunnable command, notebook cell, or workflow outline when execution is involved.
Mark anything requiring credentials, proprietary data, or external services as unverified unless it was actually checked.

Output Pattern

Return a compact work plan first, then the implementation or review. For each result, include:

Decision made.
Evidence or file/API source.
Failure modes.
Next verification step.

Más de este repositorio

mismo repositorio

computational-fluid-dynamics

BaranziniLab/biorouter-skills

Plan and review computational fluid dynamics workflows with meshes, boundary conditions, turbulence models, OpenFOAM/FluidSim-style solvers, validation cases, convergence checks, and reproducible simulation artifacts. Use when users mention CFD, fluid dynamics, Navier-Stokes, meshing, turbulence, OpenFOAM, or flow simulation.

2026-07-011

arbor-optimization

BaranziniLab/biorouter-skills

Run evaluator-driven hypothesis trees for improving research artifacts, prompts, analyses, and designs. Use when a task needs branch-and-prune exploration, rubric scoring, iterative refinement, or explicit comparison of competing scientific/workflow alternatives.

2026-07-011

autoskill-workflow-discovery

BaranziniLab/biorouter-skills

Detect repeated user workflows and draft native BioRouter skills, hooks, or checklist updates from observed work patterns. Use when users ask to turn repeated work, screen-history patterns, project routines, or recurring guardrails into reusable BioRouter skills.

2026-07-011

bids-neuroimaging

BaranziniLab/biorouter-skills

Plan and audit BIDS neuroimaging datasets, derivatives, validation, metadata, and reproducible preprocessing. Use when users mention BIDS, fMRI, MRI, EEG/MEG/iEEG, DICOM conversion, dataset_description.json, participants.tsv, or neuroimaging derivatives.

2026-07-011

clinical-ai-modeling

BaranziniLab/biorouter-skills

Plan and review clinical AI modeling workflows with EHR cohorts, PyHealth-style tasks, validation, bias checks, calibration, safety boundaries, and no-PHI handling. Use when users ask about clinical prediction models, risk scores, treatment-response ML, medical reports, or clinical model evaluation.

2026-07-011

general-time-series-forecasting

BaranziniLab/biorouter-skills

Plan and review general time-series forecasting with classical models, ML, foundation models, backtesting, leakage checks, and uncertainty. Use for non-omics forecasting, sensor streams, operations, finance, clinical vitals, demand, or irregular temporal data.

2026-07-011

Biomedical Imaging and Pathology

When to Use

Use this skill when the user asks for Imaging. Load more specific BioSkills, BRXT extensions, or language skills when the task touches a concrete dataset, file format, package, or platform.

Intake

Collect the minimum context before acting:

Research question or operational goal.

Data source, file format, platform, package, or API involved.

Unit of analysis and expected output.

Privacy, credential, licensing, and compute constraints.

Whether the user wants a plan, executable code, review, or installed-tool workflow.

Native BioRouter Routing

Prefer these BioRouter-native routes before writing new glue code:

Use relevant BRXT extensions when platform/API access is needed.

Use scientific-research for broad research orchestration.

Use citation-temporal-integrity and claim-evidence-integrity for evidence-heavy deliverables.

Use replication-package-audit when outputs must be reproducible.

Use python-scripting, r-scripting, or BioSkills for package-specific code style.

Quality Gates

Before presenting results as final:

State the data provenance and tool/package versions.

Separate exploratory output from confirmatory evidence.

Check that identifiers, coordinates, sample ids, citations, or run ids are preserved.

Identify assumptions that could change the conclusion.

Provide a rerunnable command, notebook cell, or workflow outline when execution is involved.

Mark anything requiring credentials, proprietary data, or external services as unverified unless it was actually checked.

Output Pattern

Return a compact work plan first, then the implementation or review. For each result, include:

Decision made.

Evidence or file/API source.

Failure modes.

Next verification step.