agentsclimarketplace

Plex diagnostic expert

Skill Lunatic16/LLM-Skills-Collection/plex-diagnostic-expert

A collection of specialized skills for Gemini CLI to enhance its capabilities in Fedora technical support, financial analysis, and Plex media server diagnostics.

Install
npx -y skills add Lunatic16/LLM-Skills-Collection --skill plex-diagnostic-expert

Assembled 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.

What its author says it does

Copied from the file, not written here

Troubleshooting Plex Media Server playback, instability, and library issues by analyzing server logs and environment metadata.

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:

  1. Overall Grade: (A to F).
  2. Physician's Summary: A metaphor-rich summary of the server's health.
  3. 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).

Gives 0 of the 12 instructions most debug triage skills give in 392 tokens

Counted across 839 of the 1,149 authors here whose files we hold, read 2026-08-06

  • investigate root cause before proposing any fixin 102 of 839, across 65 files
  • read error messages completelyin 90 of 839, across 48 files
  • create a failing test case before fixingin 84 of 839, across 44 files
  • reproduce the issue consistentlyin 82 of 839, across 40 files
  • change one variable at a timein 82 of 839, across 42 files
  • check recent changesin 74 of 839, across 35 files
  • write the regression test before fixingin 74 of 839, across 36 files
  • fix the root cause not the symptomin 60 of 839, across 43 files
  • implement a single fix at a timein 59 of 839, across 20 files
  • trace data flow backward to the sourcein 50 of 839, across 20 files
  • remove all debug instrumentationin 49 of 839, across 13 files
  • form a single hypothesisin 48 of 839, across 18 files

Said here and by no other author read

  • Request the last 100-200 lines of the main log
  • Check transcoding speed values for bottlenecks
  • Analyze remote connectivity test failures and NAT issues
  • Assign an overall grade from A to F
  • Write a metaphor-rich summary of server health
  • Provide exactly three numbered steps to resolve the issue

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.