BIOMERO.WorkflowSkills
biomero-workflow-skills is a small, framework-neutral catalog for Agent
Plugins and Agent Skills stored with BIOMERO workflow repositories. It resolves
exact GitHub revisions, validates each package locally, and exposes typed
catalog data to OMERO plugins.
Agent Plugins 1.0.0 are discovered from <workflow>_plugin_path (default .).
The package uses its bundled schema without network access, reads only immediate
skills/*/SKILL.md directories, and materializes only bounded UTF-8 skill files
and text references. Repositories without plugin.json retain the 0.x
_agents/skills fallback. A present but invalid manifest is reported as an
error.
It is an optional provider for
OMERO.Analysis.
It is not an OMERO.web application and does not modify or import
OMERO.biomero.
Basic use
from biomero_workflow_skills import WorkflowSkillCatalog
catalog = WorkflowSkillCatalog()
available = catalog.get_catalog("omero-analysis")
package = catalog.get_package(
"cisegmentation",
"analyze-cisegmentation-measurements",
)
For stateless adapters, get_package(..., consumer="omero-analysis") is
also supported and performs the consumer-filtered catalog lookup first.
Only attachment-analysis skills explicitly declaring omero-analysis are
returned. [APPLICATIONS] is intentionally ignored; applications such as
BIOMERO.ZarrViewer publish their own skills.
The package reads BIOMERO_WORKFLOW_SKILLS_CONFIG when set. Otherwise it merges
the existing files at /etc/slurm-config.ini, /OMERO/slurm-config.ini, and
~/slurm-config.ini, matching BIOMERO's configuration precedence.
Public GitHub repositories need no credential. Set BIOMERO_GITHUB_TOKEN to a
read-only token for private repositories or a larger API allowance.
The cache follows configured release pins: tags and commits are immutable, while branches are revalidated hourly with GitHub ETags. Removing a workflow or skill removes it from the next authoritative response; stale content is used only for a transient failure of the same unchanged source.
See Workflow skill authoring and deployment for the repository contract, security model, caching, and plugin integration.
Metadata
Release files for biomero-workflow-skills 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| biomero_workflow_skills-0.4.0.tar.gz | 28.2 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| biomero_workflow_skills-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 50.8 kB
Release files / biomero_workflow_skills-0.4.0.tar.gz
| Download URL | biomero_workflow_skills-0.4.0.tar.gz |
|---|---|
| Size | 28.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
693d490a7eda6d92fc90361af81d34aeb78c1f4190570ae4740ca628414b81f4
|
|
BLAKE2b-256 checksum How to use checksums |
79b5038df62e3d2aeff280df3ab762f8037919d8114081e22cff20ea6eff1e4e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency logRelease files / biomero_workflow_skills-0.4.0-py3-none-any.whl
| Download URL | biomero_workflow_skills-0.4.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e6fa3fb6af782decf01d21758ecf4f61d10ace5611c949fd079ddfe15c4d5bfc
|
|
BLAKE2b-256 checksum How to use checksums |
4da50735b9f1176da311e15529071e2e80aea8ad172c1374dd56cede99ecff83
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Aug 10, 2026.
Transparency log