debug-pipeline

Diagnose directory-pipeline failures and provide exact fix commands.

17|2|Updated Feb 26, 2026
One-click install
npx skills add https://github.com/hadro/directory-pipeline --skill debug-pipeline-hadro
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: debug-pipeline
Source: https://github.com/hadro/directory-pipeline/tree/main/.claude/skills/debug-pipeline
Command: npx skills add https://github.com/hadro/directory-pipeline --skill debug-pipeline-hadro

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Diagnoses and guides you through diagnosing problems in the directory-pipeline project. It triggers a structured, multi-step diagnostic flow when the user reports symptoms like missing thumbnails, empty CSVs, or incorrect bounding boxes, and provides the exact fix command.

Core Features & Use Cases

  • Guided symptom selection with a menu of common failure modes.
  • Targeted file checks and step-by-step diagnostics to pinpoint root causes.
  • Produce precise, copy-paste fix commands to restore correct outputs.

Quick Start

Describe the symptom you observe, and I will run targeted checks to identify the root cause and provide a fix command.

Frequently Asked Questions about debug-pipeline

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

FAQPage Schema
How do I fix missing thumbnails or empty CSVs in my pipeline?

To fix an empty CSV in your directory-pipeline, a guided diagnostic flow runs targeted file checks to pinpoint the root cause and generates the exact copy-paste command needed to restore correct output.

Why does my pipeline output incorrect bounding boxes or missing canvas fragments?

Incorrect bounding boxes or missing canvas fragments typically result from processing failures within the directory-pipeline, which can be diagnosed using targeted step-by-step checks to identify and resolve the specific failure mode.

How do I troubleshoot directory-pipeline failures when outputs are completely missing?

To troubleshoot directory-pipeline failures with missing outputs, select the observed symptom from a menu of common failure modes to trigger targeted diagnostics that isolate the issue and provide the precise fix command.

What is the best way to diagnose pipeline problems without manually checking every file?

The best way to diagnose pipeline problems without manual file checks is using a structured diagnostic flow that automatically targets common failure modes and outputs the exact fix command to restore correct results.

Can I get exact fix commands for specific pipeline failure modes like missing thumbnails?

Yes, you can get exact fix commands for specific failure modes like missing thumbnails by describing the observed symptom, which triggers targeted diagnostics that produce precise commands to restore correct output.