Omero Integration logo

Omero Integration

Community
dralkh
omero-integration

Microscopy data management platform. Access images via Python, retrieve datasets, analyze pixels, manage ROIs/annotations, batch processing, for high-content screening and microscopy workflows.

Overview

Publisherdralkh
Repositoryseerai
Skill nameomero-integration
Stars
96
Forks
5
Bundled files
8
LicenseUnknown
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.

  • 8 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by dralkh on GitHub. Read the source before you install it.

Installation

Install the Omero Integration 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/dralkh/seerai/tree/main/skills/omero-integration
  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/dralkh/seerai.git /tmp/seerai
mkdir -p .claude/skills
cp -r /tmp/seerai/skills/omero-integration .claude/skills/omero-integration
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Omero Integration 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 Omero Integration 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 Omero Integration 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.

OMERO Integration

Overview

OMERO is an open-source platform for managing, visualizing, and analyzing microscopy images and metadata. Access images via Python API, retrieve datasets, analyze pixels, manage ROIs and annotations, for high-content screening and microscopy workflows.

When to Use This Skill

This skill should be used when:

  • Working with OMERO Python API (omero-py) to access microscopy data
  • Retrieving images, datasets, projects, or screening data programmatically
  • Analyzing pixel data and creating derived images
  • Creating or managing ROIs (regions of interest) on microscopy images
  • Adding annotations, tags, or metadata to OMERO objects
  • Storing measurement results in OMERO tables
  • Creating server-side scripts for batch processing
  • Performing high-content screening analysis

Core Capabilities

This skill covers eight major capability areas. Each is documented in detail in the references/ directory:

1. Connection & Session Management

File: references/connection.md

Establish secure connections to OMERO servers, manage sessions, handle authentication, and work with group contexts. Use this for initial setup and connection patterns.

Common scenarios:

  • Connect to OMERO server with credentials
  • Use existing session IDs
  • Switch between group contexts
  • Manage connection lifecycle with context managers

2. Data Access & Retrieval

File: references/data_access.md

Navigate OMERO's hierarchical data structure (Projects → Datasets → Images) and screening data (Screens → Plates → Wells). Retrieve objects, query by attributes, and access metadata.

Common scenarios:

  • List all projects and datasets for a user
  • Retrieve images by ID or dataset
  • Access screening plate data
  • Query objects with filters

3. Metadata & Annotations

File: references/metadata.md

Create and manage annotations including tags, key-value pairs, file attachments, and comments. Link annotations to images, datasets, or other objects.

Common scenarios:

  • Add tags to images
  • Attach analysis results as files
  • Create custom key-value metadata
  • Query annotations by namespace

4. Image Processing & Rendering

File: references/image_processing.md

Access raw pixel data as NumPy arrays, manipulate rendering settings, create derived images, and manage physical dimensions.

Common scenarios:

  • Extract pixel data for computational analysis
  • Generate thumbnail images
  • Create maximum intensity projections
  • Modify channel rendering settings

5. Regions of Interest (ROIs)

File: references/rois.md

Create, retrieve, and analyze ROIs with various shapes (rectangles, ellipses, polygons, masks, points, lines). Extract intensity statistics from ROI regions.

Common scenarios:

  • Draw rectangular ROIs on images
  • Create polygon masks for segmentation
  • Analyze pixel intensities within ROIs
  • Export ROI coordinates

6. OMERO Tables

File: references/tables.md

Store and query structured tabular data associated with OMERO objects. Useful for analysis results, measurements, and metadata.

Common scenarios:

  • Store quantitative measurements for images
  • Create tables with multiple column types
  • Query table data with conditions
  • Link tables to specific images or datasets

7. Scripts & Batch Operations

File: references/scripts.md

Create OMERO.scripts that run server-side for batch processing, automated workflows, and integration with OMERO clients.

Common scenarios:

  • Process multiple images in batch
  • Create automated analysis pipelines
  • Generate summary statistics across datasets
  • Export data in custom formats

