Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/griddynamics/rosetta/solr-schemanpx skills add griddynamics/rosetta --skill solr-schemagit clone --depth 1 https://github.com/griddynamics/rosettaWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/griddynamics/rosetta/solr-schema)<a href="https://agentmods.dev/skills/griddynamics/rosetta/solr-schema"><img src="https://agentmods.dev/badge/skills/griddynamics/rosetta/solr-schema.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.02174 |
| Opus 5 | $0.00013 | $0.01087 |
| Sonnet 5 | $0.00005 | $0.00435 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
solr-schema scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.xmland/orsolrconfig.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 FILEreferences/07-live-inspection.md. - Mode B — Design. The user describes a domain. Produce field-type / analyzer / docValues / synonym recommendations plus a concrete
managed-schemafragment, justifying eachindexed/stored/docValueschoice 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)? Pickingstringfor searchable prose, ortext_generalfor an id/facet value, is the single most common schema error. - Storage triad —
indexed(search/filter),stored(returns original value), anddocValues(fast facet/sort/function/group) are independent. Defaulting all three totruewastes 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 |
solrconfig.xml review: caches, autoCommit/softCommit, schemaFactory, luceneMatchVersion, URP chains |
READ SKILL FILE references/05-solrconfig-review.md |
| Anti-pattern catalog + Solr 9.x version-compat | READ SKILL FILE references/06-anti-patterns.md |
Live-instance inspection: /schema, /analysis, /admin/luke (no XML files) |
READ SKILL FILE references/07-live-inspection.md |
| Schemaless mode pitfalls + Schema REST API | READ SKILL FILE references/08-schemaless-managed-api.md |
<audit_checklist>
Mode A spine — walk in order; earlier items cause the loudest production failures.
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- README.md 8.1 KB
- references/01-field-types.md 8.7 KB
- references/02-analyzer-asymmetry.md 11 KB
- references/03-docvalues-stored-indexed.md 8.5 KB
- references/04-synonyms.md 9.1 KB
- references/05-solrconfig-review.md 14 KB
- references/06-anti-patterns.md 8.8 KB
- references/07-live-inspection.md 8.4 KB
- references/08-schemaless-managed-api.md 11 KB
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago First seen · 116 lines · 25 tokens per session scan A f983a88dd990
solr-schema is a skill published in the GitHub repository griddynamics/rosetta (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 2,174 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
azure-devops-rest-api
Guide for working with Azure DevOps REST APIs and OpenAPI specifications. Use this skill when implementing new Azure DevOps API integrations, exploring API capabilities, understanding request/response formats, or referencing the official OpenAPI specifications from the vsts-rest-api-specs repository.
decision-mapping
Turn a loose idea into a sequenced map of investigation tickets, then drive them to resolution one at a time.
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.
memorix-orchestrate
Use when a main agent needs Memorix to coordinate explicit subagent work through tasks, handoffs, messages, file locks, or the orchestrate CLI.