Bioconductor Treesummarizedexperiment logo

Bioconductor Treesummarizedexperiment

Organization
bioMate-AI
bioconductor-treesummarizedexperiment

TreeSummarizedExperiment has extended SingleCellExperiment to include hierarchical information on the rows or columns of the rectangular data.

Overview

PublisherbioMate-AI
Repositorybiomate-bioconductor-kb
Skill namebioconductor-treesummarizedexperiment
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 Treesummarizedexperiment 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/single-cell/treesummarizedexperiment
  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/single-cell/treesummarizedexperiment .claude/skills/bioconductor-treesummarizedexperiment
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Bioconductor Treesummarizedexperiment 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 Treesummarizedexperiment 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 Treesummarizedexperiment 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.

TreeSummarizedExperiment

Dependencies & Environment

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

  • Version: 2.20.0 · Bioconductor: 3.23 · R: ≥ 4.6
  • Depends: SingleCellExperiment, S4Vectors, Biostrings
  • Imports: BiocGenerics, ape, rlang, dplyr, SummarizedExperiment, BiocParallel, IRanges, treeio
  • System requirements: URL
  • Install: BiocManager::install("TreeSummarizedExperiment")

When to Use

  • Storing rectangular experimental data alongside hierarchical tree structures using the TreeSummarizedExperiment class.
  • Aggregating data to different taxonomic levels (e.g., phylum or class) using aggTSE.
  • Subsetting data by specific tree nodes or leaves using subsetByNode.
  • Storing reference sequence data per feature using the referenceSeq slot.

When NOT to Use

  • For standard single-cell RNA-seq without hierarchical relationships, use SingleCellExperiment because the tree-related slots and overhead are unnecessary.
  • For purely manipulating or visualizing phylogenetic trees without rectangular assay data, use ape or ggtree directly because they are specialized for tree operations.

Data Requirements

  • An assays matrix representing observed data (e.g., counts) with rows as entities and columns as samples.
  • rowData and colData data frames for feature and sample annotations.
  • Hierarchical structures provided as phylo objects for rowTree and/or colTree.
  • Link information mapping assay rows/columns to tree nodes via rowNodeLab or colNodeLab.
  • Optional reference sequences as DNAStringSet or DNAStringSetList.

Key Parameters

  • rowTree: A phylo object representing the hierarchical structure on the rows of the assays.
  • rowNodeLab: A character vector linking the rows of the assays to the node labels of the rowTree.
  • colLevel: The desired aggregation level for columns in aggTSE, specified via node label or node number.
  • rowFun: The aggregate function (e.g., sum) applied to the row dimension in aggTSE.
  • only.leaf (TRUE): Logical in findDescendant to specify if only leaf descendants should be returned.
  • rowFirst (FALSE): Determines the aggregation order in aggTSE when aggregating both dimensions.
  • colDataCols: Specifies which columns of colData to keep in the final output of aggTSE.

Best Practices

  • Use toTree to convert a taxonomic data.frame into a phylo object before adding it to the object.
  • Use changeTree to replace an existing tree and update the mapping if nodes are labeled differently.
  • Use aggTSE with colDataCols to speed up aggregation by dropping irrelevant column data.
  • Avoid modifying rowLinks or colLinks manually to prevent breaking the link between assays and trees.

Common Pitfalls

  • Missing node labels: Row or column names in the assay do not match the node labels of the tree, causing them to be removed with warnings. Fix: Provide the correct mapping via rowNodeLab or colNodeLab during construction.
  • Broken links after pruning: Subsetting a tree with ape::keep.tip changes node numbers and breaks links. Fix: Use trackNode to track alias labels and update the LinkDataFrame accordingly.
  • Failed tree replacement: Replacing a tree directly with rowTree<- fails if names cannot be matched. Fix: Use changeTree with rowNodeLab when labels differ between the object and the new tree.

Alternatives

  • SingleCellExperiment: For storing single-cell data without hierarchical tree structures.
  • ape: For general phylogenetic tree manipulation without associated rectangular assay data.
  • ggtree: For visualizing phylogenetic trees, which TreeSummarizedExperiment relies on for plotting rather than implementing itself.

Citations

  • Huang R, et al. (2021). TreeSummarizedExperiment: a S4 class for data with tree structures. F1000Research.
  • Lun and Risso (2020). SingleCellExperiment.

References


Run this on BioMate

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

▶ Open treesummarizedexperiment on BioMate →

Frequently asked questions

What does the Bioconductor Treesummarizedexperiment AI skill do?

TreeSummarizedExperiment has extended SingleCellExperiment to include hierarchical information on the rows or columns of the rectangular data.

Why use Bioconductor Treesummarizedexperiment on TypingMind?

Because you install it once and use it with any model. Bioconductor Treesummarizedexperiment 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 Treesummarizedexperiment in TypingMind?

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

Which AI models can use Bioconductor Treesummarizedexperiment?

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 Treesummarizedexperiment?

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

Is the Bioconductor Treesummarizedexperiment 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 👇