/plugadvpl:sx-status

Report row counts per SX table from the local SQLite index.

Updated Aug 27, 2026

Search Tags:#sqlite #fts5 #advpl #tlpp #ingestion validation #sx dictionary #index diagnostics

Ready to run

npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-sx-status

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: /plugadvpl:sx-status
Source: https://github.com/JoniPraia/plugadvpl/tree/main/skills/sx-status
Command: npx skills add https://github.com/JoniPraia/plugadvpl --skill plugadvpl-sx-status

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly confirm whether the SX dictionary CSVs were ingested correctly by showing per-table row counts, preventing silent indexing problems from going unnoticed.

Core Features & Use Cases

Per-table ingestion counters: Reports row counts for SX2, SX3, SIX, SX7, SX6, SX1, SX5, SX9, SXA, SXB, and SXG.
Post-ingest sanity check: Useful right after running the indexing pipeline for SX data to catch missing or unexpectedly small CSVs.
Next-step guidance: If nothing was ingested yet, it suggests running the appropriate ingestion step.

Quick Start

Run sx-status after ingesting your SX CSVs to confirm each dictionary table has a reasonable number of rows.

Frequently Asked Questions about /plugadvpl:sx-status

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

FAQPage Schema

How do I verify SX dictionary ingestion counts in SQLite after loading ADVPL CSVs?▼

To verify SX dictionary ingestion, you can check row counts per SX table to confirm your ADVPL CSVs were loaded into the SQLite index correctly. This prevents silent indexing problems by reporting rows for tables like SX2, SX3, and SIX.

What is the best way to check if my SX dictionary data is missing from the local SQLite index?▼

Checking for missing SX dictionary data involves reading the index metadata and producing a summary line per SX table. If ingestion has not occurred, it explicitly indicates when sx_ingerido is false so you know to run the ingestion step.

When do I need to run an ingestion validation check for SX tables?▼

You need to run an ingestion validation check immediately after your SX data indexing pipeline completes and before downstream analysis. This post-ingest sanity check catches missing or unexpectedly small CSV files early.

Can I use this to troubleshoot ADVPL or TLPP index diagnostics before running impact analysis?▼

Yes, this applies directly to troubleshooting and verification workflows before downstream impact or doctor diagnostics. It validates that ADVPL and TLPP indexes were ingested into the local SQLite index by reporting row counts.

Why does my SQLite FTS5 index show zero rows for SX dictionary tables after loading?▼

Your SQLite FTS5 index shows zero rows because the SX dictionary CSVs were not ingested yet. The status check indicates sx_ingerido is false and suggests running the appropriate ingestion step to populate the tables.

Does the SX status check support all standard ADVPL dictionary tables like SX5 and SX9?▼

Yes, the SX status check supports standard ADVPL dictionary tables by reporting per-table ingestion counters. It covers SX2, SX3, SIX, SX7, SX6, SX1, SX5, SX9, SXA, SXB, and SXG.