Agent skill

Troubleshooting Router

Routes troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the type of problem.

AGPL-3.0Auto-check passed

Install Troubleshooting Router

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .claude/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .claude/skills/troubleshooting-router && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .claude/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .agents/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .agents/skills/troubleshooting-router && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .agents/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .cursor/skills/troubleshooting-router && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .cursor/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Hello-QM/catgo-LRG.git --path server/catgo/workflow/skills/troubleshooting

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .gemini/skills/troubleshooting-router && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .gemini/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .github/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .github/skills/troubleshooting-router && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .github/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Hello-QM/catgo-LRG troubleshooting-router --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Hello-QM/catgo-LRG.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/server/catgo/workflow/skills/troubleshooting .opencode/skills/troubleshooting-router && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "troubleshooting-router" agent skill from https://github.com/Hello-QM/catgo-LRG/tree/main/server/catgo/workflow/skills/troubleshooting into .opencode/skills/troubleshooting-router/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "troubleshooting-router", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: troubleshooting-router
GitHub stars: 205
Token cost: ~944 tokens
SKILL.md length: 307 words
Files: 1
Skills in repo: 75
Repo updated: Sep 22, 2026
First seen: Oct 7, 2026
Licence: AGPL-3.0

At a glance

Routes troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the type of problem.

Works in 3 steps: Identify the error source → Route based on error type → Gather diagnostics
SKILL.md covers When to Use, Routing Decision Tree, Common Patterns and MCP Tool Examples, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Troubleshooting Router is an agent skill from Hello-QM/catgo-LRG. Routes troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the type of problem.

Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: AI-driven workbench for computational materials science — interactive 3D structure viewer, natural-language CatBot assistant, visual DAG workflow engine, HPC job submission… The licence is AGPL-3.0.

Example prompts

“Use the troubleshooting-router skill to route troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the…”
“/troubleshooting-router”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

Identify the error source
Route based on error type
Gather diagnostics

What it can do on your machine

Read from SKILL.md and the folder at commit fd6291b. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Troubleshooting Router loads about 944 tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 307 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~38
When it runs · the whole SKILL.md, loaded when a task matches: ~944

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Hello-QM/catgo-LRG at commit fd6291b, republished under its AGPL-3.0 licence (© Hello-QM). 307 words, ~944 tokens.

