launchd-process-health-check

Diagnose launchd-managed processes and detect stale exit codes.

2|7|Updated Jun 19, 2026
One-click install
npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill launchd-process-health-check
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: launchd-process-health-check
Source: https://github.com/humanerd-drew/opencode-drewgent/tree/main/skills/brain/launchd-process-health-check
Command: npx skills add https://github.com/humanerd-drew/opencode-drewgent --skill launchd-process-health-check

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill helps diagnose and verify the health of launchd services, detecting stale exit codes and ensuring that services are actually running as expected.

Core Features & Use Cases

  • Detect Stale Exit Codes: Identifies and verifies services with stale exit codes, ensuring they are still running.
  • Service Verification: Uses multiple commands to confirm the actual running status of a service.
  • Exit Code Analysis: Provides explanations and fixes for common exit code issues.
  • Use Case: If launchctl list shows a service with an exit code of -15 but the service is actually running, this Skill can help determine if the service needs to be restarted or if the exit code is just stale.

Quick Start

To check the health of the 'cron-runner' service, use the command: launchd-process-health-check cron-runner

Frequently Asked Questions about launchd-process-health-check

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

FAQPage Schema
How do I check launchd service health when launchctl list shows a stale exit code?

A stale exit code in launchd occurs when launchctl list shows a non-zero status for a service that is still actively running. The Skill verifies actual process health using ps commands to prevent unnecessary service restarts.

Why does launchctl list show an exit code of -15 but the service is still running?

An exit code like -15 in launchctl can remain stale if the process was signaled but respawned. The Skill detects this by verifying the actual running status against multiple system commands to determine if intervention is required.

How do I verify if a launchd-managed process is actually running on macOS?

You can verify a launchd-managed process by running the health check with the service name. It analyzes exit codes and uses shell commands to confirm the operational status of macOS launchd services.

Do I need shell access to diagnose launchd exit codes on macOS?

Yes, you need shell access to the macOS system and familiarity with launchctl and ps commands. The Skill relies on these commands to diagnose launchd service health and explain stale exit codes.

What is the best way to fix common launchd exit code issues?

The best way to fix launchd exit code issues is to run the health check to get specific explanations for the codes. It identifies stale codes and determines whether a service restart is actually necessary.