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

/algolia-core-workflow-a

@820dfc8
Run it yourself

Implement or review a single-index Algolia search contract with filters, facets, pagination, and highlighting. Use when building product or content search against the JavaScript v5 client. Trigger with "Algolia search workflow", "add facets", or "searchSingleIndex".

Use this Skill: https://skilld.dev/gh/jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-a

Nothing lands on disk. Nothing to clean up.

Fork this Skill

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

SKILL.md

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

Description uses 3.6% 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 ≈292 characters, or 3.6%.

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 Search Contract

Overview

This skill defines the read path between application input and Algolia search results. It keeps query construction, allowed filters, pagination, and result projection explicit so UI behavior can be tested independently.

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

  • Use searchSingleIndex for one index and pass indexName plus searchParams on the v5 client.
  • Treat filters and facet filters as structured application inputs; do not concatenate untrusted syntax.
  • Request only attributes the interface needs and preserve objectID as the stable result identity.
  • Enable click analytics only when the product also implements the query ID and event contract.

Authentication

Browser search should use the search-only key or a backend-generated secured key. Write-capable credentials remain server-side.

Instructions

  1. Inspect the installed client version, index settings, record schema, and current UI query state.
  2. Define a typed search input with bounded query length, page, hits per page, filters, and facets.
  3. Translate application filters through an allowlist rather than accepting raw filter strings.
  4. Call the v5 search boundary and map hits into the application result type.
  5. Test empty query, no results, special characters, pagination edges, and unavailable facets.
  6. Verify returned attributes do not disclose fields the interface should not expose.

Approval Boundaries

Do not change index settings, enable analytics, or expose additional attributes as part of a read-path implementation without explicit review.

Output

Return the typed input/output contract, query builder, relevant tests, credential boundary, observed response metadata, and any required index-setting change.

Error Handling

Condition Response
Invalid filter syntax Reject or normalize at the application boundary.
Facet missing Confirm the attribute is configured before changing the UI.
Unexpected fields returned Tighten retrieval and index visibility settings.
No query ID Enable click analytics only with an approved event design.

Examples

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

Input:

query=boots; facets=brand,size; page=0; credential=search-only

Expected handoff:

hits=24; exposed-fields=objectID,name,price; raw-filter-input=blocked

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

    The skill is safe and follows security best practices for implementing Algolia search, including credential separation and input validation.

  • 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] [index-name]
version
1.8.0
author
Jeremy Longshore <jeremy@intentsolutions.io>
All 6 allowed tools
ReadGlobGrepWebFetchWriteEdit
Other metadata
tags
[
  "saas",
  "algolia",
  "search"
]
model
inherit
effort
medium
compatibility
Designed for Claude Code

README badge

README badge for jeremylongshore/tons-of-skills-marketplace/algolia-core-workflow-a