paradedb-skill

Write ParadeDB SQL for BM25 and pgvector hybrid search queries.

6|4|Updated Nov 1, 2025
One-click install
npx skills add https://github.com/Montte-erp/montte-nx --skill paradedb-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paradedb-skill
Source: https://github.com/Montte-erp/montte-nx/tree/main/.agents/skills/paradedb-skill
Command: npx skills add https://github.com/Montte-erp/montte-nx --skill paradedb-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and data engineers implement and tune high-quality full-text and hybrid search (BM25 + semantic vectors) inside Postgres using ParadeDB, removing guesswork about index design, tokenizers, and relevance tuning.

Core Features & Use Cases

  • Query Authoring: Provide runnable ParadeDB SQL for BM25 indexes, hybrid searches with pgvector, phrase and fuzzy queries, and relevance scoring.
  • Configuration Guidance: Recommend tokenizers, analyzers, BM25 field weights, and hybrid fusion strategies for production search.
  • Operational Advice: Explain migration patterns from Elasticsearch, faceted aggregations, and performance/monitoring tips for large datasets.
  • Use Case: Implement a product search that combines BM25 title/description ranking with vector semantics for personalized relevance.

Quick Start

Fetch the official ParadeDB llms-full.txt docs, then produce a runnable ParadeDB SQL statement that creates a BM25 index and a hybrid BM25+vector query for a products table.

Frequently Asked Questions about paradedb-skill

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

FAQPage Schema
How do I implement hybrid search with pgvector and BM25 in Postgres?

Hybrid search in Postgres combines BM25 text ranking with pgvector semantic scoring. You configure BM25 indexes with specific field weights and use fusion strategies to merge relevance scores for personalized search results.

What's the best way to migrate from Elasticsearch to Postgres full-text search?

Migrating from Elasticsearch to Postgres full-text search involves creating BM25 indexes with configurable tokenizers and analyzers. This approach delivers Elasticsearch-quality search relevance natively inside Postgres without maintaining a separate search engine.

How do I configure tokenizers and analyzers for a ParadeDB BM25 index?

Configuring BM25 index tokenizers and analyzers requires specifying settings in your SQL index creation statement. You define tokenization rules and BM25 field weights to control how text is processed and ranked for production search.

Can I use ParadeDB for faceted aggregations and product search in Postgres?

ParadeDB supports faceted aggregations and product search inside Postgres by combining phrase queries, fuzzy matching, and BM25 scoring. It handles large datasets with performance monitoring and query tuning for analytics workflows.

Does ParadeDB require fetching official documentation to write accurate SQL queries?

Writing accurate ParadeDB SQL requires fetching and caching the official ParadeDB llms-full.txt documentation. This ensures precise syntax for BM25 indexing, hybrid search queries, and tokenizer configuration.

Why use BM25 field weighting instead of standard Postgres full-text search?

BM25 field weighting provides superior relevance tuning compared to standard Postgres full-text search. It allows differential scoring across document fields, combining with pgvector semantics for hybrid search results.