| name | paradedb-skill |
| description | Expert guidance on ParadeDB full-text search, hybrid search (BM25 + semantic), aggregations, and analytics in Postgres. Use when writing ParadeDB queries, creating BM25 indexes, configuring tokenizers, or implementing Elasticsearch-quality search in Postgres.
|
ParadeDB Skill
ParadeDB is one Postgres that unifies your application data, full-text search, vector retrieval, and aggregations via the pg_search extension.
Use this skill when users ask about:
- BM25 indexes and relevance ranking
- Hybrid search (keyword + semantic vectors via
pgvector)
- Tokenizers, analyzers, fuzzy matching, and phrase queries
- Facets, aggregations, snippets/highlighting, and query tuning
For up-to-date ParadeDB documentation, always fetch the documentation index
(llms.txt) using the bundled script at scripts/paradedb-docs.
Resolve that path relative to the directory containing this SKILL.md, not
relative to the current working directory or repo root.
scripts/paradedb-docs llms.txt
Once you have the list of urls, load the pages necessary to answer the user's question. For example:
scripts/paradedb-docs documentation/getting-started/environment.md
scripts/paradedb-docs documentation/full-text/match.md
scripts/paradedb-docs documentation/indexing/create-index.md
After a successful fetch, treat that content as cached session context and
reuse it for later ParadeDB questions in the same session if applicable.
Do not refetch on every turn when the previously fetched docs are still
available and relevant.
The tool uses curl internally and requires network access. Make sure you run it with network access.
If you have to ask the user for permission to run the tool, make sure to ask them to allow you to run
the command for all arguments so you can fetch every page.
