isabl-monitor-analyses

Monitor Isabl analysis statuses, failures, and running jobs across projects.

3|3|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/juanesarango/isabl-mcp --skill isabl-monitor-analyses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: isabl-monitor-analyses
Source: https://github.com/juanesarango/isabl-mcp/tree/main/skills/isabl-monitor-analyses
Command: npx skills add https://github.com/juanesarango/isabl-mcp --skill isabl-monitor-analyses

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Monitoring and tracing Isabl analyses to identify failures, bottlenecks, and overall pipeline health.

Core Features & Use Cases

  • Check counts of analyses by status (SUCCEEDED, FAILED, RUNNING, SUBMITTED) across projects.
  • Identify problematic analyses (recent failures, stalled runs) and surface relevant metadata.
  • Generate concise running-status reports to aid debugging and operations.

Quick Start

Monitor analyses for a given project to view status, failures, and running jobs in one view.

Frequently Asked Questions about isabl-monitor-analyses

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

FAQPage Schema
How do I monitor Isabl analysis pipeline status and identify failures?

You can monitor Isabl analyses by querying projects and applications to compute status distributions, identify recent failures with storage references, and track running jobs. This surfaces bottlenecks and overall pipeline health for debugging.

What is the best way to check counts of Isabl analyses by status across projects?

Checking Isabl analysis status counts involves querying analyses by project and application to compute distributions across SUCCEEDED, FAILED, RUNNING, and SUBMITTED states, generating concise reports for operational decision making.

How do I retrieve recent failed Isabl analyses and their storage metadata?

Retrieving recent failed Isabl analyses involves querying the pipeline by project scope to surface problematic runs, extracting relevant metadata and storage references to aid debugging and operational tracing.

Can I track running jobs for specific Isabl applications like MUTECT?

Yes, you can track running jobs for specific Isabl applications like MUTECT by querying analyses scoped to that application, computing status distributions, and generating running-status reports to aid operations.

Does monitoring Isabl analyses require any external dependencies?

Monitoring Isabl analyses requires no external dependencies, allowing you to directly query project-scoped analyses, inspect failures, track running jobs, and generate status reports without additional environment setup.