flowio

Parse FCS 2.0 to 3.1 files to extract event data and metadata.

15|2|Updated Dec 17, 2025
One-click install
npx skills add https://github.com/rubensliv/k-dense-ai --skill flowio-rubensliv
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: flowio
Source: https://github.com/rubensliv/k-dense-ai/tree/main/scientific-skills/flowio
Command: npx skills add https://github.com/rubensliv/k-dense-ai --skill flowio-rubensliv

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

FlowIO solves the challenge of reading Flow Cytometry Standard (FCS) files, extracting event data as numerical arrays, and retrieving channel metadata for downstream analysis and data pipelines.

Core Features & Use Cases

  • Read FCS v2.0, v3.0, and v3.1 files and access event data and TEXT metadata.
  • Convert events to NumPy arrays or export to CSV/DataFrame for analytics and visualization.
  • Handle single- and multi-dataset files with robust error handling and preprocessing options.

Quick Start

Process a sample.fcs file to extract event data and channel metadata and export to CSV.

Frequently Asked Questions about flowio

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

FAQPage Schema
How do I parse FCS files and extract flow cytometry event data?

FCS files are parsed by reading Flow Cytometry Standard v2.0 to v3.1 data to extract event arrays and TEXT metadata. This handles single- and multi-dataset files with robust error-handling mechanisms for downstream analysis.

Can I convert flow cytometry events to a NumPy array or CSV?

Extracted flow cytometry events can be converted to NumPy arrays or exported to CSV and DataFrame formats. This enables seamless analytics and visualization within data pipelines.

Does flowio support multi-dataset FCS files and automatic channel typing?

Multi-dataset FCS files are supported with automatic channel typing and preprocessing options. The parser implements robust error handling across FCS versions 2.0, 3.0, and 3.1.

What is the best way to extract channel metadata from FCS files for data pipelines?

Extracting channel metadata is done using a parser that retrieves TEXT metadata and event data simultaneously. This allows direct integration into preprocessing steps for data pipelines.

Do I need external dependencies to parse FCS v3.1 files?

No external dependencies are required to parse FCS v3.1 files. The parser operates independently to extract event data and metadata without additional libraries.

Why does my FCS file parsing fail with multi-dataset configurations?

FCS file parsing may fail without proper error-handling mechanisms for multi-dataset configurations. Using a parser with robust preprocessing options ensures events are extracted correctly across versions.