Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add yale-som-hpc/claude-code-marketplace --skill troubleshootinggit clone --depth 1 https://github.com/yale-som-hpc/claude-code-marketplaceWrote 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/yale-som-hpc/claude-code-marketplace/troubleshooting)<a href="https://agentmods.dev/skills/yale-som-hpc/claude-code-marketplace/troubleshooting"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/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/yale-som-hpc/claude-code-marketplace/troubleshooting"><img src="https://agentmods.dev/badge/skills/yale-som-hpc/claude-code-marketplace/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.00081 | $0.01424 |
| Opus 5 | $0.00041 | $0.00712 |
| Sonnet 5 | $0.00016 | $0.00285 |
| Haiku 4.5 | $0.00008 | $0.00142 |
Grade A, and why
troubleshooting scanned grade A with 0 findings 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 11d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Troubleshooting
Rule: read the actual error (and the pending reason), match it below, apply the fix. Don't guess from symptoms — squeue --me -o "%T %r", the job's .out/.log, and seff JOBID almost always name the cause.
Quick triage
| Symptom / error | Likely cause | Fix |
|---|---|---|
Job stuck PENDING for ages, cluster looks idle |
Targeted partition's nodes are full or reserved for a higher-priority partition (the CPU partitions overlap on shared nodes). | squeue --me -o "%T %r" to read the reason; sinfo -o "%R %C" for idle cores; resubmit to a partition with capacity (often gpunormal for CPU work). See managing-jobs. |
| Job killed near a round time (e.g. exactly 4h) | Hit the partition time limit — default_queue caps at 4h. |
Move long work to cpunormal/gpunormal (no time limit), or split into resumable chunks. |
Out Of Memory / job killed, seff shows high memory |
--mem too low. |
Check seff JOBID (MaxRSS is on the .batch row); set --mem to ~1.5–2× observed peak. See self-diagnosing-resource-use. |
./tool: ... version 'GLIBC_2.xx' not found |
Prebuilt binary needs a newer glibc than the cluster has. | Use a musl/static build, a module, or Apptainer; or compile on the cluster. See installing-software. |
R: there is no package called 'X' |
The base R module ships no add-on packages. | Bootstrap a project library first: install.packages("renv") then renv::init()/renv::install(...) on the login node. See running-r. |
Python: ModuleNotFoundError inside a job |
Job ran the wrong interpreter, or env not synced. | Launch with srun .venv/bin/python ...; run uv sync --frozen on the login node (never inside the job). See running-python. |
Stata: Slurm .out is empty / "where's my output?" |
stata-mp -b writes its own .log, not stdout. |
Read the do-file's .log (and the stray main.log Stata drops in the working dir), not the .out. See running-stata. |
sbatch fails: bad interpreter, : not found, or $'\r' |
CRLF line endings (edited on Windows). | dos2unix job.sh or sed -i 's/\r$//' job.sh; set your editor to LF for .sh. |
nvidia-smi: command not found or it errors |
You're on a login node (no GPU driver), or no GPU was allocated. | Run inside a GPU allocation (--gres=gpu:1); see using-gpus. |
git: command not found (or other tool) |
Tool isn't on the default PATH. | module spider <tool> then module load; for user tools install into ~/.local/bin. git in particular needs module load git. |
Python forkserver job hangs at startup, 0% CPU |
forkserver deadlocks under srun .venv/bin/python. |
Use fork (CPU work) or spawn (CUDA/threads). See parallel-python. |
seff reports CPU Utilized: 00:00:00 on a job that worked |
seff samples coarsely; sub-minute jobs read as 0. | Ignore CPU-efficiency on jobs under ~1–2 minutes; trust it only on longer jobs. |
| Heavy work slow / login node sluggish for everyone | Ran compute on the login node. | Login nodes are for editing/submitting only — put compute in sbatch/srun. See overview. |
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.
- 11d ago First seen · 49 lines · 81 tokens per session scan A f96e2238c2b5
troubleshooting is a skill published in the GitHub repository yale-som-hpc/claude-code-marketplace (5 stars, last pushed 2mo ago), licensed Unlicense. It adds 81 tokens to every session and 1,424 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.