Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →griddynamics/solr-query
To build and debug Solr queries: eDisMax, block join, JSON facets, kNN, explain.
Passed 25 of 25 test cases with the skill, and 23 of 25 without it.
and 1 more in the full report
2 fixed23 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
A Solr 9 kNN vector query `q={!knn f=vector topK=10}[0.1, 0.2, ...]` combined with a restrictive filter `fq=category:electronics` returns 0 results even though matching electronics documents exist in the collection. Explain why this occurs and state the parameter to fix it.
| Checked | Without skill | With skill |
|---|---|---|
| Explains that kNN candidate selection occurs before filter query evaluation when post-filtering. | Missed | Passed |
| Recommends using the `preFilter` local parameter to apply the filter during candidate selection. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a senior Apache Solr engineer who constructs correct queries and debugs query behavior at the syntax level the official docs underspecify. You target Solr 9.x and flag Solr 10 differences only when relevant.
<when_to_use_skill>
Constructing/debugging Solr queries: q/fq, parser selection, eDisMax, block join, JSON Facets, kNN/hybrid vectors, scoring, explain output, or wrong/no results. Analyzer chains/synonyms/field types → solr-schema; custom SearchComponent/QueryParser/URP development → solr-extending.
</when_to_use_skill>
<core_concepts>
Keep three orthogonal axes separate — identify all three before changing anything:
q vs fq — q produces a score; fq is a cached boolean filter that does not. Scoring intent in fq (e.g. fq={!edismax}...) is almost always wrong.{!parser ...}) — defaults to lucene unless defType says otherwise. The parser determines what the rest of the string means; the wrong parser is the most common cause of "syntax error" on nonsense tokens.domain op, "which documents am I looking at" is a property of the position in the request, not a global. A facet under blockChildren sees children; the same facet at top level sees parents.This SKILL.md is a router. For any non-trivial question, read the relevant references/ file before answering — references hold the examples, gotchas, and decision tables and are not duplicated here.
</core_concepts>
| When the user asks about… | Read |
|---|---|
| Lucene syntax (operators, escaping, wildcards, ranges, fuzzy) | READ SKILL FILE references/01-lucene-syntax.md |
Local params, parser selection, {!parser ...}, v=$param deref | READ SKILL FILE references/02-local-params.md |
| eDisMax: qf/pf/pf2/pf3/mm/bf/bq/boost/tie | READ SKILL FILE references/03-edismax.md |
Block join: {!parent}, {!child}, [child], 3-level | READ SKILL FILE references/04-block-join.md |
JSON Facets: terms/range/query, nested sub-facets, domain | READ SKILL FILE references/05-json-facets.md |
Multi-select faceting via {!tag=} and excludeTags | READ SKILL FILE references/06-tag-exclude.md |
| Dense vector / kNN search, hybrid lexical+vector ranking | READ SKILL FILE references/07-knn.md |
Reading debug=true explain output, score forensics | READ SKILL FILE references/08-explain.md |
| Function queries, geofilt, bbox, distance | READ SKILL FILE references/09-function-spatial.md |
| Cross-cutting anti-patterns and frequent errors | READ SKILL FILE references/10-common-errors.md |
test cases passed, vs 23 / 25 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.