isabl-debug-analysis

Diagnose failed Isabl analyses by inspecting metadata, head_job.sh, and logs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically debug a failed or problematic Isabl analysis to identify root causes and restore expected behavior.

Core Features & Use Cases

  • Retrieve and review analysis metadata (status, application, targets)
  • Inspect command scripts and logs (head_job.sh, head_job.log, head_job.err) to locate failures
  • Validate inputs and settings, and propose actionable fixes for re-run

Quick Start

Start debugging by loading an analysis PK and reviewing its head_job.sh and the corresponding log files to identify the failure cause.

Frequently Asked Questions about isabl-debug-analysis

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

FAQPage Schema
How do I debug a failed Isabl bioinformatics workflow?

To debug a failed Isabl bioinformatics workflow, retrieve the analysis metadata and inspect the head_job.sh script and head_job.log files to locate the exact failure cause. You can validate inputs and settings to propose corrective actions for re-running the analysis.

What is the best way to inspect Isabl analysis logs for errors?

The best way to inspect Isabl analysis logs for errors is to parse the analysis metadata and review the head_job.log and head_job.err files. This step-by-step verification reveals script failures and unexpected behavior across projects.

Why does my Isabl analysis show a FAILED status?

Your Isabl analysis shows a FAILED status due to script errors, invalid inputs, or incorrect settings. Diagnose the exact cause by parsing the analysis metadata and reviewing the head_job.sh and head_job.log files to guide corrective actions.

Can I diagnose unexpected behavior in Isabl analyses across different projects?

You can diagnose unexpected behavior in Isabl analyses across different projects by collecting status, application, and targets metadata. This allows step-by-step verification of scripts, inputs, and settings to identify and fix the root cause.

How to verify inputs and settings before re-running a failed Isabl analysis?

To verify inputs and settings before re-running a failed Isabl analysis, inspect the command scripts and log files like head_job.sh. Validating these components ensures you can propose actionable fixes for a successful re-run.