heal

Detect and repair containerized infrastructure issues by checking service health and network connectivity.

Updated Mar 23, 2026
One-click install
npx skills add https://github.com/disciplin-run-org/jjstack --skill heal-disciplin-run-org
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: heal
Source: https://github.com/disciplin-run-org/jjstack/tree/main/skills/heal
Command: npx skills add https://github.com/disciplin-run-org/jjstack --skill heal-disciplin-run-org

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses the challenge of maintaining and repairing complex containerized infrastructure by automatically diagnosing and fixing common issues, reducing downtime and manual intervention.

Core Features & Use Cases

  • Infrastructure Health Checks: Verify container status, port accessibility, and health endpoints for services.
  • Automated Repairs: Restart, rebuild, or reconfigure services to restore operation when faults are detected.
  • Use Case: When a service becomes unresponsive or ports are closed, use this Skill to automatically bounce containers and reapply configuration, minimizing manual troubleshooting.

Quick Start

Use the heal skill to automatically diagnose and fix container and network issues in your deployment environment.

Frequently Asked Questions about heal

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

FAQPage Schema
How do I automate infrastructure recovery for unresponsive containerized services?

Automate infrastructure recovery by checking service health, network connectivity, and configuration drift to detect faults, then restarting or rebuilding containers to restore continuous operation and minimize manual troubleshooting.

What does automated container repair check when diagnosing deployment issues?

Automated container repair checks service health by verifying container status, testing port accessibility, and querying health endpoints to identify network connectivity problems and configuration drift causing downtime.

How do I fix configuration drift and closed ports in a containerized environment?

Fix configuration drift and closed ports by reapplying configuration settings and bouncing containers automatically, which restores port accessibility and ensures services return to their expected operational state.

Can I use automated recovery to maintain continuous operation without manual intervention?

Yes, you can use automated recovery to maintain continuous operation by diagnosing and repairing containerized infrastructure issues automatically, reducing the need for manual intervention during service outages.

When should I use automated diagnostics instead of manual troubleshooting for containers?

Use automated diagnostics for containers when dealing with complex infrastructure where quick detection of service health issues, network faults, and configuration drift is needed to reduce downtime faster than manual troubleshooting allows.