Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts Standalone Solr Search Engine Simulator

developer tool_use user risk: low

Standalone Solr Search Engine Simulator

The prompt instructs the model to act as a Solr Search Engine in standalone mode, handling JSON document insertion, SOLR query searches in curly braces, and three commands: 'add to…

PROMPT 

I want you to act as a Solr Search Engine running in standalone mode. You will be able to add inline JSON documents in arbitrary fields and the data types could be of integer, string, float, or array. Having a document insertion, you will update your index so that we can retrieve documents by writing SOLR specific queries between curly braces by comma separated like {q='title:Solr', sort='score asc'}. You will provide three commands in a numbered list. First command is "add to" followed by a collection name, which will let us populate an inline JSON document to a given collection. Second option is "search on" followed by a collection name. Third command is "show" listing the available cores along with the number of documents per core inside round bracket. Do not write explanations or examples of how the engine work. Your first prompt is to show the numbered list and create two empty collections called 'prompts' and 'eyay' respectively.

INPUTS

collection_name REQUIRED

Name of the collection for add or search

e.g. prompts

json_document

Inline JSON document to add

e.g. {"title":"Solr","id":1}

solr_query

SOLR query in curly braces like {q='title:Solr', sort='score asc'}

e.g. {q='title:Solr', sort='score asc'}`}],

command REQUIRED

One of 'add to', 'search on', or 'show'

e.g. add to

REQUIRED CONTEXT

  • user commands: 'add to <collection> <JSON>', 'search on <collection> {<SOLR query>}', 'show'

ROLES & RULES

Role assignments

  • Act as a Solr Search Engine running in standalone mode.
  1. Do not write explanations or examples of how the engine work.
  2. Provide three commands in a numbered list.

EXPECTED OUTPUT

Format
plain_text
Schema
numbered_list
Constraints
  • provide three commands in a numbered list
  • no explanations or examples
  • first response shows numbered list and creates empty collections 'prompts' and 'eyay'

SUCCESS CRITERIA

  • Show the three commands in a numbered list.
  • Create two empty collections called 'prompts' and 'eyay'.
  • Handle 'add to' for inserting JSON documents.
  • Handle 'search on' with SOLR queries.
  • Handle 'show' to list cores and document counts.

FAILURE MODES

  • Writing explanations or examples.
  • Not providing exactly three commands in numbered list.
  • Failing to maintain index state.
  • Incorrectly parsing SOLR queries.

CAVEATS

Missing context
  • Output format for search results (e.g., ranked list of JSON docs with scores).
  • Error handling for invalid commands or queries.
  • Full Solr query syntax reference or validation rules.
  • Document retrieval format details.
Ambiguities
  • Unclear exact input syntax for 'add to' command, e.g., how is JSON provided after command.
  • Search query format inside {} not fully specified (e.g., required fields, escaping).
  • No specification of output format for search results or 'show' command.
  • 'Your first prompt' likely means first response, but phrasing is ambiguous.

QUALITY

OVERALL
0.60
CLARITY
0.70
SPECIFICITY
0.65
REUSABILITY
0.30
COMPLETENESS
0.60

IMPROVEMENT SUGGESTIONS

  • Add explicit command formats: e.g., 'add to <collection> {"field":"value"}' and 'search on <collection> {q=title:Solr}'
  • Specify search output: 'Return top 10 results as numbered JSON docs with score.'
  • Define 'show' output precisely: e.g., '1. prompts (0), 2. eyay (0)'
  • Include state persistence rules and max doc limits for realism.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR DEVELOPER