li-index

Synchronize INDEX.md files with source documents and repair stale entries.

79|18|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/jiangjiax/li-skills --skill li-index
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: li-index
Source: https://github.com/jiangjiax/li-skills/tree/main/li-index
Command: npx skills add https://github.com/jiangjiax/li-skills --skill li-index

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents broken or outdated INDEX entries by ensuring every indexed library stays synchronized with its underlying source files, so AI retrieval remains accurate and reference-worthy.

Core Features & Use Cases

  • Incremental index maintenance: When you add or move a file in any INDEX-managed library, it reads the full source content and appends a correct entry into the right partition following the existing INDEX format.
  • Index health-check (diff + repair): When you run an index inspection, it scans actual files vs recorded INDEX paths, produces a missing/invalid report, and then updates only after you confirm what to add or clean up.
  • Multi-library coverage: Supports all registered INDEX-based libraries described in the skill, including special handling rules for each library type (e.g., different INDEX formats and special blast-script index behavior).

Quick Start

When you say “索引体检”,run an index health-check and show the diff report first, then ask what to repair before making any changes.

Frequently Asked Questions about li-index

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

FAQPage Schema
How do I keep INDEX.md files synchronized with my markdown source documents?

To keep INDEX.md files synchronized, this Skill reads full source content and updates index entries to match the actual files, ensuring AI knowledge retrieval remains accurate and preventing broken or outdated paths.

What is a markdown index health check and how does a diff report work?

A markdown index health check scans actual files against recorded INDEX paths to produce a missing or invalid diff report. It verifies stale entries across registered libraries before executing any user-confirmed repairs.

How do I add new entries to an existing knowledge library index after moving files?

To add new entries after moving files, the Skill performs incremental index maintenance by appending correct entries into the right partition, strictly preserving the existing INDEX formatting and path conventions.

Can I apply index maintenance across multiple knowledge libraries with different formatting rules?

Yes, you can apply index maintenance across multiple registered INDEX-based libraries. It supports special handling rules for each library type, including different INDEX formats and specific blast-script index behaviors.

Does the index repair process automatically overwrite my existing INDEX formatting?

No, the index repair process does not automatically overwrite formatting. It requires full source reading, preserves existing INDEX path conventions, and performs updates only after you confirm the diff report.