Plex diagnostic expert
Skill Lunatic16/LLM-Skills-Collection/plex-diagnostic-expert
Troubleshooting Plex Media Server playback, instability, and library issues by analyzing server logs and environment metadata.From its SKILL.md
npx -y skills add Lunatic16/LLM-Skills-Collection --skill plex-diagnostic-expertAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.8 KB, 392 tokens by cl100k_base, as published. Nobody here has run it
Plex Diagnostic Expert
Guidance for diagnosing and fixing Plex Media Server issues. Follow a structured "checkup" approach to identify root causes in core stability, transcoding, scanning, or networking.
Diagnostic Workflow
1. Environment Discovery
Identify the platform and the primary symptoms.
- Platform: Windows, Mac, Linux, Docker/Unraid, Synology, etc.
- Issue: Buffering, "Server unavailable", "Files not appearing", "Remote access down".
2. Log Retrieval
Guide the user to find their Plex Media Server.log.
- Refer to platform-guide.md for OS-specific paths.
- Request the last 100-200 lines of the main log file.
3. The Diagnostic Checkup
Analyze provided logs for "Vital Signs". Refer to log-analysis.md for specific string patterns.
- Heartbeat (Core Stability): Check for database corruption or critical system errors.
- Circulation (Transcoding): Look for
Speed =>values.> 1.0: Healthy transcoding.< 1.0: Hardware/resource bottleneck.
- Vision (Scanner/Library): Check for processing directory errors or permission issues.
- Remote Connection: Analyze connectivity test failures and NAT issues.
4. The Doctor's Report
Present findings clearly:
- Overall Grade: (A to F).
- Physician's Summary: A metaphor-rich summary of the server's health.
- Prescription: Exactly 3 clear, numbered steps to resolve the primary issue.
Emergency Protocol
If logs are unavailable or the user is overwhelmed, suggest "Home Remedies":
- Restart the server.
- Force "Analyze" on specific files.
- Check disk space (common cause of database errors).
What ships with it: 4 files
2.3 KB alongside SKILL.md
assets/
- .gitkeep0 B
references/
- log-analysis.md1.3 KB
- platform-guide.md981 B
scripts/
- .gitkeep0 B