pipeline

Detect broken background pipelines and summarize HEALTHY, DEGRADED, or DEAD status.

8|5|Updated Feb 18, 2026

Search Tags:#background jobs #pipeline health #operations monitoring #systemd services #log staleness #process checks

Ready to run

npx skills add https://github.com/shenxingy/Clade --skill pipeline-shenxingy

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pipeline
Source: https://github.com/shenxingy/Clade/tree/main/configs/skills/pipeline
Command: npx skills add https://github.com/shenxingy/Clade --skill pipeline-shenxingy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It helps you quickly detect which background pipelines are healthy, degraded, or dead so you can stop debugging blindly and restore reliability.

Core Features & Use Cases

Health dashboard for background pipelines: Reads a local pipeline registry and per-project pipeline definitions to produce a clear status view.
DEGRADED/DEAD detection with actionable details: Runs health checks across system/process/port/log indicators and surfaces stale logs or non-responsive endpoints.
Optional continuous watch guidance: Provides instructions for a periodic monitor mode that alerts on status changes.

Quick Start

Ask the AI to run /pipeline to check the health of all registered pipelines.

Frequently Asked Questions about pipeline

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

FAQPage Schema

How do I monitor background pipeline health across multiple projects?▼

To monitor background pipeline health, this Skill reads a local pipeline registry and per-project pipeline definitions to produce a grouped dashboard showing HEALTHY, DEGRADED, or DEAD status for all registered services.

How do I detect stale logs or non-responsive systemd services?▼

Detect stale logs and non-responsive systemd services by executing a pipeline-check health script that evaluates system, process, port, and log indicators to surface failures and provide restart_cmd guidance.

Do I need a pipeline.yml file in every project to check pipeline status?▼

Yes, you need a PROJECT/.claude/pipeline.yml file for each project and a user-level ~/.claude/pipeline-registry.yml to define and register your background pipelines before executing health checks.

What is the best way to troubleshoot broken background pipelines?▼

The best way to troubleshoot broken background pipelines is to generate a health dashboard that groups services by status and surfaces specific operational failures like log staleness or non-responsive endpoints with actionable restart commands.

Can I set up continuous watch mode for operations monitoring of registered pipelines?▼

Yes, you can set up continuous operations monitoring by following the Skill's provided instructions for a periodic monitor mode that alerts on status changes for your registered background pipelines.