omero-integration
by K-Dense-AIomero-integration skill for OMERO Python workflows in Backend Development. Connect to OMERO, retrieve projects, datasets, images, ROIs, annotations, tables, and run batch scripts with less guesswork.
This skill scores 78/100, which means it is a solid directory candidate for users doing OMERO microscopy work. It is triggerable from a clear domain focus (OMERO Python API, data retrieval, ROIs, metadata, tables, scripts) and the repository provides enough workflow detail to help an agent operate with less guesswork than a generic prompt, though users should still expect to piece together setup from references rather than a single quick-start path.
- Broad, concrete OMERO workflow coverage across connection, data access, image processing, ROIs, metadata, tables, and batch scripts.
- Good operational depth: the SKILL.md points to eight dedicated reference files, and the body includes executable Python examples and workflow-oriented headings.
- No placeholder or experimental markers; frontmatter is valid and the content is substantial enough to support real use in microscopy automation.
- No install command or explicit setup/onboarding flow, so users may need prior OMERO familiarity to get started.
- The repository is reference-heavy and fragmented across multiple files, which may slow first-time adoption compared with a single guided workflow.
Overview of omero-integration skill
What omero-integration is for
The omero-integration skill helps you work with OMERO from Python when the job is not “write a quick prompt,” but reliably connect, fetch microscopy objects, and manipulate image-linked data. It is aimed at backend development and scientific automation where you need the omero-integration skill to handle projects, datasets, images, ROIs, annotations, tables, or batch scripts with fewer assumptions than a generic coding prompt.
Best-fit users and jobs
Use omero-integration if you are building tools for microscopy data management, screening pipelines, or lab backends that need OMERO API access. The practical job-to-be-done is usually one of these: authenticate to a server, traverse OMERO hierarchy, pull pixel data, attach metadata, or run server-side processing with predictable object IDs and outputs.
Why this skill is worth installing
The main value of omero-integration is that it nudges you toward OMERO-specific patterns instead of generic Python guesses. That matters because OMERO work is constrained by session handling, object types, permissions, group context, and the difference between client-side data access and server-side batch execution. The skill is most useful when you need repeatable integration guidance, not just example code.
When it is a good or bad fit
It is a strong fit for Python-based OMERO automation, image analysis, annotation workflows, and high-content screening. It is a weaker fit if you only need a one-off query, if you are not using OMERO at all, or if your task is mostly UI configuration rather than API-driven backend development.
How to Use omero-integration skill
Install and inspect the right files
Install the omero-integration skill with the directory’s normal skill install flow, then read SKILL.md first and branch into references/connection.md, references/data_access.md, references/image_processing.md, references/metadata.md, references/rois.md, references/tables.md, references/scripts.md, and references/advanced.md as needed. For omero-integration install decisions, the reference files matter more than the top-level summary because they show the exact connection, retrieval, and update patterns the skill expects.
Start from a concrete OMERO task
Good prompts name the OMERO object type, the operation, and the context. For example: “Connect to OMERO with BlitzGateway, list datasets in group 5, and export image IDs with names,” or “Create ROIs on images from dataset 42 and attach a QC tag.” That level of specificity makes omero-integration usage much more reliable than asking for “help with OMERO.”
Read the workflow files in order
For connection problems, read references/connection.md first. For object traversal and filtering, use references/data_access.md. For pixels and derived images, go to references/image_processing.md. For tags, comments, and map annotations, use references/metadata.md. For shape creation and ROI linking, use references/rois.md. For batch execution, use references/scripts.md. This order reduces guesswork and helps you match the skill to the exact OMERO layer you are changing.
Give inputs that reduce OMERO ambiguity
A strong omero-integration guide prompt should include server host, auth style, object IDs, hierarchy depth, and output target. Example: “Using an existing session, fetch Image 123, get the first Z plane for channel 1, and return the NumPy shape plus min/max.” If you omit the object scope or group context, the assistant may give code that works syntactically but fails against OMERO permissions or the wrong container.
omero-integration skill FAQ
Is omero-integration only for OMERO Python API work?
Mostly yes. The skill is centered on OMERO Python workflows such as BlitzGateway, object retrieval, ROI handling, annotations, and script execution. If your task is outside OMERO or does not involve API-level data operations, a generic Python prompt is usually enough.
Do I need to be an expert to use it?
No. The omero-integration skill is useful for beginners who need a reliable starting pattern, but you still need to know what object you want and where it lives in OMERO. Beginners usually get better results when they provide one image, one dataset, or one script goal instead of a broad “analyze my data” request.
How is this different from ordinary prompting?
An ordinary prompt may produce plausible Python, but omero-integration is better when you need OMERO-specific choices: connection cleanup, session reuse, hierarchy traversal, and the right API object methods. It lowers the chance of using the wrong object model or forgetting server-side constraints.
When should I not use this skill?
Do not reach for omero-integration if you only need a UI walkthrough, if your data is not in OMERO, or if you cannot provide enough context to identify the object hierarchy. It is also not the best choice if your task is purely local image processing with no OMERO integration.
How to Improve omero-integration skill
Provide the smallest valid OMERO scope
The best omero-integration results come from tight scope: one server, one user context, one object type, one expected output. Say “dataset 88 in group 3” instead of “all my datasets,” and specify whether you want names, IDs, pixel arrays, ROI shapes, or attached annotations. This sharply improves relevance and avoids overbroad code.
State constraints that affect implementation
Mention whether you can use an existing session, whether secure connection is required, whether the task must run locally or as an OMERO script, and whether you need read-only or write access. Those details change the implementation path more than cosmetic prompt wording does.
Ask for the exact output shape you need
If you want reusable code, say so. If you need a one-off script, ask for that. If you want omero-integration for Backend Development, ask for functions, error handling, and cleanup. If you need analysis results stored back in OMERO, specify the target annotation or table format so the first answer can be operational instead of illustrative.
Iterate from connection to data to writeback
A strong workflow is: connect successfully, verify the object query, inspect image or metadata fields, then add ROI, annotation, or table writeback. If the first output fails, refine by adding the failing object type, group context, or method call rather than asking for a fresh rewrite.