strongs-doctor

Diagnose and resolve Strong's concordance and lexicon issues in the Raamattu Nyt project.

Updated Dec 19, 2025
One-click install
npx skills add https://github.com/Spectaculous-Code/raamattu-nyt --skill strongs-doctor
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: strongs-doctor
Source: https://github.com/Spectaculous-Code/raamattu-nyt/tree/main/.claude/skills/strongs-doctor
Command: npx skills add https://github.com/Spectaculous-Code/raamattu-nyt --skill strongs-doctor

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill addresses and resolves complex issues related to Strong's concordance data within the Raamattu Nyt project, ensuring data accuracy and application performance.

Core Features & Use Cases

  • Diagnose & Fix: Identifies and corrects problems with Strong's numbers, lexicon entries, and KJV word mappings.
  • Data Validation: Validates lexicon data against authoritative sources and checks KJV verse mappings.
  • Performance Tuning: Optimizes Strong's lookup performance by checking indexes and identifying N+1 query issues.
  • Use Case: When users report that Strong's numbers are appearing incorrectly for certain KJV verses, or if the Strong's lookup feature is causing performance degradation, this Skill can be invoked to diagnose and fix the underlying data or code issues.

Quick Start

Use the strongs-doctor skill to diagnose and fix issues with Strong's concordance data.

Frequently Asked Questions about strongs-doctor

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

FAQPage Schema
How do I fix incorrect Strong's numbers appearing for KJV verses?

Fixing incorrect Strong's numbers involves diagnosing KJV verse to Strong's number mapping errors within your database. You must validate lexicon data against authoritative sources and correct corrupted data entries to ensure accurate concordance lookups.

What causes infinite loops during Strong's concordance lookups?

Infinite loops during Strong's concordance lookups are caused by corrupted data or recursive lexicon references. Diagnosing this requires analyzing specific database schema usage and SQL query patterns to identify and break the recursive cycle.

How can I optimize Strong's lookup performance and resolve N+1 query issues?

Optimize Strong's lookup performance by checking database indexes and identifying N+1 query issues. Analyzing SQL query patterns helps pinpoint performance bottlenecks so you can restructure queries and eliminate redundant database calls.

How do I validate Strong's lexicon data against authoritative sources?

Validating Strong's lexicon data requires comparing database entries against authoritative sources to ensure data integrity. This process checks KJV verse mappings and corrects discrepancies found within the concordance dataset.

What database schema and SQL patterns are needed for Strong's concordance troubleshooting?

Troubleshooting Strong's concordance issues requires adherence to specific database schema usage and SQL query patterns. Using the correct schema ensures effective data validation, accurate KJV verse mapping, and proper resolution of performance bottlenecks.

Why does my Strong's concordance data show corrupted entries?

Corrupted entries in Strong's concordance data stem from data validation failures or incorrect KJV verse to Strong's number mapping. Diagnosing the problem requires checking the database schema and validating lexicon entries against authoritative sources.