thor-db

Analyzes ThorDB timing data to identify slow rules, modules, and scan elements via Python sqlite3 queries and CLI outputs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

THOR relies on an internal SQLite database (thor10.db/thor11.db) to store timing telemetry, resume markers, and delta data. This Skill provides guided analysis to help engineers diagnose slow scans, optimize rule processing, and understand how THOR tracked activities during scans.

Core Features & Use Cases

  • Inspect timing data (times) to identify long-running rules or modules.
  • Evaluate resume markers and delta data to understand interruption points and improvements across runs.
  • Use the included Python scripts to export, summarize, and spot hotspots for targeted tuning.

Quick Start

Run thor_db_top_times.py on thor10.db or thor11.db to identify hotspots and review the slow rules with thor_db_slow_rules_hint.py.

Frequently Asked Questions about thor-db

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

FAQPage Schema
How do I analyze THOR SQLite database timing data to identify slow rules?

Analyze THOR SQLite database timing data by running Python scripts like thor_db_top_times.py on thor10.db or thor11.db to query the times table and identify long-running rules or modules. This pinpoints slow scan elements for targeted optimization.

What is the best way to diagnose slow THOR scans and optimize rule processing?

Diagnose slow THOR scans by inspecting timing telemetry stored in the internal SQLite database. Use thor_db_slow_rules_hint.py to review slow rules and export summaries, enabling you to optimize rule processing and debug performance hotspots effectively.

How do I evaluate resume markers and delta data in thor10.db or thor11.db?

Evaluate resume markers and delta data in thor10.db or thor11.db by querying the stats and tbl tables via Python's sqlite3 interface. This reveals interruption points and highlights improvements across multiple THOR scan runs.

Do I need any external dependencies to query ThorDB for performance diagnostics?

No external dependencies are required to query ThorDB for performance diagnostics. The Skill relies solely on Python's built-in sqlite3 interface to access thor10.db and thor11.db, exposing timing and stats results via CLI-friendly outputs.

Can I compare THOR performance telemetry across different scan runs?

Compare THOR performance telemetry across different scan runs by analyzing delta data stored in the SQLite database. The Skill evaluates resume markers and timing stats to show improvements and interruptions between thor10.db and thor11.db sessions.

What are the limitations of analyzing THOR timing data with this approach?

Limitations of analyzing THOR timing data include its strict scope of thor10.db and thor11.db files. It focuses on performance, resume state, and delta comparisons, meaning it cannot diagnose external system latency or network-related scan delays outside the SQLite telemetry.