Stats
Actions
Tags
How this skill is triggered — by the user, by Claude, or both
Slash command
/muxrun:debug-logsThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Fetch logs from a running muxrun application and analyze them for errors or unexpected behavior.
Fetch logs from a running muxrun application and analyze them for errors or unexpected behavior.
Run muxrun ps to discover which groups and apps are currently running, and to identify the exact group and app names.
If the user has not specified which app to debug, ask them which app they want to investigate, referencing the names found in step 1.
Fetch logs with a line limit to avoid flooding the context:
muxrun logs <group> <app> | tail -n 50
Adjust the line count based on context — use fewer lines (20–30) for a quick check, more (100+) if the user reports an issue that may have occurred earlier.
If the logs alone are insufficient, read muxrun.toml to understand the app's configuration (command, working directory, watch settings) and use that context when analyzing.
Analyze the logs and report:
watch is enabled)If the issue is not clear from a single fetch, iterate: fetch more lines, check a different app, or suggest the user reproduce the issue and fetch again.
npx claudepluginhub tkuramot/muxrun --plugin muxrunDebugs failed Render deployments by analyzing logs, metrics, and database state. Identifies errors like missing env vars, port binding, OOM and suggests fixes for service crashes, health check failures, or performance issues.
Views Zeabur service runtime and build logs to debug deployment failures, errors, or runtime issues. Supports filtering, watching, and targeting specific deployments.
References local log file locations (Flask, MCP) and commands for debugging a Python-based project. Provides quick tail, grep, and watch patterns for error tracing and server restart guidance.