multi-tool-consensus-annotation

Reconciles per-cell votes from multiple annotation methods into one consensus label set.

1|Updated Nov 20, 2025
One-click install
npx skills add https://github.com/tony-zhelonkin/scio --skill multi-tool-consensus-annotation-tony-zhelonkin
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: multi-tool-consensus-annotation
Source: https://github.com/tony-zhelonkin/scio/tree/main/skills/multi-tool-consensus-annotation
Command: npx skills add https://github.com/tony-zhelonkin/scio --skill multi-tool-consensus-annotation-tony-zhelonkin

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Single cell-type annotation methods each carry their own biases and failure modes, and combining their outputs naively produces dead tallies when vocabularies differ or inflated confidence when methods are correlated. This Skill provides a framework for running a panel of independent annotation voters and fusing their per-cell votes into one defensible, flag-heavy consensus label set. ## Core Features & Use Cases - Voter panel composition: Coordinates marker consensus, scANVI/scArches reference transfer, popV ensembles, treeArches open-set novelty detection, and Census KNN votes as independent per-cell voters. - Vocabulary harmonization: Maps every voter's native nomenclature into one canonical label space via crosswalk adapters before tallying, preventing the dead-tally bug where labels never string-match. - Conservative fusion policy: Emits a frozen per-cell contract with annotation_confidence, basis_of_label, novelty_flag, and consensus labels, preserving disagreement as Uncertain or Novel rather than forcing labels. - Use Case: Annotating an aging or treatment-remodeling single-cell cohort where no reference atlas covers all states, so treeArches flags out-of-distribution cells as candidate novel states while independent corroborators raise confidence on known types. ## Quick Start Ask the AI to run a multi-tool consensus annotation over your clustered single-cell dataset, harmonizing votes from reference transfer, popV, and treeArches into one frozen label set with confidence and novelty flags.

Frequently Asked Questions about multi-tool-consensus-annotation

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple cell-type annotation methods into one consensus?▼

Run each method as an independent per-cell voter, harmonize all labels into one canonical vocabulary with crosswalk adapters, then apply an ordered fusion policy. The consensus emits confidence, basis_of_label, and novelty flags per cell rather than forcing agreement.

Why do my annotation methods never agree on cell labels?▼

Methods using different nomenclatures never string-match, so agreement thresholds become unreachable. Fix this by mapping every voter's native labels into one canonical label space through a crosswalk table before tallying votes.

How do I detect novel cell states not in any reference atlas?▼

Use treeArches or scHPL as an open-set novelty guard whose distance-based rejection identifies out-of-distribution cells. These route to de-novo Novel states with condition-specific flags instead of snapping to known labels.

When should I use single-method annotation instead of a consensus panel?▼

Use a single method like scANVI label transfer when one reference fits your data well and its confidence suffices. The consensus framework is for cases where no single method is trustworthy enough alone.

How do I avoid overcounting agreement between correlated annotation methods?▼

Group methods sharing one evidence chain, such as a reference vote seeding both scANVI and treeArches, so they count as roughly one corroborator. Only genuinely independent legs like popV or atlas transfer should raise confidence to high.