Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Raw1mage/patentmcpnpx agentmods add skills/raw1mage/patentmcp/troubleshooting-assistantWrote 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/raw1mage/patentmcp/troubleshooting-assistant)<a href="https://agentmods.dev/skills/raw1mage/patentmcp/troubleshooting-assistant"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/troubleshooting-assistant/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/raw1mage/patentmcp/troubleshooting-assistant"><img src="https://agentmods.dev/badge/skills/raw1mage/patentmcp/troubleshooting-assistant.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.00037 | $0.01059 |
| Opus 5 | $0.00018 | $0.00530 |
| Sonnet 5 | $0.00007 | $0.00212 |
| Haiku 4.5 | $0.00004 | $0.00106 |
Grade A, and why
troubleshooting-assistant 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 8d 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.
This is a copy
100% identical to troubleshooting-assistant — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
Troubleshooting Assistant Skill
Expert diagnostic system for identifying and resolving Claude Patent Creator issues.
When to Use
System not working, error messages, slow performance, MCP server not loading, search returns no results/errors, GPU not detected, BigQuery auth fails, index build fails, tests failing, unexpected behavior.
Troubleshooting Methodology
Problem Reported
|
[1] Gather Information (errors, recent changes, system state)
|
[2] Reproduce Issue (minimal test case, consistent?)
|
[3] Isolate Component (which part failing? dependencies?)
|
[4] Diagnose Root Cause (check logs, test components, verify config)
|
[5] Apply Fix (targeted solution, verify works)
|
[6] Prevent Recurrence (document, add monitoring, update checks)
Common Issues & Quick Fixes
| Issue | Quick Fix |
|---|---|
| MCP server not loading | claude mcp list -> Re-register if missing |
| GPU not detected | Reinstall PyTorch with CUDA |
| BigQuery auth fails | gcloud auth application-default login |
| Index not found | patent-creator rebuild-index |
| Import errors | Activate venv: venv\Scripts\activate |
| Slow searches | Check GPU usage, reduce top_k, disable HyDE |
| Irrelevant results | Rephrase query with MPEP terminology |
Detailed Issue Guides
MCP Server Issues
Problems: Server not loading, tools don't work/return errors
- 5-step diagnostic workflow
- Path verification and correction
- Dependency troubleshooting
- Server restart procedures
GPU & BigQuery Issues
Problems: GPU not detected, slow performance, BigQuery auth fails, query timeouts
- CUDA detection and PyTorch reinstallation
- Performance diagnostics and optimization
- BigQuery authentication and permissions
- Timeout configuration
Index, Dependencies & Configuration
Problems: Index not found, build fails, ModuleNotFoundError, import errors, env vars not loading, irrelevant search results
- Index rebuild procedures
- OOM (Out of Memory) solutions
- Virtual environment activation
- Pydantic validation errors
- Configuration troubleshooting
- Search quality tuning
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.
- 8d ago First seen · 160 lines · 37 tokens per session scan A bb9e25d5a054
troubleshooting-assistant is a skill published in the GitHub repository Raw1mage/patentmcp (2 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 1,059 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to troubleshooting-assistant, differing in 0 lines, and is treated as a copy.
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.