cqs-stats

Display index statistics including chunk counts by language and last update time for the cqs index.

13|3|Updated Jan 31, 2026
One-click install
npx skills add https://github.com/jamie8johnson/cqs --skill cqs-stats
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cqs-stats
Source: https://github.com/jamie8johnson/cqs/tree/main/.claude/skills/cqs-stats
Command: npx skills add https://github.com/jamie8johnson/cqs --skill cqs-stats

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

cqs-stats exposes essential index health metrics for the MCP code search tool, including per-language chunk counts and the last update timestamp, enabling quick maintenance decisions.

Core Features & Use Cases

  • Show chunk counts broken down by language to identify indexing gaps
  • Display total indexed chunks and the last update time for historical tracking
  • Use in regular audits, capacity planning, and health checks of the local index

Quick Start

Run the cqs_stats tool to retrieve current index statistics from the local MCP index.

Frequently Asked Questions about cqs-stats

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

FAQPage Schema
How do I check the health of my code search index?

Checking code search index health involves reading the local index to display concise metrics like per-language chunk counts and the last update time, enabling quick maintenance decisions and capacity planning.

What metrics are needed for a code search index audit?

A code search index audit requires per-language chunk counts, total indexed chunks, and the last update timestamp to monitor indexing progress across multiple languages and identify indexing gaps.

How can I monitor indexing progress across multiple languages?

Monitoring indexing progress across multiple languages is done by retrieving current index statistics that show chunk counts broken down by language and the total indexed data from the local index.

Does the code search stats tool require external dependencies?

The code search stats tool requires no external dependencies, reading the local index directly to provide deterministic output suitable for human review or downstream tooling integration.

Can I use index statistics for downstream tooling and automation?

Index statistics can be used for downstream tooling because the tool formats concise metrics with deterministic output and no external dependencies, making it suitable for automated health checks and regular audits.