skills.rest
mkusaka
mkusakaCOMMUNITY
Explore all skills by this author →
GitHub

stuck-background-daemon-diagnostics

Diagnose stuck background daemon issues by analyzing lock, status, and log files.

7|Updated Mar 8, 2026
Search Tags:#troubleshooting#log analysis#system administration#background session#daemon diagnostics
One-click install
npx skills add https://github.com/mkusaka/ccskills --skill stuck-background-daemon-diagnostics
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: stuck-background-daemon-diagnostics
Source: https://github.com/mkusaka/ccskills/tree/main/skills/stuck-background-daemon-diagnostics
Command: npx skills add https://github.com/mkusaka/ccskills --skill stuck-background-daemon-diagnostics

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

The Skill solves the problem of diagnosing stuck background daemon issues in the /stuck skill.

Core Features & Use Cases

  • Diagnose stuck background daemon: Analyze daemon.lock and daemon.status.json to identify issues.
  • Log inspection: Review daemon logs for detailed diagnostic information.
  • Worker roster and state: Inspect live worker roster and per-job state for additional context.

Quick Start

Use the stuck-background-daemon-diagnostics skill to get diagnostics for the stuck background daemon.

Frequently Asked Questions about stuck-background-daemon-diagnostics

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

FAQPage Schema
How do I diagnose a stuck background daemon?▼

To diagnose a stuck background daemon, you need to analyze daemon.lock and daemon.status.json files alongside daemon logs to identify the operational issue. Reviewing live worker rosters and per-job state provides additional context.

What is the best way to troubleshoot production workflow daemon hang issues?▼

Troubleshooting production daemon hang issues is best handled by inspecting daemon lock and status files to detect deadlocks. Analyzing daemon log content and worker state helps pinpoint the exact cause of the background session freeze.

What files do I need to access for background session diagnostics?▼

Background session diagnostics requires access to daemon.lock and daemon.status.json files, as well as daemon log files. These files provide the lock state, status data, and log content necessary to identify the issue.

Can I inspect live worker rosters during daemon troubleshooting?▼

Yes, you can inspect live worker rosters and per-job state during daemon troubleshooting. Reviewing this live worker data alongside daemon lock and status files provides additional context to identify why the background daemon is stuck.

Why does my background daemon get stuck in production workflows?▼

Background daemons get stuck in production workflows due to lock contention or job state issues recorded in daemon.lock and daemon.status.json. Analyzing daemon logs and worker rosters reveals the specific operational blockage causing the freeze.

Related Skills

Explore More Software Engineering Skills→
ryanbreenryanbreen
7

log-analysis

Search and analyze Breenix kernel logs for errors and checkpoints.

Community
Basic
twikustwikus
3

ci-fixer

Diagnose CI/CD failures and apply verified local fixes across GitHub Actions, Vercel, and Netlify.

Community
Advanced
filipexyzfilipexyz
6

daemon-manager

Manage the Ravi runtime daemon lifecycle, service installation, and logs.

Community
Intermediate
launchapp-devlaunchapp-dev

animus-daemon-operations

Start, stop, and monitor the Animus daemon with status checks and logs.

Official
Basic