Verified:GitHub

zicato-index-ops

Rebuild the derived SQLite analytical index from canonical zicato workspace files.

4|2|Updated May 14, 2026

Search Tags:#sqlite #index rebuilding #loss analysis #cross-run analytics #tournament history #drift metrics #generation lineage

Ready to run

npx skills add https://github.com/pedapudi/zicato --skill zicato-index-ops

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: zicato-index-ops
Source: https://github.com/pedapudi/zicato/tree/main/skills/zicato-index-ops
Command: npx skills add https://github.com/pedapudi/zicato --skill zicato-index-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill keeps zicato’s derived SQLite analytical index synchronized with canonical workspace files and enables safe cross-run investigation without hand-editing or corrupting the index.

Core Features & Use Cases

Index Rebuilding: Rebuild the complete SQLite projection after canonical workspace files are changed.
Targeted Repair: Repair generation lineage and promotion data when only the generations table has drifted.
Read-Only Analytics: Query loss profiles, tournaments, experiments, patches, judge results, drift metrics, and generation lineage across epochs.
Use Case: Investigate which drift metrics recur most often, compare generation outcomes, and identify mutation points associated with rejected tournaments.

Quick Start

Ask the zicato index-ops skill to rebuild the workspace index and report the generations with the highest average drift loss.

Frequently Asked Questions about zicato-index-ops

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

FAQPage Schema

How do I rebuild a SQLite analytical index after hand-editing canonical workspace files?▼

You can rebuild the derived SQLite analytical index from canonical zicato workspace files to synchronize projections after manual epoch data changes. This process repairs stale indexes and restores data integrity for cross-run analytics.

What is the best way to query tournament history and loss analysis across multiple runs?▼

Querying tournament history and loss analysis across runs requires read-only SQLite SELECT commands against the workspace index database. This approach enables safe cross-run investigation of loss profiles, judge results, and drift metrics without consuming LLM budget.

Do I need the zicato CLI to investigate drift metrics and generation lineage?▼

Yes, investigating drift metrics and generation lineage requires the zicato CLI and a workspace index database. The CLI manages index rebuilding and targeted repair of promotion data when the generations table drifts.

How does targeted repair fix generation lineage drift without rebuilding the entire database?▼

Targeted repair fixes generation lineage drift by selectively rewriting promotion data in the SQLite analytical index. This isolates corrections to the generations table, avoiding a full database rebuild while restoring lineage integrity.

Can I identify mutation points associated with rejected tournaments using SQLite queries?▼

Yes, you can identify mutation points associated with rejected tournaments using read-only SQLite SELECT queries. This cross-run analytics capability compares generation outcomes and investigates recurring drift metrics without hand-editing the index.

When should I avoid manual SQLite edits to prevent corrupting the workspace index?▼

You should avoid manual SQLite edits when investigating stale indexes or generation lineage, as hand-editing corrupts the derived analytical index. Instead, use index rebuilding or targeted repair via the zicato CLI to maintain synchronization.