菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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.
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.
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.
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.
| 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. |
Use this skill to understand what the running app is actually doing before changing code or blaming the UI.
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.
