Ready to supercharge your AI agents?

Install any skill in seconds. Free to start, no credit card required.

Get Started Free →

Solr Schema · griddynamics | DecimalAI

databy griddynamics

Solr Schema

griddynamics/solr-schema

Source griddynamics/rosetta ↗License Apache-2.0

To design and audit Solr schemas: field types, analyzers, docValues, solrconfig.

SkillScore86Maintained

Automatic

Data Engineer pack

Last verified 8/20/2026

What it changes

Passed 19 of 22 test cases with the skill, and 18 of 22 without it.

Without skill82%

With skill86%

Checks it passed that the model alone missed

provides updated XML with SynonymGraphFilterFactory configured in the index analyzer
recommends placing SynonymGraphFilterFactory in the index analyzer rather than the query analyzer
explains that multi-word synonyms at query time disrupt phrase queries and minimum-should-match calculations

2 fixed17 passed either way2 still failing1 broke

Pass-rate lift: +5 pp
Tokens: +91%
Agent turns: 0%
Response time: -13%

Model gemini-3.6-flashMeasured 8/20/2026v119 of 22 cases passed with skill

Tokens, turns and time describe resource use, not a dollar price.

Use this skill

Save it into your project's skills folder. Claude Code picks it up in its next session.

curl -fsSL --create-dirs -o .claude/skills/griddynamics-solr-schema/SKILL.md https://app.decimal.ai/s/griddynamics-solr-schema/SKILL.md

Want it pinned and updatable? pip install "decimalai>=0.15", then decimalai skills add griddynamics-solr-schema, and start Claude Code with claude --plugin-dir "$(git rev-parse --show-toplevel)/.agents"

1 · One-time — install the CLI (docs ↗)

pip install "decimalai>=0.15"

2 · Get the skill — writes .agents/skills/griddynamics-solr-schema/ and pins it in .decimal/skills.lock

decimalai skills add griddynamics-solr-schema

No CLI? Get the same file — curl · raw file

curl -fsSL --create-dirs -o .claude/skills/griddynamics-solr-schema/SKILL.md https://app.decimal.ai/s/griddynamics-solr-schema/SKILL.md

Raw file: /s/griddynamics-solr-schema/SKILL.md ↗ · machine-readable summary at /s/griddynamics-solr-schema.json ↗

Safety checks: 3 of 3 passed

Code scan CleanIntent PassedContent Clean

See it in action

One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.

1 of 2

Prompt

We recently updated our Solr setup to support multi-word synonyms and soft commits, but we are seeing unexpected zero-hit query results and high CPU load during updates. Here are the relevant configuration snippets: ```xml <fieldType name="text_syn" class="solr.TextField"> <analyzer type="query"> <tokenizer class="solr.StandardTokenizerFactory"/> <filter class="solr.SynonymGraphFilterFactory" synonyms="synonyms.txt" expand="true"/> </analyzer> </fieldType> <autoSoftCommit> <maxTime>500</maxTime> </autoSoftCommit> ``` Please review these XML definitions and give us an audit report listing vulnerabilities in order of severity, explaining why they cause production issues, and supplying corrected XML configurations to resolve them.

What was checked, without and with the skill
Checked	Without skill	With skill
recommends placing SynonymGraphFilterFactory in the index analyzer rather than the query analyzer	Missed	Passed
explains that sub-second autoSoftCommit causes frequent cache invalidation	Passed	Passed
provides updated XML with SynonymGraphFilterFactory configured in the index analyzer	Missed	Passed

case-01 · gemini-3.6-flash · 8/20/2026 · answers are capped and redacted

What's inside

The instructions your model reads when the skill loads.

SKILL.md102 lines9 files

You are a senior Apache Solr engineer who audits existing schemas/solrconfig and designs new ones from a domain description. You focus on field-type, analyzer, docValues, synonym, and solrconfig decisions that quietly break relevance, faceting, or indexing in production. You target Solr 9.x and flag Solr 10 differences only when relevant.

<when_to_use_skill>

Audit/design a managed-schema/schema.xml/solrconfig.xml, or field types, analyzer chains, docValues/stored/indexed choices, and synonyms for a new collection. Triggers: fieldType, tokenizer/filter/analyzer, docValues, synonyms, schemaless, the Schema REST API, "review/audit my schema", "design field types for…". Query construction/debugging (eDisMax, faceting, kNN, explain output) → solr-query skill. Custom plugin code (SearchComponent, QueryParser, URP, DocTransformer, ValueSource) → solr-extending skill. Tagging/graph semantic-search architecture → solr-semantic-search skill. This skill stops at the schema and solrconfig layer.

</when_to_use_skill>

<core_concepts>

This skill operates in two modes:

Mode A — Audit. The user pastes a managed-schema/schema.xml and/or solrconfig.xml, or gives a running-Solr URL. Walk the audit checklist in severity order, cite the specific field/element, explain the impact, and give corrected config. If only a URL is available (no files), pivot to live inspection — READ SKILL FILE references/07-live-inspection.md.
Mode B — Design. The user describes a domain. Produce field-type / analyzer / docValues / synonym recommendations plus a concrete managed-schema fragment, justifying each indexed/stored/docValues choice against the field's actual use (search vs. facet vs. sort vs. display vs. function).

Three orthogonal axes must be decided per field, never globally:

Analysis — exact-match (string, one opaque token) or full-text (text_*, a token stream from an analyzer chain)? Picking string for searchable prose, or text_general for an id/facet value, is the single most common schema error.
Storage triad — indexed (search/filter), stored (returns original value), and docValues (fast facet/sort/function/group) are independent. Defaulting all three to true wastes disk and memory.
Index vs query symmetry — index- and query-time analyzer chains can legally differ; small divergences (a filter on one side only, multi-word synonyms at query time) cause silent zero-hit failures with no error.

This SKILL.md is a router. For any non-trivial question, read the relevant references/ file before answering — references hold the examples, decision tables, and gotchas and are not duplicated here.

</core_concepts>

When the user asks about…	Read
Field type selection; `string` vs `text_general` vs `text_en`; tokenizers + filter chains	READ SKILL FILE `references/01-field-types.md`
Index vs query analyzer asymmetry; detecting silent misses	READ SKILL FILE `references/02-analyzer-asymmetry.md`
`indexed`/`stored`/`docValues` triad; `useDocValuesAsStored`; facet/sort/function needs	READ SKILL FILE `references/03-docvalues-stored-indexed.md`
Synonyms: `SynonymGraphFilter`, index vs query placement, `synonyms.txt` vs managed	READ SKILL FILE `references/04-synonyms.md`

Track record

Benchmark

19 / 22

test cases passed, vs 18 / 22 without

Adoption

Users: 0
Times used: 0

Safety and source details

SkillSafety

✓ 3 of 3 passed

Code scan15 of 15 checks clean

0 critical · 0 warning · 0 info — scanner v4 — 8/3/2026

View 15 scanner checks

live_secretremote_code_executionreverse_shelldata_exfiltrationssrf_metadataagent_snoopinganti_refusaldestructive_commandsobfuscated_unicodeunicode_homoglyphopaque_blobsuspicious_urltool_overreachtrigger_abuseprompt_injection_phrasing

IntentSafe

LLM judge · does the skill do what it claims

ContentClean

LLM judge · policy & harmful-content review

Source

Imported

griddynamics / rosetta

plugins/core-antigravity/skills/solr-schema/SKILL.md

View on GitHub ↗

License Apache-2.0Imported 8/26/2026Version v1Bundled 8 files

More skills from the same source and nearby in the registry, with their headline benchmark lift.