query-index-optimizer

Audit helix-query.yaml properties against live query-index.json and sitemap URLs.

Updated May 14, 2026
One-click install
npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill query-index-optimizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query-index-optimizer
Source: https://github.com/Focus-GTS/eds-content-ops-skills/tree/main/skills/query-index-optimizer
Command: npx skills add https://github.com/Focus-GTS/eds-content-ops-skills --skill query-index-optimizer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you diagnose and optimize an AEM Edge Delivery Services (EDS) helix-query.yaml query index when the index is bloated, missing pages, or contains stale entries that break block-driven lists and navigation.

Core Features & Use Cases

It audits the live query-index.json output, compares indexed entries against your sitemap to find missing pages, and checks for stale entries by validating indexed paths. It also analyzes index size and pagination behavior and produces ready-to-paste Helix recommendations for improving property coverage and performance.

Quick Start

Ask the AI to audit your EDS query index for bloated properties and stale or missing pages, using your branch URL and GitHub repo details, and to generate the exact helix-query.yaml diff to improve it.

Frequently Asked Questions about query-index-optimizer

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

FAQPage Schema
Why does my AEM Edge Delivery Services query index contain stale entries and missing pages?

AEM EDS query index bloat and missing pages occur when helix-query.yaml properties are misconfigured against live URLs. Auditing the query-index.json output against your sitemap identifies stale entries and missing paths to resolve block-driven list and navigation gaps.

How do I audit helix-query.yaml properties against live query-index.json output?

To audit helix-query.yaml, fetch the live query-index.json output and compare indexed properties against actual sitemap URLs. This maps property usage to downstream consumers and generates actionable helix-query.yaml recommendation diffs to fix missing pages and bloat.

What is the best way to fix bloated AEM EDS query indexes hitting the default limit?

Fixing bloated AEM EDS query indexes requires analyzing index size and pagination behavior to determine if configuration changes or architectural updates are needed. Optimizing helix-query.yaml property coverage reduces bloat and restores block-driven list functionality.

Can I generate a helix-query.yaml diff to resolve incomplete block-driven lists and navigation?

Yes, analyzing live query-index.json output and mapping property usage to downstream consumer needs produces ready-to-paste helix-query.yaml recommendation diffs. These diffs optimize property coverage and resolve incomplete block-driven lists and navigation.

Does the query index optimization process work with existing sitemap URLs?

Yes, the optimization process validates indexed paths by comparing live query-index.json entries against actual sitemap URL existence. This checks for stale entries and missing pages to ensure your AEM EDS query index reflects live site architecture.

When should I restructure my AEM EDS query index architecture instead of adjusting properties?

Restructuring AEM EDS query index architecture is necessary when index responses hit the default limit and pagination fails to resolve performance issues. Analyzing index size and pagination behavior determines whether property adjustments or architectural changes are required.