Download SKILL.mdSave it as .claude/skills/troubleshooting-router/SKILL.md (or your agent's skills folder).

name: troubleshooting-router
description: Routes troubleshooting requests to vasp_errors, convergence_issues, or workflow_errors sub-skills based on the type of problem.

Troubleshooting Router Skill

When to Use

Use this skill when the user reports a problem with a calculation or workflow. Route to the appropriate sub-skill based on the error type.

Routing Decision Tree

Step 1: Identify the error source

Ask the user or check the workflow status:

json

catgo_workflow_engine(action: "status", params: { workflow_id: "<wf_id>" })

If a specific task failed, get the error details:

json

catgo_workflow_engine(action: "get_result", params: {
  workflow_id: "<wf_id>",
  task_id: "<task_id>"
})

Step 2: Route based on error type

Error signature	Route to
VASP error messages (ZBRENT, BRMIX, EDDDAV, etc.)	`troubleshooting/vasp_errors`
SCF not converging, ionic relaxation oscillating	`troubleshooting/convergence_issues`
ORCA SCF/geometry convergence	`troubleshooting/convergence_issues`
CatGo engine errors (REMOTE_ERROR, stuck tasks)	`troubleshooting/workflow_errors`
HPC connection issues (SSH, SFTP)	`troubleshooting/workflow_errors`
POTCAR not found, missing files	`troubleshooting/workflow_errors`
Test/verify cluster config before submitting; POTCAR/pseudopotential/binary/module checks; job "completed" with no output	`troubleshooting/cluster_config_test`

Step 3: Gather diagnostics

Before routing, collect relevant information:

json

catgo_workflow_engine(action: "status", params: { workflow_id: "<wf_id>" })

For VASP/convergence issues, check the calculation output:

json

catgo_analyze(action: "convergence", params: {
  workflow_id: "<wf_id>",
  task_id: "<task_id>"
})

For system-level issues:

json

catgo_system(action: "status")

json

catgo_system(action: "errors")

Common Patterns

"My calculation failed"

Check workflow status to identify which task failed
Get the error message from the failed task
Route to the appropriate sub-skill

"My calculation is taking too long"

Check if it is still running or stuck
If running: check convergence progress -> convergence_issues
If stuck in READY/QUEUED: -> workflow_errors

"My results look wrong"

Check if the calculation converged
Check for warnings in the output
Often a convergence issue in disguise -> convergence_issues

"I cannot connect to the HPC"

Direct to workflow_errors for SSH/connection troubleshooting.

MCP Tool Examples

Full diagnostic sequence

Get workflow overview:

json

catgo_workflow_engine(action: "status", params: { workflow_id: "<wf_id>" })

Get failed task details:

json

catgo_workflow_engine(action: "get_result", params: {
  workflow_id: "<wf_id>",
  task_id: "<failed_task_id>"
})

Check convergence if applicable:

json

catgo_analyze(action: "convergence", params: {
  workflow_id: "<wf_id>",
  task_id: "<task_id>"
})

Check system health:

json

catgo_system(action: "status")

Based on findings, route to the appropriate sub-skill and apply fixes.

Quick retry after fixing parameters

json

catgo_workflow_engine(action: "modify_params", params: {
  workflow_id: "<wf_id>",
  task_id: "<task_id>",
  params: { "ALGO": "All", "NELM": 200 }
})

json

catgo_workflow_engine(action: "retry", params: {
  workflow_id: "<wf_id>",
  task_id: "<task_id>"
})

Key Principle

Always diagnose before prescribing. Do not blindly suggest parameter changes without first understanding what went wrong. Use the diagnostic tools (status, get_result, convergence analysis) to identify the root cause, then apply targeted fixes.

Files

Just SKILL.md in server/catgo/workflow/skills/troubleshooting of Hello-QM/catgo-LRG.

Open the folder on GitHubat commit fd6291b

Compare with similar skills

Troubleshooting Router next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Troubleshooting Router compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Troubleshooting Router this skillHello-QM/catgo-LRG	205	—	~944	Automated safety check: Pass	AGPL-3.0	17 days ago
Router Onweave-os/router	5.6k	—	~169	Automated safety check: Pass	Apache-2.0	today
Acp Routeropenclaw/openclaw	392k	—	~2.4k	Automated safety check: Pass	MIT	today
Router Offweave-os/router	5.6k	—	~183	Automated safety check: Pass	Apache-2.0	today
OmniRoute Routing CLIdiegosouzapw/OmniRoute	75k	—	~342	Automated safety check: Pass	MIT	today
OmniRoute Combo Routingdiegosouzapw/OmniRoute	75k	—	~2.1k	Automated safety check: Pass	MIT	today

Similar skills

Router On
weave-os/router
Route Codex through the Weave Router again (turn it back on).
5.6k GitHub stars~169 tokensUpdated today
Auto-check passed
Acp Router
openclaw/openclaw
Route plain-language requests for Claude Code, Cursor, Copilot, OpenClaw ACP, OpenCode, Gemini CLI, Qwen, Kiro, Kimi, iFlow, Factory Droid, Kilocode, or explicit ACP harness work into either…
392k GitHub stars~2.4k tokensUpdated today
Writing & ContentAuto-check passed
Router Off
weave-os/router
Route Codex to its default provider again (turn the Weave Router off).
5.6k GitHub stars~183 tokensUpdated today
Auto-check passed
OmniRoute Routing CLI
diegosouzapw/OmniRoute
Creates, switches, and inspects OmniRoute model-routing combos, plus a suggestion command with cost and latency constraints.
75k GitHub stars~342 tokensUpdated today
AI & LLM EngineeringAuto-check passed
OmniRoute Combo Routing
diegosouzapw/OmniRoute
Manages OmniRoute routing combos through its REST API: create and update combos, choose from 19 strategies, set fallback chains, test outcomes and read metrics.
75k GitHub stars~2.1k tokensUpdated today
Backend & APIsAuto-check passed
SPA Routes and Features
lobehub/lobehub
Explains LobeHub's split between src/routes page segments and src/features domain code, and where router config, redirects and platform adapters belong.
83k GitHub stars~3.2k tokensUpdated today
Frontend & DesignAuto-check passed

Questions about Troubleshooting Router

What does Troubleshooting Router do?

Routes troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the type of problem. Troubleshooting Router is an agent skill from Hello-QM/catgo-LRG. Routes troubleshooting requests to vasperrors, convergenceissues, or workflowerrors sub-skills based on the type of problem.

How do I install Troubleshooting Router in Claude Code?

Run `npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a claude-code`. Or copy the skill folder (server/catgo/workflow/skills/troubleshooting in Hello-QM/catgo-LRG) into .claude/skills/troubleshooting-router in your project. Claude Code loads it when a task matches its description.

How do I install Troubleshooting Router in Codex?

Run `npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a codex`. Or copy the skill folder (server/catgo/workflow/skills/troubleshooting in Hello-QM/catgo-LRG) into .agents/skills/troubleshooting-router in your project. Codex loads it when a task matches its description.

Can I use Troubleshooting Router in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Hello-QM/catgo-LRG --skill troubleshooting-router -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/troubleshooting-router, .gemini/skills/troubleshooting-router, .github/skills/troubleshooting-router and .opencode/skills/troubleshooting-router in your project.

What does Troubleshooting Router need to run?

SKILL.md names no scripts, command-line tools or credentials: Troubleshooting Router is instructions for the agent only.

Does Troubleshooting Router access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Troubleshooting Router safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Troubleshooting Router use?

Troubleshooting Router is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Troubleshooting Router use?

About 944 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Troubleshooting Router?

Skills that share tags, products or a category with Troubleshooting Router: Router On (weave-os/router, 5.6k stars), Acp Router (openclaw/openclaw, 392k stars), Router Off (weave-os/router, 5.6k stars) and OmniRoute Routing CLI (diegosouzapw/OmniRoute, 75k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Troubleshooting Router?

Hello-QM (a GitHub user) maintains it in Hello-QM/catgo-LRG, which has 205 GitHub stars. The repository holds 75 skills in this directory. The repository was last updated on September 22, 2026.

Source: Hello-QM/catgo-LRG on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Troubleshooting Router

Facts

At a glance

What it does

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Troubleshooting Router Skill

When to Use

Routing Decision Tree

Step 1: Identify the error source

Step 2: Route based on error type

Step 3: Gather diagnostics

Common Patterns

"My calculation failed"

"My calculation is taking too long"

"My results look wrong"

"I cannot connect to the HPC"

MCP Tool Examples

Full diagnostic sequence

Quick retry after fixing parameters

Key Principle

Files

Compare with similar skills

Similar skills

More from Hello-QM/catgo-LRG

Questions about Troubleshooting Router