Algolia search
Algolia's skills for search: record and index design, relevance settings, InstantSearch UI and click and conversion events.
Category: Backend. By playbookrun. Reviewed by PlaybookRun before publishing. Installs in Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and more.
Tags: algolia, search, instantsearch, indexing, relevance
Skills
- Algolia Search Implementation (algolia-search-implementation): Execution checklist for net-new Algolia search, browse, autocomplete, ecommerce search, recommendations, personalization, Dynamic Re-Ranking, or search UI builds. Use during a greenfield build to keep data contract, event taxonomy, index configuration, UI, and release QA visible as explicit checkpoints with completion signposts and suggested artifacts, so agents proceed deliberately and document tradeoffs and deferrals. Do NOT use as the entry point for Algolia work; start with algolia-discovery-planning, which maps the request to the lifecycle and loads this skill for net-new builds.
- Algolia Index Configuration (algolia-index-configuration): Algolia index settings and relevance configuration guidance. Use when configuring searchableAttributes, attributesForFaceting, customRanking, ranking, replicas, virtual replicas, rules, synonyms, typo tolerance, distinct, filters, optional filters, merchandising, browse/category relevance, or A/B-testable relevance changes. Also use when auditing, reviewing, health-checking, or troubleshooting an EXISTING index's settings — "is this configured correctly", inherited implementations, relevance regressions, or a settings review before launch — not only when configuring something new. Do NOT use for live settings writes, backups, copies, or operational account tasks; use algolia-cli or algolia-mcp instead. Do NOT use for record-shape or variant strategy; use algolia-data-modeling instead.
- Algolia Data Modeling (algolia-data-modeling): Algolia data modeling and indexing guidance. Use before or alongside indexing records or building Algolia search UI for net-new search, browse, autocomplete, ecommerce, personalization, Dynamic Re-Ranking, recommendations, or analytics-aware implementations. Also use to audit or review an EXISTING implementation's record shape and data contract. Makes record shape, objectID, display fields, facets, ranking fields, and event attribution explicit decisions. Use for records, variants, SKUs, indices, replicas, searchable and faceting attributes, denormalization, merchandising fields, timestamps, inventory, event attribution, indexing pipelines, partial updates, secured data, multi-language or multi-region strategies, and migrations. Do NOT use for live imports, exports, record mutations, settings changes, or account actions; use algolia-cli or algolia-mcp. Do NOT use for frontend UI implementation; use algolia-instantsearch-ui, algolia-autocomplete, algolia-ui-libraries, or the official instantsearch skill.
- Algolia InstantSearch UI (algolia-instantsearch-ui): Build and review Algolia InstantSearch experiences in JavaScript, React, Vue, Angular (via InstantSearch.js; Angular InstantSearch is deprecated), or compatible frontend stacks. Use when planning or reviewing search results pages, browse/category pages, routing, widgets, filters, facets, sort-by, pagination, infinite hits, current refinements, insights middleware, SSR, or UI-state synchronization. For net-new search UI builds, start with algolia-discovery-planning, which loads algolia-search-implementation so data contract and event taxonomy decisions are visible before UI is marked ready. Do NOT use for autocomplete/typeahead experiences before the user commits to a results page; use algolia-autocomplete instead. Do NOT use for choosing between Algolia UI libraries; use algolia-ui-libraries. Do NOT use as the source of truth for current framework APIs or code-level implementation details; use the official instantsearch skill and current docs alongside this customer-readiness skill.
- Algolia Events Insights (algolia-events-insights): Algolia event instrumentation guidance for Insights, analytics, personalization, Dynamic Re-Ranking, Recommend, and merchandising feedback loops. Use for search, autocomplete, browse, ecommerce, personalization, recommendations, or analytics instrumentation. Makes event decisions explicit before an Algolia UI is considered ready. Use when implementing or auditing clickedObjectIDsAfterSearch, convertedObjectIDsAfterSearch, viewedObjectIDs, addedToCartObjectIDsAfterSearch, purchasedObjectIDsAfterSearch, userToken, queryID, eventName, eventSubtype, or frontend/backend event pipelines. Do NOT use for live analytics retrieval, top-query inspection, or account-aware diagnostics; use algolia-mcp. Do NOT use for framework-specific InstantSearch or Autocomplete APIs; use the official instantsearch skill alongside this planning and validation skill.
- Algolia Search & Analytics (algolia-mcp): Search Algolia indices via the Algolia MCP server, retrieve analytics (top searches, no-result rates, click positions, user counts), and get product recommendations (bought-together, related, trending). Triggers on search, indexing, analytics, Algolia, recommendations, MCP.
MCP servers
- Algolia: Algolia's hosted server: search and inspect your indices and analytics; sign in with your Algolia account.
Install
claude plugin marketplace add Fcakiroglu16/marketplace claude plugin install algolia-search@playbookrun