8. Advanced Features

File: references/advanced.md

Covers permissions, filesets, cross-group queries, delete operations, and other advanced functionality.

Common scenarios:

  • Handle group permissions
  • Access original imported files
  • Perform cross-group queries
  • Delete objects with callbacks

Installation

bash
uv pip install omero-py

Requirements:

  • Python 3.7+
  • Zeroc Ice 3.6+
  • Access to an OMERO server (host, port, credentials)

Quick Start

Basic connection pattern:

python
from omero.gateway import BlitzGateway

# Connect to OMERO server
conn = BlitzGateway(username, password, host=host, port=port)
connected = conn.connect()

if connected:
    # Perform operations
    for project in conn.listProjects():
        print(project.getName())

    # Always close connection
    conn.close()
else:
    print("Connection failed")

Recommended pattern with context manager:

python
from omero.gateway import BlitzGateway

with BlitzGateway(username, password, host=host, port=port) as conn:
    # Connection automatically managed
    for project in conn.listProjects():
        print(project.getName())
    # Automatically closed on exit

Selecting the Right Capability

For data exploration:

  • Start with references/connection.md to establish connection
  • Use references/data_access.md to navigate hierarchy
  • Check references/metadata.md for annotation details

For image analysis:

  • Use references/image_processing.md for pixel data access
  • Use references/rois.md for region-based analysis
  • Use references/tables.md to store results

For automation:

  • Use references/scripts.md for server-side processing
  • Use references/data_access.md for batch data retrieval

For advanced operations:

  • Use references/advanced.md for permissions and deletion
  • Check references/connection.md for cross-group queries

Common Workflows

Workflow 1: Retrieve and Analyze Images

  1. Connect to OMERO server (references/connection.md)
  2. Navigate to dataset (references/data_access.md)
  3. Retrieve images from dataset (references/data_access.md)
  4. Access pixel data as NumPy array (references/image_processing.md)
  5. Perform analysis
  6. Store results as table or file annotation (references/tables.md or references/metadata.md)

Workflow 2: Batch ROI Analysis

  1. Connect to OMERO server
  2. Retrieve images with existing ROIs (references/rois.md)
  3. For each image, get ROI shapes
  4. Extract pixel intensities within ROIs (references/rois.md)
  5. Store measurements in OMERO table (references/tables.md)

Workflow 3: Create Analysis Script

  1. Design analysis workflow
  2. Use OMERO.scripts framework (references/scripts.md)
  3. Access data through script parameters
  4. Process images in batch
  5. Generate outputs (new images, tables, files)

Error Handling

Always wrap OMERO operations in try-except blocks and ensure connections are properly closed:

python
from omero.gateway import BlitzGateway
import traceback

try:
    conn = BlitzGateway(username, password, host=host, port=port)
    if not conn.connect():
        raise Exception("Connection failed")

    # Perform operations

except Exception as e:
    print(f"Error: {e}")
    traceback.print_exc()
finally:
    if conn:
        conn.close()

Additional Resources

Notes

  • OMERO uses group-based permissions (READ-ONLY, READ-ANNOTATE, READ-WRITE)
  • Images in OMERO are organized hierarchically: Project > Dataset > Image
  • Screening data uses: Screen > Plate > Well > WellSample > Image
  • Always close connections to free server resources
  • Use context managers for automatic resource management
  • Pixel data is returned as NumPy arrays for analysis

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Omero Integration AI skill do?

Microscopy data management platform. Access images via Python, retrieve datasets, analyze pixels, manage ROIs/annotations, batch processing, for high-content screening and microscopy workflows.

Why use Omero Integration on TypingMind?

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

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dralkh/seerai/tree/main/skills/omero-integration. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Omero Integration?

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 Omero Integration?

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

Is the Omero Integration AI skill free?

Yes. It is published on GitHub by dralkh under the Unknown license. 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 👇