thor-troubleshooting

Diagnose THOR run failures and provide ranked causes with next steps.

12|2|Updated Jan 17, 2026
One-click install
npx skills add https://github.com/NextronSystems/thor-skill --skill thor-troubleshooting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: thor-troubleshooting
Source: https://github.com/NextronSystems/thor-skill/tree/main/thor-troubleshooting
Command: npx skills add https://github.com/NextronSystems/thor-skill --skill thor-troubleshooting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Troubleshoot THOR runs that are stuck, slow, failing to start, stopping early, or producing missing output, helping operators quickly identify root causes and decide minimal next steps.

Core Features & Use Cases

  • Structured, step-by-step triage for THOR issues including freezes, long runtimes, and abrupt terminations.
  • Provides a prioritized list of probable causes, actionable next commands, and evidence collection guidance to hand to incident responders.
  • Leverages built-in references and optional helper scripts to gather diagnostics without disrupting ongoing scans.

Quick Start

Describe the THOR symptom in detail and run thor-util diagnostics to generate a prioritized fix plan.

Frequently Asked Questions about thor-troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my THOR scan freeze or run for an unusually long time?

THOR scans freezing or running long often stem from AV/EDR interference, memory pressure, or timeout limits. This Skill diagnoses these specific issues by returning a ranked list of probable causes and actionable next commands.

How do I troubleshoot a THOR run that terminates unexpectedly?

To troubleshoot unexpected THOR terminations, describe the symptom in detail and run thor-util diagnostics. This generates a prioritized fix plan covering Windows and Linux failures, including licensing issues.

What is the best way to collect forensic evidence when a THOR scan fails?

The best way to collect forensic evidence for failed THOR scans is using the Skill's built-in references and optional helper scripts. These gather diagnostics without disrupting ongoing scans, providing steps to reproduce and escalate.

Does this diagnostics tool work for THOR failures on both Windows and Linux?

Yes, this diagnostics tool works for THOR failures on both Windows and Linux. It applies structured triage to scans that fail to start, stop early, or produce missing output across both operating systems.

What should I do when THOR is producing missing output files?

When THOR produces missing output, use this Skill to identify root causes and minimal next steps. It provides a structured, step-by-step triage to pinpoint why output is missing and recommends commands to fix it.