pegasus-debug

Diagnoses Pegasus workflow failures by analyzing error messages and logs.

Updated Feb 11, 2026
One-click install
npx skills add https://github.com/pegasus-isi/pegasus-workflow-toolkit --skill pegasus-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pegasus-debug
Source: https://github.com/pegasus-isi/pegasus-workflow-toolkit/tree/main/.claude/skills/pegasus-debug
Command: npx skills add https://github.com/pegasus-isi/pegasus-workflow-toolkit --skill pegasus-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and scripts (resource) components.

What problem does it solve?

This Skill helps users diagnose and fix errors in Pegasus workflows by analyzing error messages and logs.

Core Features & Use Cases

  • Error Analysis: Identifies common failure patterns in Pegasus workflows, including file staging, container, resource, dependency, and wrapper script issues.
  • Guided Debugging: Provides step-by-step instructions to gather necessary information and suggests specific code or configuration fixes.
  • Use Case: When a Pegasus workflow fails, use this Skill to pinpoint the cause, such as a missing input file or an incorrect command in a wrapper script, and receive precise instructions on how to resolve it.

Quick Start

Use the pegasus-debug skill to diagnose a workflow failure by providing the error message and run directory.

Frequently Asked Questions about pegasus-debug

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

FAQPage Schema
How do I debug a failing Pegasus workflow?

To debug a failing Pegasus workflow, analyze error messages, logs, and run directory contents to identify root causes like file staging or container issues, then apply suggested configuration and code fixes.

Why does my Pegasus workflow fail during file staging or container setup?

Pegasus workflow failures during file staging or container setup often stem from missing inputs or misconfigured environments. Analyzing run directory logs identifies the root cause for these specific resource or container errors.

How do I troubleshoot wrapper script errors in a Pegasus pipeline?

Troubleshoot wrapper script errors in a Pegasus pipeline by examining workflow logs and run directory contents to locate incorrect commands, then apply corrective code fixes and verification steps to resolve the execution failure.

What is the best way to resolve Pegasus resource allocation and dependency failures?

Resolve Pegasus resource allocation and dependency failures by analyzing error messages and run directory contents to identify resource bottlenecks or missing dependencies, then apply the provided configuration adjustments to execute the workflow.

What information do I need to diagnose a Pegasus workflow crash?

Diagnosing a Pegasus workflow crash requires providing the specific error message and the run directory path. This allows the system to analyze logs and contents to identify root causes like staging, container, or wrapper script failures.