Run any Skill in Manus with one click

runtime-diagnostics

Stars1

Forks0

UpdatedApril 5, 2026 at 09:59

Debug the local media-library-manager runtime by inspecting jobs, ports, reports, state artifacts, and backend health. Use when the dashboard looks stale, API behavior differs from edited files, a job is stuck, a scan keeps timing out, or the backend needs a clean restart.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

leolionart

leolionart/media-library-manager

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

name	runtime-diagnostics
description	Debug the local media-library-manager runtime by inspecting jobs, ports, reports, state artifacts, and backend health. Use when the dashboard looks stale, API behavior differs from edited files, a job is stuck, a scan keeps timing out, or the backend needs a clean restart.

Runtime Diagnostics

Use this skill to understand what the running app is actually doing before changing code or blaming the UI.

Workflow

Inspect runtime state first. Read /api/process and /api/state. Compare live state with files under data/.
Check ports and processes. In this repo, Vite commonly runs on 127.0.0.1:5173 and the Python backend on 127.0.0.1:8766. Confirm which process is actually serving the current API.
Inspect logs and artifacts. Check current_job.logs, activity_log, and relevant saved artifacts such as last-path-repair-scan.json.
Restart cleanly when needed. Stop the Python backend, confirm the port is free, then restart with the repo's PYTHONPATH=src setup and the correct data/app-state.json.
Re-verify after restart. Confirm that the live API reflects the edited code and current state file before resuming workflow operations.

Guardrails

Distinguish between stale saved reports and live provider reality.
Do not assume Vite and the Python backend restarted together.
Prefer direct API checks over guessing from the UI.

Typical Requests

"Kiểm tra backend đang chạy code nào"
"Tại sao UI và file state không khớp"
"Restart backend sạch rồi verify lại"

More from this repository

same repository

bulk-refresh

leolionart/media-library-manager

Run controlled bulk provider path rewrites and refreshes with batching, progress checks, and failure tracking. Use when the user explicitly wants to rewrite many Radarr or Sonarr items with known paths, rerun provider refreshes in bulk, or measure whether same-path rewrites change provider behavior.

2026-04-051

duplicate-cleanup

leolionart/media-library-manager

Clean duplicate movie or series folders on connected rclone or SMB roots. Use when the user wants to scan for duplicate folders, review deletion candidates, rerun cleanup on a narrow scope such as drive/gdrive Movies or TV Series, or apply duplicate-folder deletions in safe batches.

2026-04-051

path-repair

leolionart/media-library-manager

Investigate Radarr or Sonarr path mismatches and repair only verified old-to-new path changes. Use when the user wants to search for a replacement folder for one provider item, compare old and new paths, or update provider paths after verifying the target folder really exists.

2026-04-051

remove-with-exclusion

leolionart/media-library-manager

Remove Radarr or Sonarr items without deleting media files and add import exclusion so they are not automatically re-imported. Use when the user wants to remove one provider item, remove a small batch, or verify whether an exclusion was really created.

2026-04-051

name	runtime-diagnostics
description	Debug the local media-library-manager runtime by inspecting jobs, ports, reports, state artifacts, and backend health. Use when the dashboard looks stale, API behavior differs from edited files, a job is stuck, a scan keeps timing out, or the backend needs a clean restart.

Runtime Diagnostics

Use this skill to understand what the running app is actually doing before changing code or blaming the UI.

Workflow

Inspect runtime state first. Read /api/process and /api/state. Compare live state with files under data/.
Check ports and processes. In this repo, Vite commonly runs on 127.0.0.1:5173 and the Python backend on 127.0.0.1:8766. Confirm which process is actually serving the current API.
Inspect logs and artifacts. Check current_job.logs, activity_log, and relevant saved artifacts such as last-path-repair-scan.json.
Restart cleanly when needed. Stop the Python backend, confirm the port is free, then restart with the repo's PYTHONPATH=src setup and the correct data/app-state.json.
Re-verify after restart. Confirm that the live API reflects the edited code and current state file before resuming workflow operations.

Guardrails

Distinguish between stale saved reports and live provider reality.
Do not assume Vite and the Python backend restarted together.
Prefer direct API checks over guessing from the UI.

Typical Requests

"Kiểm tra backend đang chạy code nào"
"Tại sao UI và file state không khớp"
"Restart backend sạch rồi verify lại"