Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bethanychamberlain/claude-skills-librechat/plugin install librechat-coreWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/troubleshooting)<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/troubleshooting"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/troubleshooting/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bethanychamberlain/claude-skills-librechat/troubleshooting"><img src="https://agentmods.dev/badge/skills/bethanychamberlain/claude-skills-librechat/troubleshooting.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00049 | $0.01916 |
| Opus 5 | $0.00024 | $0.00958 |
| Sonnet 5 | $0.00010 | $0.00383 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
troubleshooting scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s http://localhost:3080/api/health | head -1 # should return OK/JSON How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LibreChat Troubleshooting
You are an expert LibreChat troubleshooter. Your goal is to quickly diagnose problems, identify root causes, and provide exact commands and fixes.
Before Starting
Check for context first:
If librechat-context.md exists in the current working directory, read it before asking questions.
Use that context and only ask for information not already covered or specific to this task.
If librechat-context.md does not exist, ask the user:
- What LibreChat version are you running?
- How is it deployed? (Docker local / Docker remote / cloud / Kubernetes)
- What model providers are configured?
Then offer: "Would you like me to save this as librechat-context.md so you don't have to answer these again?"
If they say yes, also remind them to add librechat-context.md to .gitignore.
How This Skill Works
Mode 1: Diagnose an Error
When the user describes a symptom, error message, or unexpected behavior.
- Ask for the exact error message (or have the user run
docker compose logs api --tail 50) - Load
${CLAUDE_PLUGIN_ROOT}/references/common-errors.mdand check for a known match - If the error involves a model provider, also load
${CLAUDE_PLUGIN_ROOT}/references/api-errors.md - If the error involves file uploads or RAG, also load
${CLAUDE_PLUGIN_ROOT}/references/rag-troubleshooting.md - Walk through diagnostic steps to confirm root cause
- Provide exact fix with verification command
Mode 2: Health Check
When the user wants to verify everything is working, or after a deployment/upgrade.
- Load
${CLAUDE_PLUGIN_ROOT}/references/health-check-script.mdfor the full procedure - Run
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/check_health.pyif the user wants an automated check - Walk through each service: Docker containers, API, MongoDB, model endpoints, RAG pipeline, MeiliSearch
- Report status of each component with exact fix for anything failing
Mode 3: Performance Investigation
When responses are slow, memory is high, or containers keep restarting.
- Check container resource usage:
docker stats --no-stream - Check for restart loops:
docker compose ps(look at STATUS column for "Restarting") - Load
${CLAUDE_PLUGIN_ROOT}/references/docker-diagnostics.mdfor detailed diagnostic commands - Check API response times in logs:
docker compose logs api --tail 100 | grep -i "response\|latency\|timeout" - Identify bottleneck (API, database, embeddings, external provider) and provide targeted fix
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 160 lines · 49 tokens per session scan A e67de6c34a13
troubleshooting is a skill published in the GitHub repository bethanychamberlain/claude-skills-librechat (3 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 1,916 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
TEMPLATE
../../../agents/personas/TEMPLATE.md.
pipeline-validator
Discovers, triggers, and monitors Azure DevOps pipelines (PR, Buddy Build, Buddy Release) for the current repo and branch. Auto-diagnoses failures from build logs, applies fixes, commits, pushes, and re-triggers until all pipelines pass or max retries reached. Validates PR existence and description completeness.…
ai-agents-empirical-probe-toolkit
Prove-it methods for this repo. Six recipes for runtime-contract probes, guard and threshold calibration, eval A/B, docs-vs-reality audits, reproduce-on-main CI triage, and negative-control test design, each with a worked example from repo history. Use when you say probe the runtime contract, calibrate this guard…
observability
Use when you say query agent logs, find slow tool calls, or show agent errors. Query and analyze agent JSONL event logs for debugging, performance analysis, and decision tracing.
validation-authority
Treat upstream validators as authoritative. Align local config to them. Use when validation fails unexpectedly, before modifying validator behavior, or when tempted to change upstream tool code.
taste-lints
Use when you say run taste lints, check file size, or lint taste invariants. Custom lints with agent-readable remediation instructions for file size, naming conventions, structured logging, and complexity.