post-indexing-analysis

Detect failures and anomalies in post-indexing runs for vector collections and knowledge graphs.

Updated Mar 29, 2026
One-click install
npx skills add https://github.com/Alex1980Alex/1C-Framework --skill post-indexing-analysis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: post-indexing-analysis
Source: https://github.com/Alex1980Alex/1C-Framework/tree/main/.claude/skills/post-indexing-analysis
Command: npx skills add https://github.com/Alex1980Alex/1C-Framework --skill post-indexing-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

It automates post-run diagnostics for indexing and graph-building workflows, helping you quickly understand whether a run completed correctly, drifted in quality, or produced broken graph and vector data.

Core Features & Use Cases

  • Indexing Run Review: Summarize the latest indexing execution, including stages, timing, run-end status, and collection state.
  • Vector Quality Checks: Detect dimension mismatches, norm drift, zero vectors, and self-recall problems in Qdrant collections.
  • Graph Integrity Analysis: Inspect SQLite call graphs, Neo4j structures, and graph_embeddings for orphan nodes, dangling calls, and relationship imbalances.
  • Use Case: After a long ingestion job, use this Skill to generate a report that explains whether the collection is healthy, whether the graph is consistent, and where anomalies need attention.

Quick Start

Ask the skill to analyze the latest indexing run and produce a report for the relevant collection or graph source.

Frequently Asked Questions about post-indexing-analysis

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

FAQPage Schema
How do I detect vector norm drift and dimension mismatches after a Qdrant ingestion job?

To detect vector norm drift and dimension mismatches after a Qdrant ingestion job, run automated post-indexing diagnostics that verify run-end state, dimensional consistency, and zero vectors to ensure collection health.

What is post-indexing analysis for knowledge graphs and vector collections?

Post-indexing analysis is the process of verifying run-end state, timing, and data consistency after automated ingestion jobs to detect failures, norm drift, orphan nodes, and dangling relationships in vector collections and knowledge graphs.

How do I check a Neo4j graph for orphan nodes and dangling relationships after data ingestion?

To check a Neo4j graph for orphan nodes and dangling relationships after data ingestion, apply graph integrity analysis scripts that inspect structural imbalances, verify dimensional consistency, and report broken graph data.

Does post-indexing diagnostics work with SQLite call graphs and graph_embeddings?

Yes, post-indexing diagnostics work with SQLite call graphs and graph_embeddings, inspecting these structures for orphan nodes, dangling calls, and relationship imbalances to verify overall graph integrity after ingestion.

Why does my vector collection have self-recall problems after an automated ingestion run?

Vector collections experience self-recall problems after an automated ingestion run due to norm drift, zero vectors, or dimensional mismatches, which you can identify by running deterministic diagnostics and quality checks.