[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-algolia-algolia-search-implementation":3,"mdc-ow9v32-key":39,"related-repo-algolia-algolia-search-implementation":473,"related-org-algolia-algolia-search-implementation":573},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":23,"repoUrl":24,"updatedAt":25,"license":26,"forks":27,"topics":28,"repo":34,"sourceUrl":37,"mdContent":38},"algolia-search-implementation","implement Algolia search and discovery","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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"algolia","Algolia","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Falgolia.png",[12,14,17,20],{"name":9,"slug":8,"type":13},"tag",{"name":15,"slug":16,"type":13},"E-commerce","e-commerce",{"name":18,"slug":19,"type":13},"Search","search",{"name":21,"slug":22,"type":13},"Frontend","frontend",8,"https:\u002F\u002Fgithub.com\u002Falgolia\u002Fskills","2026-08-01T06:06:02.522421","MIT",2,[29,30,8,31,32,19,33],"agent","ai-assistant","mcp","recommendations","skills",{"repoUrl":24,"stars":23,"forks":27,"topics":35,"description":36},[29,30,8,31,32,19,33],"Algolia skills for AI Agents","https:\u002F\u002Fgithub.com\u002Falgolia\u002Fskills\u002Ftree\u002FHEAD\u002Fskills\u002Falgolia-search-implementation","---\nname: algolia-search-implementation\ndescription: >\n  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.\nlicense: MIT\nmetadata:\n  author: algolia\n  version: \"0.2\"\n---\n\n# Algolia Search Implementation\n\nUse this skill as the execution checklist for net-new Algolia search builds, loaded from `algolia-discovery-planning` once the phase plan marks a greenfield implementation in scope. Its job is to make data, events, index configuration, UI, and release QA visible decision points, especially when an agent needs to move quickly or proceed with provisional assumptions.\n\nUse the whole Algolia lens: data and events are not side quests. The data contract determines what search can retrieve, rank, filter, display, merchandise, secure, and attribute. The event foundation determines whether analytics, personalization, Recommend, Dynamic Re-Ranking, NeuralSearch evaluation, and Agent Studio feedback loops can be trusted. Let UI and AI feature decisions inherit from those foundations instead of discovering them late.\n\n## Recommended Workflow\n\nFor any net-new Algolia search, browse, autocomplete, ecommerce, recommendations, personalization, or Dynamic Re-Ranking implementation, work through these checkpoints in order when practical:\n\n1. Data contract checkpoint: use `algolia-data-modeling`.\n2. Event instrumentation checkpoint: use `algolia-events-insights`.\n3. Index configuration checkpoint: use `algolia-index-configuration`.\n4. UI implementation checkpoint:\n   - Choosing the UI library, framework fit, SSR\u002Frouting strategy, or mobile SDKs: use `algolia-ui-libraries`.\n   - Autocomplete or typeahead: use `algolia-autocomplete`.\n   - Search results page, browse page, filters, facets, routing, sort, pagination, or current refinements: use `algolia-instantsearch-ui`.\n   - Current framework APIs and production code details: use the official `instantsearch` skill alongside `algolia-instantsearch-ui` or `algolia-autocomplete`.\n5. Release QA checkpoint: use `algolia-release-qa`.\n\nBefore UI work, pause long enough to identify the data contract and event taxonomy. If the user asks for a quick prototype or the information is unavailable, proceed with a minimal provisional contract, name the assumptions, and record what must be revisited before launch.\n\n## Foundation Lens\n\nWhen using the full skills library, orient the work in this order:\n\n1. Data shape: records, variants, objectIDs, searchable\u002Fdisplay fields, facets, ranking signals, inventory, permissions, and update ownership.\n2. Event shape: userToken strategy, click and conversion taxonomy, queryID\u002FobjectID\u002Fposition preservation, ownership, deduplication, and validation.\n3. Relevance and UI: settings, widgets, routing, filters, autocomplete sources, and result interactions that match the data and event contracts.\n4. AI readiness: NeuralSearch, Dynamic Re-Ranking, Recommend, personalization, and Agent Studio behavior evaluated against data quality and behavioral signals.\n5. QA: evidence that data, events, settings, UI, security, and rollback are understood.\n\n## Completion Signposts\n\nUse these signposts when deciding whether to call the implementation ready, prototype-ready, or ready with documented follow-ups:\n\n- Data contract exists.\n- Index settings match the UI.\n- Records include all display, facet, ranking, merchandising, inventory, and event-attribution fields used by the experience.\n- Autocomplete has source, ordering, selection, routing, and event-handoff contracts when autocomplete is included.\n- Search results or browse pages handle query, hits, filters, sort, current refinements, pagination or infinite loading, empty states, recovery, loading, and error states when those surfaces are included.\n- Events taxonomy exists.\n- Click events are implemented, validated, or explicitly deferred by the user.\n- Conversion events are planned, implemented, validated, or explicitly deferred by the user.\n- Live index validation queries pass when live data is available.\n- Browser QA passes for the relevant UI surfaces when a browser is available.\n\n## Suggested Artifacts\n\nFor production-oriented work, create or update:\n\n- `algolia\u002Findex-contract.md` or an equivalent index contract artifact.\n- `algolia\u002Fsearch-event-taxonomy.md` or an equivalent event taxonomy artifact.\n- A release QA note or report covering data, settings, UI, events, security, and rollback where relevant.\n\nFor small demos or prototypes, produce the minimal contract:\n\n- One paragraph data contract.\n- One table of events.\n- Three validation queries.\n- Explicit deferred production concerns.\n\n## Decision Behavior\n\n- If sample records, UI fields, objectID strategy, event attribution fields, or userToken strategy are missing, state assumptions and create a provisional artifact instead of silently skipping the decision.\n- If the user asks to defer events or conversions, record the deferral explicitly with owner, risk, and follow-up validation.\n- If live Algolia inspection or writes are needed, route through Algolia MCP, Algolia CLI, or official Algolia skills first, then return to this guided workflow.\n- If a task is only an audit of an existing implementation, start with `algolia-release-qa`, then route findings back to data, events, index configuration, autocomplete, or InstantSearch skills as needed.\n\n## Output Contract\n\nReturn a checkpoint-by-checkpoint implementation summary:\n\n- Data contract status.\n- Event taxonomy status.\n- Index configuration status.\n- UI implementation status.\n- Release QA status.\n- Explicit deferrals and risks.\n- Next validation step.\n",{"data":40,"body":43},{"name":4,"description":6,"license":26,"metadata":41},{"author":8,"version":42},"0.2",{"type":44,"children":45},"root",[46,54,69,74,81,86,211,216,222,227,255,261,266,319,325,330,360,365,388,394,424,430,435],{"type":47,"tag":48,"props":49,"children":50},"element","h1",{"id":4},[51],{"type":52,"value":53},"text","Algolia Search Implementation",{"type":47,"tag":55,"props":56,"children":57},"p",{},[58,60,67],{"type":52,"value":59},"Use this skill as the execution checklist for net-new Algolia search builds, loaded from ",{"type":47,"tag":61,"props":62,"children":64},"code",{"className":63},[],[65],{"type":52,"value":66},"algolia-discovery-planning",{"type":52,"value":68}," once the phase plan marks a greenfield implementation in scope. Its job is to make data, events, index configuration, UI, and release QA visible decision points, especially when an agent needs to move quickly or proceed with provisional assumptions.",{"type":47,"tag":55,"props":70,"children":71},{},[72],{"type":52,"value":73},"Use the whole Algolia lens: data and events are not side quests. The data contract determines what search can retrieve, rank, filter, display, merchandise, secure, and attribute. The event foundation determines whether analytics, personalization, Recommend, Dynamic Re-Ranking, NeuralSearch evaluation, and Agent Studio feedback loops can be trusted. Let UI and AI feature decisions inherit from those foundations instead of discovering them late.",{"type":47,"tag":75,"props":76,"children":78},"h2",{"id":77},"recommended-workflow",[79],{"type":52,"value":80},"Recommended Workflow",{"type":47,"tag":55,"props":82,"children":83},{},[84],{"type":52,"value":85},"For any net-new Algolia search, browse, autocomplete, ecommerce, recommendations, personalization, or Dynamic Re-Ranking implementation, work through these checkpoints in order when practical:",{"type":47,"tag":87,"props":88,"children":89},"ol",{},[90,104,116,128,199],{"type":47,"tag":91,"props":92,"children":93},"li",{},[94,96,102],{"type":52,"value":95},"Data contract checkpoint: use ",{"type":47,"tag":61,"props":97,"children":99},{"className":98},[],[100],{"type":52,"value":101},"algolia-data-modeling",{"type":52,"value":103},".",{"type":47,"tag":91,"props":105,"children":106},{},[107,109,115],{"type":52,"value":108},"Event instrumentation checkpoint: use ",{"type":47,"tag":61,"props":110,"children":112},{"className":111},[],[113],{"type":52,"value":114},"algolia-events-insights",{"type":52,"value":103},{"type":47,"tag":91,"props":117,"children":118},{},[119,121,127],{"type":52,"value":120},"Index configuration checkpoint: use ",{"type":47,"tag":61,"props":122,"children":124},{"className":123},[],[125],{"type":52,"value":126},"algolia-index-configuration",{"type":52,"value":103},{"type":47,"tag":91,"props":129,"children":130},{},[131,133],{"type":52,"value":132},"UI implementation checkpoint:\n",{"type":47,"tag":134,"props":135,"children":136},"ul",{},[137,149,161,173],{"type":47,"tag":91,"props":138,"children":139},{},[140,142,148],{"type":52,"value":141},"Choosing the UI library, framework fit, SSR\u002Frouting strategy, or mobile SDKs: use ",{"type":47,"tag":61,"props":143,"children":145},{"className":144},[],[146],{"type":52,"value":147},"algolia-ui-libraries",{"type":52,"value":103},{"type":47,"tag":91,"props":150,"children":151},{},[152,154,160],{"type":52,"value":153},"Autocomplete or typeahead: use ",{"type":47,"tag":61,"props":155,"children":157},{"className":156},[],[158],{"type":52,"value":159},"algolia-autocomplete",{"type":52,"value":103},{"type":47,"tag":91,"props":162,"children":163},{},[164,166,172],{"type":52,"value":165},"Search results page, browse page, filters, facets, routing, sort, pagination, or current refinements: use ",{"type":47,"tag":61,"props":167,"children":169},{"className":168},[],[170],{"type":52,"value":171},"algolia-instantsearch-ui",{"type":52,"value":103},{"type":47,"tag":91,"props":174,"children":175},{},[176,178,184,186,191,193,198],{"type":52,"value":177},"Current framework APIs and production code details: use the official ",{"type":47,"tag":61,"props":179,"children":181},{"className":180},[],[182],{"type":52,"value":183},"instantsearch",{"type":52,"value":185}," skill alongside ",{"type":47,"tag":61,"props":187,"children":189},{"className":188},[],[190],{"type":52,"value":171},{"type":52,"value":192}," or ",{"type":47,"tag":61,"props":194,"children":196},{"className":195},[],[197],{"type":52,"value":159},{"type":52,"value":103},{"type":47,"tag":91,"props":200,"children":201},{},[202,204,210],{"type":52,"value":203},"Release QA checkpoint: use ",{"type":47,"tag":61,"props":205,"children":207},{"className":206},[],[208],{"type":52,"value":209},"algolia-release-qa",{"type":52,"value":103},{"type":47,"tag":55,"props":212,"children":213},{},[214],{"type":52,"value":215},"Before UI work, pause long enough to identify the data contract and event taxonomy. If the user asks for a quick prototype or the information is unavailable, proceed with a minimal provisional contract, name the assumptions, and record what must be revisited before launch.",{"type":47,"tag":75,"props":217,"children":219},{"id":218},"foundation-lens",[220],{"type":52,"value":221},"Foundation Lens",{"type":47,"tag":55,"props":223,"children":224},{},[225],{"type":52,"value":226},"When using the full skills library, orient the work in this order:",{"type":47,"tag":87,"props":228,"children":229},{},[230,235,240,245,250],{"type":47,"tag":91,"props":231,"children":232},{},[233],{"type":52,"value":234},"Data shape: records, variants, objectIDs, searchable\u002Fdisplay fields, facets, ranking signals, inventory, permissions, and update ownership.",{"type":47,"tag":91,"props":236,"children":237},{},[238],{"type":52,"value":239},"Event shape: userToken strategy, click and conversion taxonomy, queryID\u002FobjectID\u002Fposition preservation, ownership, deduplication, and validation.",{"type":47,"tag":91,"props":241,"children":242},{},[243],{"type":52,"value":244},"Relevance and UI: settings, widgets, routing, filters, autocomplete sources, and result interactions that match the data and event contracts.",{"type":47,"tag":91,"props":246,"children":247},{},[248],{"type":52,"value":249},"AI readiness: NeuralSearch, Dynamic Re-Ranking, Recommend, personalization, and Agent Studio behavior evaluated against data quality and behavioral signals.",{"type":47,"tag":91,"props":251,"children":252},{},[253],{"type":52,"value":254},"QA: evidence that data, events, settings, UI, security, and rollback are understood.",{"type":47,"tag":75,"props":256,"children":258},{"id":257},"completion-signposts",[259],{"type":52,"value":260},"Completion Signposts",{"type":47,"tag":55,"props":262,"children":263},{},[264],{"type":52,"value":265},"Use these signposts when deciding whether to call the implementation ready, prototype-ready, or ready with documented follow-ups:",{"type":47,"tag":134,"props":267,"children":268},{},[269,274,279,284,289,294,299,304,309,314],{"type":47,"tag":91,"props":270,"children":271},{},[272],{"type":52,"value":273},"Data contract exists.",{"type":47,"tag":91,"props":275,"children":276},{},[277],{"type":52,"value":278},"Index settings match the UI.",{"type":47,"tag":91,"props":280,"children":281},{},[282],{"type":52,"value":283},"Records include all display, facet, ranking, merchandising, inventory, and event-attribution fields used by the experience.",{"type":47,"tag":91,"props":285,"children":286},{},[287],{"type":52,"value":288},"Autocomplete has source, ordering, selection, routing, and event-handoff contracts when autocomplete is included.",{"type":47,"tag":91,"props":290,"children":291},{},[292],{"type":52,"value":293},"Search results or browse pages handle query, hits, filters, sort, current refinements, pagination or infinite loading, empty states, recovery, loading, and error states when those surfaces are included.",{"type":47,"tag":91,"props":295,"children":296},{},[297],{"type":52,"value":298},"Events taxonomy exists.",{"type":47,"tag":91,"props":300,"children":301},{},[302],{"type":52,"value":303},"Click events are implemented, validated, or explicitly deferred by the user.",{"type":47,"tag":91,"props":305,"children":306},{},[307],{"type":52,"value":308},"Conversion events are planned, implemented, validated, or explicitly deferred by the user.",{"type":47,"tag":91,"props":310,"children":311},{},[312],{"type":52,"value":313},"Live index validation queries pass when live data is available.",{"type":47,"tag":91,"props":315,"children":316},{},[317],{"type":52,"value":318},"Browser QA passes for the relevant UI surfaces when a browser is available.",{"type":47,"tag":75,"props":320,"children":322},{"id":321},"suggested-artifacts",[323],{"type":52,"value":324},"Suggested Artifacts",{"type":47,"tag":55,"props":326,"children":327},{},[328],{"type":52,"value":329},"For production-oriented work, create or update:",{"type":47,"tag":134,"props":331,"children":332},{},[333,344,355],{"type":47,"tag":91,"props":334,"children":335},{},[336,342],{"type":47,"tag":61,"props":337,"children":339},{"className":338},[],[340],{"type":52,"value":341},"algolia\u002Findex-contract.md",{"type":52,"value":343}," or an equivalent index contract artifact.",{"type":47,"tag":91,"props":345,"children":346},{},[347,353],{"type":47,"tag":61,"props":348,"children":350},{"className":349},[],[351],{"type":52,"value":352},"algolia\u002Fsearch-event-taxonomy.md",{"type":52,"value":354}," or an equivalent event taxonomy artifact.",{"type":47,"tag":91,"props":356,"children":357},{},[358],{"type":52,"value":359},"A release QA note or report covering data, settings, UI, events, security, and rollback where relevant.",{"type":47,"tag":55,"props":361,"children":362},{},[363],{"type":52,"value":364},"For small demos or prototypes, produce the minimal contract:",{"type":47,"tag":134,"props":366,"children":367},{},[368,373,378,383],{"type":47,"tag":91,"props":369,"children":370},{},[371],{"type":52,"value":372},"One paragraph data contract.",{"type":47,"tag":91,"props":374,"children":375},{},[376],{"type":52,"value":377},"One table of events.",{"type":47,"tag":91,"props":379,"children":380},{},[381],{"type":52,"value":382},"Three validation queries.",{"type":47,"tag":91,"props":384,"children":385},{},[386],{"type":52,"value":387},"Explicit deferred production concerns.",{"type":47,"tag":75,"props":389,"children":391},{"id":390},"decision-behavior",[392],{"type":52,"value":393},"Decision Behavior",{"type":47,"tag":134,"props":395,"children":396},{},[397,402,407,412],{"type":47,"tag":91,"props":398,"children":399},{},[400],{"type":52,"value":401},"If sample records, UI fields, objectID strategy, event attribution fields, or userToken strategy are missing, state assumptions and create a provisional artifact instead of silently skipping the decision.",{"type":47,"tag":91,"props":403,"children":404},{},[405],{"type":52,"value":406},"If the user asks to defer events or conversions, record the deferral explicitly with owner, risk, and follow-up validation.",{"type":47,"tag":91,"props":408,"children":409},{},[410],{"type":52,"value":411},"If live Algolia inspection or writes are needed, route through Algolia MCP, Algolia CLI, or official Algolia skills first, then return to this guided workflow.",{"type":47,"tag":91,"props":413,"children":414},{},[415,417,422],{"type":52,"value":416},"If a task is only an audit of an existing implementation, start with ",{"type":47,"tag":61,"props":418,"children":420},{"className":419},[],[421],{"type":52,"value":209},{"type":52,"value":423},", then route findings back to data, events, index configuration, autocomplete, or InstantSearch skills as needed.",{"type":47,"tag":75,"props":425,"children":427},{"id":426},"output-contract",[428],{"type":52,"value":429},"Output Contract",{"type":47,"tag":55,"props":431,"children":432},{},[433],{"type":52,"value":434},"Return a checkpoint-by-checkpoint implementation summary:",{"type":47,"tag":134,"props":436,"children":437},{},[438,443,448,453,458,463,468],{"type":47,"tag":91,"props":439,"children":440},{},[441],{"type":52,"value":442},"Data contract status.",{"type":47,"tag":91,"props":444,"children":445},{},[446],{"type":52,"value":447},"Event taxonomy status.",{"type":47,"tag":91,"props":449,"children":450},{},[451],{"type":52,"value":452},"Index configuration status.",{"type":47,"tag":91,"props":454,"children":455},{},[456],{"type":52,"value":457},"UI implementation status.",{"type":47,"tag":91,"props":459,"children":460},{},[461],{"type":52,"value":462},"Release QA status.",{"type":47,"tag":91,"props":464,"children":465},{},[466],{"type":52,"value":467},"Explicit deferrals and risks.",{"type":47,"tag":91,"props":469,"children":470},{},[471],{"type":52,"value":472},"Next validation step.",{"items":474,"total":572},[475,492,505,517,531,544,555],{"slug":476,"name":476,"fn":477,"description":478,"org":479,"tags":480,"stars":23,"repoUrl":24,"updatedAt":491},"algobot-cli","build conversational AI with Algolia","Use for anything AI\u002Fagent\u002Fconversational built on Algolia: algobot CLI, Agent Studio, RAG systems, conversational product discovery, genAI content generation from search results (carousels, descriptions, headers), chatbots or recommendation agents using Algolia as retrieval, config-as-code workflows, multi-environment deploy (dev\u002Fstaging\u002Fprod), memory and personalization, MCP tool integrations, conversation history \u002F GDPR retention, or adding a chat widget alongside InstantSearch. Trigger on: \"algobot\", \"Agent Studio\", \"RAG with Algolia\", \"conversational experience\", \"AI agent\" + Algolia, \"genAI carousel\", \"chat widget\", or building AI features on top of Algolia search. Do NOT use for raw index ops (records, synonyms, settings) — use algolia-cli. Do NOT use for pure frontend search UI (InstantSearch, autocomplete) with no AI\u002Fagent layer.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[481,484,487,490],{"name":482,"slug":483,"type":13},"Agents","agents",{"name":485,"slug":486,"type":13},"Automation","automation",{"name":488,"slug":489,"type":13},"LLM","llm",{"name":18,"slug":19,"type":13},"2026-07-12T08:27:37.649724",{"slug":493,"name":493,"fn":494,"description":495,"org":496,"tags":497,"stars":23,"repoUrl":24,"updatedAt":504},"algolia-agent-studio","build conversational agents with Algolia Agent Studio","Product-specific Algolia Agent Studio implementation, validation, and optimization guidance. Use when planning, building, integrating, or auditing Agent Studio agents, AI-powered conversational experiences, LLM provider setup, Algolia Search tools, client-side tools, MCP tools, memory, prompting, conversations, turn context, caching, analytics, feedback, authentication, approved domains, guardrails, or tool security. Do NOT use for live Agent Studio configuration, dry runs, publish\u002Fdeploy actions, or config-as-code operations; use the official algobot-cli skill instead. Do NOT use for generic non-Algolia RAG or chatbot architecture unless Agent Studio is the target product.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[498,499,502,503],{"name":482,"slug":483,"type":13},{"name":500,"slug":501,"type":13},"AI","ai",{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},"2026-08-01T06:06:28.033767",{"slug":159,"name":159,"fn":506,"description":507,"org":508,"tags":509,"stars":23,"repoUrl":24,"updatedAt":516},"build Algolia autocomplete and query suggestions","Build and review Algolia Autocomplete and query suggestion experiences. Use when planning or implementing typeahead, query suggestions, recent searches, popular searches, federated autocomplete panels, product\u002Fcontent suggestions, detached mobile mode, plugins, keyboard navigation, insights events, or Autocomplete integration with InstantSearch. For net-new search or ecommerce builds, start with algolia-discovery-planning, which loads algolia-search-implementation so source strategy, data contract, and event taxonomy decisions are visible before autocomplete is marked ready. Do NOT use for full search results pages, browse pages, filters, pagination, or current refinements; use algolia-instantsearch-ui instead. Do NOT use for choosing between Algolia UI libraries; use algolia-ui-libraries. Do NOT use as the source of truth for current Autocomplete package APIs; use the official instantsearch skill and current docs alongside this customer-readiness skill.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[510,511,512,513],{"name":9,"slug":8,"type":13},{"name":21,"slug":22,"type":13},{"name":18,"slug":19,"type":13},{"name":514,"slug":515,"type":13},"UI Components","ui-components","2026-08-01T06:06:29.968123",{"slug":518,"name":518,"fn":519,"description":520,"org":521,"tags":522,"stars":23,"repoUrl":24,"updatedAt":530},"algolia-cli","manage Algolia indices and accounts","Use this skill whenever a user wants to execute operations against Algolia indices or accounts — deleting records, copying\u002Fmigrating indices, backing up data, importing\u002Fexporting records, managing API keys, editing synonyms, configuring rules, changing settings like facets, clearing indices, or automating Algolia in CI\u002FCD pipelines. The key signal is that the user wants to *act on* their Algolia data or configuration (server-side \u002F backend \u002F admin operations), regardless of whether they mention \"CLI\" or \"command line.\" If someone names a specific Algolia index and wants to change, move, query, or manage it, use this skill. Do NOT use for frontend search UI work (InstantSearch, React components, autocomplete widgets), Algolia dashboard GUI questions, or evaluating Algolia vs. other providers.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[523,526,529],{"name":524,"slug":525,"type":13},"CLI","cli",{"name":527,"slug":528,"type":13},"Data Engineering","data-engineering",{"name":18,"slug":19,"type":13},"2026-07-12T08:27:35.085246",{"slug":532,"name":532,"fn":533,"description":534,"org":535,"tags":536,"stars":23,"repoUrl":24,"updatedAt":543},"algolia-crawler","crawl websites into Algolia indices","Use this skill whenever a user wants to crawl one or more web pages or a whole site and turn them into an Algolia index using the Algolia CLI — especially for RAG, AI search, semantic search, or Agent Studio retrieval. Triggers: \"index my website\u002Fdocs with Algolia\", \"set up the Algolia Crawler\", \"crawl this page for RAG\", \"scrape my site into Algolia\", \"build a knowledge base for my AI agent from these URLs\", writing or debugging a crawler recordExtractor, or handling JavaScript-rendered pages that won't index. It guides ingestion end-to-end with `algolia crawler` commands: inspect the page, write a RAG-optimized recordExtractor, validate with `algolia crawler test` BEFORE indexing, apply index settings explicitly, then reindex. Do NOT use for building the chatbot\u002Fagent layer itself (use algobot-cli), raw record\u002Fsynonym\u002Fsettings ops on an existing index (use algolia-cli), frontend search UI (use instantsearch), or read-only search\u002Fanalytics (use algolia-mcp).",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[537,538,539,540],{"name":485,"slug":486,"type":13},{"name":527,"slug":528,"type":13},{"name":18,"slug":19,"type":13},{"name":541,"slug":542,"type":13},"Web Scraping","web-scraping","2026-07-12T08:27:40.981109",{"slug":101,"name":101,"fn":545,"description":546,"org":547,"tags":548,"stars":23,"repoUrl":24,"updatedAt":554},"design Algolia data models and indices","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. 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[549,550,553],{"name":9,"slug":8,"type":13},{"name":551,"slug":552,"type":13},"Data Modeling","data-modeling",{"name":18,"slug":19,"type":13},"2026-08-01T06:06:01.500756",{"slug":66,"name":66,"fn":556,"description":557,"org":558,"tags":559,"stars":23,"repoUrl":24,"updatedAt":571},"plan and audit Algolia search implementations","START HERE for any non-trivial Algolia work — building, adding, migrating, redesigning, auditing, or configuring search, browse, autocomplete, indexing, relevance, recommendations, personalization, merchandising, events, or analytics. Invoke this FIRST even when the task already seems scoped or the user names one specific feature (e.g. \"add InstantSearch\", \"build a storefront search\"): its job is to map the request to the full Algolia implementation lifecycle and load every companion skill each in-scope phase needs (algolia-search-implementation, algolia-data-modeling, algolia-index-configuration, algolia-ui-libraries, algolia-instantsearch-ui, algolia-autocomplete, algolia-events-insights, algolia-neuralsearch, algolia-agent-studio, algolia-release-qa) rather than jumping straight into a single skill. This skill plans and orchestrates; the focused companion skills and the official Algolia skills execute. Do NOT use for live account inspection or write actions; use algolia-mcp or algolia-cli for those.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[560,561,564,567,570],{"name":9,"slug":8,"type":13},{"name":562,"slug":563,"type":13},"Analytics","analytics",{"name":565,"slug":566,"type":13},"Configuration","configuration",{"name":568,"slug":569,"type":13},"Personalization","personalization",{"name":18,"slug":19,"type":13},"2026-08-01T06:06:03.021452",18,{"items":574,"total":693},[575,591,598,605,612,618,625,631,639,649,659,680],{"slug":576,"name":576,"fn":577,"description":578,"org":579,"tags":580,"stars":588,"repoUrl":589,"updatedAt":590},"algolia-docsearch-mcp","search developer documentation with Algolia","Use this skill when the user asks about public developer documentation, SDKs, APIs, libraries, frameworks, setup, configuration, or code examples. Fetch current docs from Algolia DocSearch MCP and cite source URLs.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[581,582,585,587],{"name":9,"slug":8,"type":13},{"name":583,"slug":584,"type":13},"Documentation","documentation",{"name":586,"slug":31,"type":13},"MCP",{"name":18,"slug":19,"type":13},4365,"https:\u002F\u002Fgithub.com\u002Falgolia\u002Fdocsearch","2026-08-01T06:06:11.572314",{"slug":476,"name":476,"fn":477,"description":478,"org":592,"tags":593,"stars":23,"repoUrl":24,"updatedAt":491},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[594,595,596,597],{"name":482,"slug":483,"type":13},{"name":485,"slug":486,"type":13},{"name":488,"slug":489,"type":13},{"name":18,"slug":19,"type":13},{"slug":493,"name":493,"fn":494,"description":495,"org":599,"tags":600,"stars":23,"repoUrl":24,"updatedAt":504},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[601,602,603,604],{"name":482,"slug":483,"type":13},{"name":500,"slug":501,"type":13},{"name":9,"slug":8,"type":13},{"name":18,"slug":19,"type":13},{"slug":159,"name":159,"fn":506,"description":507,"org":606,"tags":607,"stars":23,"repoUrl":24,"updatedAt":516},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[608,609,610,611],{"name":9,"slug":8,"type":13},{"name":21,"slug":22,"type":13},{"name":18,"slug":19,"type":13},{"name":514,"slug":515,"type":13},{"slug":518,"name":518,"fn":519,"description":520,"org":613,"tags":614,"stars":23,"repoUrl":24,"updatedAt":530},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[615,616,617],{"name":524,"slug":525,"type":13},{"name":527,"slug":528,"type":13},{"name":18,"slug":19,"type":13},{"slug":532,"name":532,"fn":533,"description":534,"org":619,"tags":620,"stars":23,"repoUrl":24,"updatedAt":543},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[621,622,623,624],{"name":485,"slug":486,"type":13},{"name":527,"slug":528,"type":13},{"name":18,"slug":19,"type":13},{"name":541,"slug":542,"type":13},{"slug":101,"name":101,"fn":545,"description":546,"org":626,"tags":627,"stars":23,"repoUrl":24,"updatedAt":554},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[628,629,630],{"name":9,"slug":8,"type":13},{"name":551,"slug":552,"type":13},{"name":18,"slug":19,"type":13},{"slug":66,"name":66,"fn":556,"description":557,"org":632,"tags":633,"stars":23,"repoUrl":24,"updatedAt":571},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[634,635,636,637,638],{"name":9,"slug":8,"type":13},{"name":562,"slug":563,"type":13},{"name":565,"slug":566,"type":13},{"name":568,"slug":569,"type":13},{"name":18,"slug":19,"type":13},{"slug":114,"name":114,"fn":640,"description":641,"org":642,"tags":643,"stars":23,"repoUrl":24,"updatedAt":648},"instrument Algolia events for analytics","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\u002Fbackend 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[644,645,646,647],{"name":9,"slug":8,"type":13},{"name":562,"slug":563,"type":13},{"name":568,"slug":569,"type":13},{"name":18,"slug":19,"type":13},"2026-08-01T06:06:02.009712",{"slug":126,"name":126,"fn":650,"description":651,"org":652,"tags":653,"stars":23,"repoUrl":24,"updatedAt":658},"configure Algolia index settings and relevance","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\u002Fcategory relevance, or A\u002FB-testable relevance changes. 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[654,655,656,657],{"name":9,"slug":8,"type":13},{"name":565,"slug":566,"type":13},{"name":551,"slug":552,"type":13},{"name":18,"slug":19,"type":13},"2026-08-01T06:06:34.19163",{"slug":171,"name":171,"fn":660,"description":661,"org":662,"tags":663,"stars":23,"repoUrl":24,"updatedAt":679},"build Algolia InstantSearch frontend experiences","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\u002Fcategory 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\u002Ftypeahead 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.\n",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[664,665,668,669,672,675,676],{"name":9,"slug":8,"type":13},{"name":666,"slug":667,"type":13},"Angular","angular",{"name":21,"slug":22,"type":13},{"name":670,"slug":671,"type":13},"JavaScript","javascript",{"name":673,"slug":674,"type":13},"React","react",{"name":18,"slug":19,"type":13},{"name":677,"slug":678,"type":13},"Vue","vue","2026-08-01T06:06:33.66513",{"slug":681,"name":681,"fn":682,"description":683,"org":684,"tags":685,"stars":23,"repoUrl":24,"updatedAt":692},"algolia-mcp","search Algolia indices and retrieve analytics","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.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[686,687,690,691],{"name":562,"slug":563,"type":13},{"name":688,"slug":689,"type":13},"API Development","api-development",{"name":586,"slug":31,"type":13},{"name":18,"slug":19,"type":13},"2026-07-12T08:27:36.376387",19]