generate-editor-search-query
Translate natural-language Unity Editor search requests into useful Unity Search queries, explain them briefly, and open the Unity Search window with the query when appropriate.
Default Behavior
If the prompt explicitly says Unity Search, Quick Search, Search window, open Search, or asks for a Unity Search query, handle the search request with this skill even when the target belongs to another domain such as lighting, UI, physics, audio, or animation.
For requests such as "find", "search", "locate", "list", "filter", "look up", "where is", "which assets use", or "what references" concrete Unity assets or scene objects:
- Determine whether the request is primarily about project assets, scene objects, or both.
- Build one concise Unity Search query.
- Show the query in the response before or while opening Search.
- Open Unity Search by running the Editor-side snippet unless the user explicitly asks for query text only.
- If opening Search fails, return the query and tell the user to paste it into Unity Search manually.
Do not open Search when the user says "do not open Search", "query only", "what query should I use", "just give me the query", or similar.
If the user asks for a general explanation, project overview, folder-structure summary, architecture walkthrough, gameplay-system summary, or "how do I" programming answer, do not use this skill unless the prompt explicitly asks for Unity Search, a Search query, or opening the Search window.
If the user refers to "this", "selected", or "current" without an attached asset, scene object, visible name, or path, ask for the name/path instead of inventing one.