gpu-quality-priority

Enforce GPU-only quality-preserving processing for multiplex immunofluorescence image analysis.

3|Updated Dec 10, 2025
One-click install
npx skills add https://github.com/smith6jt-cop/Skills_Registry --skill gpu-quality-priority
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gpu-quality-priority
Source: https://github.com/smith6jt-cop/Skills_Registry/tree/main/plugins/kintsugi/gpu-quality-priority/skills/gpu-quality-priority
Command: npx skills add https://github.com/smith6jt-cop/Skills_Registry --skill gpu-quality-priority

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill defines a strict processing policy for KINTSUGI that prioritizes quality over speed and enforces GPU usage when available, with no CPU fallback.

Core Features & Use Cases

  • NEVER sacrifice quality for speed; use production-default parameters unless negligible impact is verified.
  • ALWAYS use GPU when available; disable or remove CPU options.
  • Remove CPU options when GPU exists to enforce GPU-only workflows.

Quick Start

In your pipeline, ensure GPU is enabled and a GPU is available. If not, fail fast with a clear error. Do not enable fast-mode or CPU fallbacks. See code patterns in the SKILL body for enforcement.

Frequently Asked Questions about gpu-quality-priority

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

FAQPage Schema
How do I process multiplex immunofluorescence images on GPU with quality preservation?

GPU-first quality-preserving processing for immunofluorescence images uses CUDA-backed operations on multi-GPU NVIDIA systems. This Skill enforces GPU-only execution through CuPy, applying production-default parameters across cycle processing, illumination correction, stitching, deconvolution, and segmentation without CPU fallback or fast-mode shortcuts.

Can I run high-throughput batch image processing on multiple GPUs with consistent quality?

Yes. This Skill enables high-throughput batch processing on multi-GPU NVIDIA systems by enforcing explicit device_id selection, ensuring consistent GPU-backed operation. It removes CPU options entirely and prevents quality degradation through validated parameter defaults across all processing stages.

What happens if GPU is unavailable when processing images with this Skill?

The Skill fails fast with a clear error rather than falling back to CPU execution. GPU availability is a hard requirement; no fallback modes or CPU alternatives are provided, ensuring GPU-first workflows are never compromised.

How does this approach differ from CPU-based or hybrid image processing pipelines?

This Skill prioritizes quality over speed by enforcing GPU-only execution, removing all CPU options, and locking production-default parameters. Unlike hybrid pipelines that offer CPU fallbacks or speed-quality trade-offs, it guarantees consistent quality through GPU acceleration without compromise.

What image processing stages does GPU-enforced quality control cover?

The Skill covers cycle processing, illumination correction, stitching, deconvolution, and segmentation for multiplex immunofluorescence analysis. All stages run on GPU with CuPy, maintaining validated quality defaults throughout the pipeline.

Do I need to modify my existing image processing pipeline to use this Skill?

Yes. You must ensure GPU is enabled, a GPU device is available, and you provide explicit device_id selection. The Skill removes fast-mode and CPU options, so existing pipelines using those features require reconfiguration to enforce GPU-only operation.