thor-db

Analyze ThorDB timing data to identify performance bottlenecks in THOR scans.

12|2|Updated Jan 17, 2026

Search Tags:#analysis #sqlite #timing #tuning #thor #scans #thordb

Ready to run

npx skills add https://github.com/NextronSystems/thor-skill --skill thor-db

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: thor-db
Source: https://github.com/NextronSystems/thor-skill/tree/main/thor-db
Command: npx skills add https://github.com/NextronSystems/thor-skill --skill thor-db

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

THOR's performance data is scattered across multiple scans and requires a consolidated view to diagnose slow scans, performance regressions, and resume behavior.

Core Features & Use Cases

Performance telemetry – Timing data for rules, modules, and scan elements.
Resume state visibility – Markers to continue interrupted scans and understand resume points.
Delta comparisons – Compare current vs previous results to identify changes between runs.
Exporting & reporting – Export times, stats, and metadata to CSV/JSON for analysis.
Use Case: Investigate a slow THOR scan by identifying top time sinks and validating resume state.

Quick Start

Run the ThorDB scripts to export timing data from thor10.db or thor11.db and review the top time sinks.

Frequently Asked Questions about thor-db

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

FAQPage Schema

How do I identify performance bottlenecks in a slow THOR scan?▼

To identify performance bottlenecks in a slow THOR scan, analyze the timing data and stats stored in ThorDB. This isolates top time sinks across deep_scan and bulk_scan operations to guide tuning.

How do I export THOR scan timing data to CSV or JSON for analysis?▼

You can export THOR scan timing data to CSV or JSON by running scripts against the thor10.db or thor11.db SQLite databases. This extracts times, stats, and metadata for external analysis and reporting.

What is the best way to compare timing data between different THOR scan runs?▼

The best way to compare timing data between THOR scan runs is to perform delta comparisons on the exported ThorDB metrics. This highlights performance regressions and changes between current and previous scan executions.

Can I check the resume state and markers of an interrupted THOR scan?▼

Yes, you can check the resume state of an interrupted THOR scan by querying the ThorDB tables. This provides visibility into resume markers and metrics to help understand where the scan was halted.

Does THOR scan tuning require access to specific database files?▼

Yes, THOR scan tuning requires access to the SQLite database files thor10.db or thor11.db. These databases contain the essential timing data, stats, and resume state needed to diagnose performance issues.