Bioconductor Biovizbase logo

Bioconductor Biovizbase

Organization
bioMate-AI
bioconductor-biovizbase

The biovizBase package is designed to provide a set of utilities, color schemes and conventions for genomic data. It serves as the base for various high-level packages for biological data visualization. This saves development effort and enc

Overview

PublisherbioMate-AI
Repositorybiomate-bioconductor-kb
Skill namebioconductor-biovizbase
Stars
804
Forks
66
Bundled files
Instructions only
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by bioMate-AI on GitHub. Read the source before you install it.

Installation

Install the Bioconductor Biovizbase AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/bioMate-AI/biomate-bioconductor-kb/tree/main/skills/general/biovizbase
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/bioMate-AI/biomate-bioconductor-kb.git /tmp/biomate-bioconductor-kb
mkdir -p .claude/skills
cp -r /tmp/biomate-bioconductor-kb/skills/general/biovizbase .claude/skills/bioconductor-biovizbase
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bioconductor Biovizbase in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Bioconductor Biovizbase on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Bioconductor Biovizbase is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

biovizBase

Dependencies & Environment

Package-intrinsic requirements from the Bioconductor landing page — reproduce in any R environment.

  • Version: 1.60.0 · Bioconductor: 3.23 · R: ≥ 4.6
  • Imports: scales, Hmisc, RColorBrewer, dichromat, BiocGenerics, S4Vectors, IRanges, Seqinfo, GenomeInfoDb, GenomicRanges, SummarizedExperiment, Biostrings, Rsamtools, GenomicAlignments, GenomicFeatures, AnnotationDbi, VariantAnnotation, ensembldb, AnnotationFilter, rlang
  • System requirements: URL
  • Install: BiocManager::install("biovizBase")

When to Use

  • Generating colorblind-safe palettes for biological data visualization using colorBlindSafePal().
  • Retrieving standardized, biologically sensible color schemes for cytobands, strands, or nucleotides using getBioColor().
  • Manipulating GRanges objects for plotting by adding disjoint stepping levels (addStepping()) or shrinking gaps (shrinkageFun()).
  • Fetching chromosome ideograms from the UCSC genome browser using getIdeogram().

When NOT to Use

  • For high-level, out-of-the-box static genomic plotting, use ggbio because biovizBase only provides the low-level utilities and color schemes.
  • For interactive genomic graphics, use visnab because biovizBase is designed as a foundational infrastructure package rather than an interactive plotting tool.

Data Requirements

  • Input Format: GRanges objects (from the GenomicRanges package) for genomic manipulations, or character vectors of biological categories (e.g., "A", "C", "T", "G", "N") for color mapping.
  • Structure: Genomic coordinates must be properly formatted in GRanges to use utilities like addStepping(), maxGap(), or gaps().

Key Parameters

  • repeatable (TRUE): Controls whether to repeat colors if the required number exceeds the maximum colors allowed in colorBlindSafePal().
  • source ("default"): Specifies whether to retrieve colors from the default fixed settings or from the user's options in getBioColor().
  • extend.size (5): The size to extend ranges when adding stepping levels in addStepping().
  • max.gap (0): The maximum gap size allowed when shrinking gaps using shrinkageFun().
  • cytoband (TRUE): Logical indicating whether to include cytoband information when fetching an ideogram with getIdeogram().

Best Practices

  • Use getBioColor() instead of accessing options directly to hide internal complexity and ensure uniform color schemes across all graphics.
  • Check custom color palettes for colorblind safety using dichromat() to ensure accessibility for deuteranopia and protanopia.
  • Use plotColorLegend() or showColor() to visually verify your selected color schemes before applying them to complex genomic plots.

Common Pitfalls

  • Running out of colors in a palette: Requesting more colors than a specific colorblind-safe palette supports returns NA or errors. Fix: Set repeatable = TRUE when calling the function returned by colorBlindSafePal().
  • Inconsistent color themes across plots: Hardcoding colors leads to mismatched figures. Fix: Temporarily edit colors in the global options (options(biovizBase = opts)) so getBioColor() returns uniform colors globally.

Alternatives

  • ggbio: Built on top of biovizBase, use this for actual static genomic plotting rather than just base utilities.
  • visnab: Built on top of biovizBase, use this for interactive genomic graphics.
  • RColorBrewer: Provides general color palettes, but lacks the built-in biological category mappings (like nucleotides or cytobands) provided by biovizBase.
  • dichromat: Used for colorblindness simulation, but does not provide genomic-specific color generators out of the box.

Citations

  • Tengfei Yin, Michael Lawrence, Dianne Cook (2026). "An Introduction to biovizBase".

References


Run this on BioMate

This skill is the knowledge layer — when, why, and how to use biovizbase. To run this analysis on your own data with managed compute, automated QC, and reproducible outputs, use BioMate — free to start.

▶ Open biovizbase on BioMate →

Frequently asked questions

What does the Bioconductor Biovizbase AI skill do?

The biovizBase package is designed to provide a set of utilities, color schemes and conventions for genomic data. It serves as the base for various high-level packages for biological data visualization. This saves development effort and enc

Why use Bioconductor Biovizbase on TypingMind?

Because you install it once and use it with any model. Bioconductor Biovizbase is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Bioconductor Biovizbase in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/bioMate-AI/biomate-bioconductor-kb/tree/main/skills/general/biovizbase. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Bioconductor Biovizbase?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Bioconductor Biovizbase?

As many as you like. As long as a model supports skills, you can use Bioconductor Biovizbase with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Bioconductor Biovizbase AI skill free?

It is published on GitHub by bioMate-AI. Check the repository for licensing terms. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