Index of every page on this site: llms.txt
All skills
jeremylongshore avatar

/algolia-performance-tuning

@820dfc8
Run it yourself

Analyze and optimize an Algolia search path using repository and production evidence instead of universal latency targets. Use when search feels slow, payloads are large, or rendering regresses. Trigger with "tune Algolia performance", "slow Algolia search", or "search latency".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-performance-tuning

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈77 tokens for metadata: the name and description. ≈854 when used: this file. ≈333 more on demand in 1 file.

Description uses 3.9% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈308 characters, or 3.9%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Algolia Evidence-Based Performance Tuning

Overview

This skill decomposes perceived search time into input handling, network, provider request, response transfer, transformation, and render work. Optimization starts with an owned baseline and ends with a comparable measurement.

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

  • Set targets from the application's SLO, user geography, device mix, and measured baseline.
  • Inspect record and response shape before changing relevance or faceting settings.
  • Separate query count amplification from individual request latency.
  • Preserve correctness and relevance assertions alongside performance measurements.

Authentication

Run measurements with search-only or secured keys and sanitized representative queries. Do not expose write credentials or sensitive query logs.

Instructions

  1. Define the journey, environment, representative query set, device/network profile, and success criteria.
  2. Capture request count, component timings, payload size, cache behavior, result correctness, and render cost.
  3. Locate the dominant segment before proposing changes.
  4. Test bounded changes such as debouncing, stalled-search handling, requested attributes, query batching, or render work.
  5. Compare before and after with the same harness and inspect relevance and freshness regressions.
  6. Document the accepted change, uncertainty, monitoring signal, and rollback trigger.

Approval Boundaries

Do not change ranking, remove required facets, cache personalized responses, or publish claimed improvements without comparable evidence.

Output

Return the benchmark protocol, baseline distribution, bottleneck attribution, tested changes, before/after evidence, relevance checks, and rollout guardrails.

Error Handling

Condition Response
Results are noisy Increase samples and control geography, device, cache, and query set.
Faster response changes hits Reject or obtain product acceptance for the relevance tradeoff.
Client emits duplicate requests Fix lifecycle or input handling before provider tuning.
No SLO exists Report the baseline without inventing a target.

Examples

Use this compact input and expected handoff to calibrate scope and evidence quality.

Input:

journey=mobile-typeahead; queries=approved-100; network=recorded-profile

Expected handoff:

dominant=duplicate-client-requests; requests-keystroke=3-to-1; relevance=unchanged

Resources

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

No alerts2mo3 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill provides a structured framework for analyzing and optimizing Algolia search performance based on empirical evidence. It adheres to security best practices, such as recommending the use of search-only API keys and sanitizing representative queries. No security issues or malicious patterns were detected.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: LOW · No issues

Signed by skilld at 820dfc8. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub yesterday.

Activeupdated 2 months ago
What it can do
Reads files Network Edits files
Modelinherit
argument-hint
[repository-path] [journey-or-query-set]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "performance"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-performance-tuning