algolia

Index Firestore data into Algolia for real-time search across multiple domain entities.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/trusted-american/marketplace --skill algolia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: algolia
Source: https://github.com/trusted-american/marketplace/tree/main/plugins/a3-plugin/skills/algolia
Command: npx skills add https://github.com/trusted-american/marketplace --skill algolia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Algolia-backed search across multiple domain entities by syncing Firestore data to Algolia indices, enabling fast, facet-rich queries across clients, deals, contacts, and products.

Core Features & Use Cases

  • Backend integration with separate indices for entities (clients, deals, contacts, products)
  • Firestore-to-Algolia sync triggers (onCreate, onUpdate, onDelete)
  • Frontend search service integration (key retrieval and client-side search)
  • Index configuration (searchable attributes, facets, filtering, ranking)
  • Use Case: In-app enterprise search across multiple entities with per-organization isolation

Quick Start

Install and configure the Algolia backend services and frontend key retrieval to enable real-time search.

Frequently Asked Questions about algolia

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

FAQPage Schema
How do I index Firestore data into Algolia for real-time search?

To index Firestore data into Algolia for real-time search, you deploy backend sync triggers using onCreate, onUpdate, and onDelete events to push data changes into separate Algolia indices for each entity.

What's the best way to implement faceted filtering across multiple Firestore entities?

The best way to implement faceted filtering across Firestore entities is syncing data to separate Algolia indices per entity, then configuring index settings for searchable attributes, facets, filtering, and ranking.

Do I need separate Algolia indices for different domain entities like clients, deals, and products?

Yes, you need separate Algolia indices for different domain entities. Maintaining distinct indices for clients, deals, contacts, products, and invoices enables precise facets, filtering, and pagination for typical business workflows.

How do I secure frontend API keys when querying Algolia indices directly?

You secure frontend API keys when querying Algolia indices by implementing a backend service for key retrieval that generates secured, restricted API keys before granting frontend search access to the client.

Can I achieve per-organization data isolation when searching across multiple Algolia indices?

Yes, you can achieve per-organization data isolation when searching across multiple Algolia indices by using secured API keys with filtering parameters applied during frontend search service integration.