Algolia Audit

Use this skill FIRST when reviewing an existing Algolia implementation. Its core premise: the costliest configuration defects are symptom-free. The store works, queries return, nothing errors — and the settings are still wrong in ways that quietly cost relevance, analytics integrity, security, and revenue. An audit that only investigates visible breakage will systematically miss them.

Customer-Facing Standard

• Audit against what correct looks like, not against whether anything is visibly failing. "It works" is not evidence that it is right.
• Capture the current live state (settings, replica settings, sample hit payloads, a rendered page) before proposing any change, so every finding has a before/after.
• Lead the report with the highest-severity findings; state what was checked, what was not, and what evidence backs each finding.
• When live Algolia data, settings, or account inspection is needed, use the Algolia CLI, Algolia MCP, or official Algolia skills for the live operation, then apply this skill to interpret results.
• Distinguish defects (wrong against documented practice) from preferences (defensible alternatives), and say which is which. Do not reclassify a defect as a preference to avoid the work of fixing it.

Official Companion Skills

Route deep work to the focused skills — read them, don't reinvent them: