Agent skill · marketing growth · jeremylongshore
algolia-cost-tuning
Audit Algolia usage drivers and propose measurable cost controls without hard-coded plan prices. Use when search spend, request volume, record count, replicas, or optional features need investigation. Trigger with "Algolia cost audit", "reduce Algolia usage", or "Algolia bill".
Why this skill is useful
Provides specific strategies and code snippets for optimizing Algolia costs that the AI wouldn't reliably generate on its own.
What it needs
Requires algolia account access. About 2k tokens when loaded. Last updated 2026-08-07. 2,604 stars on the source repository.
What this skill does
Algolia Usage and Cost Review Overview This skill correlates current Algolia billing and usage evidence with application behavior. It deliberately avoids embedding plan names, prices, free allowances, or assumptions that indexing is unmetered because commercial terms can change. Prerequisites A named repository, environment, and Algolia application or index in scope The local lockfile and installed client types as implementation authority A safe read-only query or explicitly disposable test target Current first-party documentation for any provider behavior that affects the change Tool Discipline Use Read, Glob, and Grep to inspect local code, configuration names, tests, and dependency versions. Use WebFetch only for current official Algolia documentation. Use Write or Edit only after identifying the target files, constraints, and verification plan. Current Contract Treat the account's current invoice, usage dashboard, and contract as the authority for billable units. Separate search traffic, records, replicas, indexing activity, analytics or AI features, and non-production duplication. Measure request amplification caused by keystrokes, federated queries, retries, bots, and duplicate clients. Recommend controls only when they preserve relevance, freshness, security, and product requirements. Authentication Use read-only account access or exported billing evidence. Do not put billing, usage, Analytics, or Admin credentials in frontend code or reports. Instructions 1. Define the billing window, applications, indices, environments, replicas, and contract source in scope. 2. Capture current usage and invoice line items without copying secret values. 3. Trace major units back to callers, UI interactions, scheduled jobs, duplicated records, and optional features. 4. Quantify each candidate change with a baseline, expected delta, uncertainty, and product tradeoff. 5. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills jeremylongshore/algolia-cost-tuning