search-engine_skill

This skill helps you design and implement production-ready search engines with deterministic pipelines, recall-precision layering, and measurable evaluation.
  • Python

2.5k

GitHub Stars

8

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill search-engine

  • _meta.json283 B
  • architecture-blueprint.md1.5 KB
  • evaluation-metrics.md1.1 KB
  • implementation-checklist.md865 B
  • memory-template.md1.4 KB
  • retrieval-patterns.md1.2 KB
  • setup.md2.0 KB
  • SKILL.md6.0 KB

Overview

This skill helps you design and build production-grade search engines with robust indexing, retrieval, relevance controls, and evaluation workflows. It codifies architecture patterns, deterministic ingestion pipelines, staged retrieval, and safe rollout practices. The goal is predictable, testable search behavior that matches explicit retrieval contracts and business objectives.

How this skill works

The agent guides you through defining a retrieval contract (query types, latency, freshness, and error tolerance) and then proposes deterministic ingestion and indexing pipelines with stable identifiers and resumable jobs. It separates recall and precision into staged components (broad candidate retrieval, reranking, formatting) and prescribes versioned relevance policies, offline evaluation workflows, and idempotent index operations for safe rollouts. It also maintains local planning notes, experiment logs, and incident records to support continuous improvement and audits.

When to use it

  • Designing a new search system for documentation, product catalogs, or knowledge bases
  • Redesigning an existing search to improve relevance, latency, or scalability
  • Scaling retrieval and ranking for growing or multilingual corpora
  • Implementing safe rollout and rollback procedures for index and relevance changes
  • Establishing repeatable evaluation and experiment pipelines before production writes

Best practices

  • Start with a clear retrieval contract before choosing tools or vendors
  • Implement ingestion as deterministic, repeatable stages with stable IDs
  • Keep recall and precision separate: retrieve broad candidates, then rerank
  • Version relevance policies and record feature weights and boosts
  • Run offline benchmarks and comparisons before changing production behavior
  • Build resumable, idempotent index operations and alias-based rollback plans

Example use cases

  • Create a hybrid search for a product catalog supporting keyword and semantic queries
  • Redesign enterprise document search to improve multilingual precision and filtering
  • Add offline evaluation pipelines to validate relevance tuning before deployment
  • Implement safe index updates for a high-availability search service using aliases
  • Define retrieval SLAs and hit-quality benchmarks for a public-facing search API

FAQ

A retrieval contract documents query types, response format, latency, freshness, and error tolerance. It prevents tool-driven decisions and gives measurable success criteria for design and evaluation.

How do I avoid catastrophic rollouts when changing relevance?

Version relevance policies, run offline benchmarks with labeled queries, compare deltas to a baseline, and deploy behind feature gates with rollback-ready aliases and resumable index updates.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational