Search UX design: query input, zero-results states, and result presentation
Forgiving autocomplete, search-as-navigation, results layouts and relevance ranking, faceted refinement, zero-results retention design, and search analytics (queries, refinements, abandonment)
- What
- Forgiving autocomplete, search-as-navigation, results layouts and relevance ranking, faceted refinement, zero-results retention design, and search analytics (queries, refinements, abandonment)
- Cost
- Free
- Needs
- a product with search (or one being built) to design or review — the skill is guidance the agent follows, not software to install
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @owl-listener's search-UX skill: design the full retrieval experience — forgiving entry (descriptive placeholders, width signaling query length, autofocus, Enter-to-submit, clear/reset, completions after 2-3 characters with recents → trending → predicted, 5-8 suggestions max per Hick's Law, keyboard navigation, query-term highlighting) — search-as-navigation (navigational destinations in suggestions, exact-match pages first, never "no results" for destinations that exist), results presentation (list vs grid vs grouped-by-type, result counts, matched-field signaling, decision-enough snippets), ranking (recency, popularity, exact-title match, personalization with surfaced sort logic), faceted refinement (context-relevant filters with counts, individually removable, clear-all), the zero-results state treated as a retention moment (confirm the query, typo corrections, broader terms, browse/support alternatives — never a blank page), and search analytics (top queries, zero-result queries, refinement rate, click position, abandonment). Honest caveats: methodology only — it doesn't implement the search backend, only its UX; keep it on mobile too (search is often primary navigation there). MIT licensed. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Quick answer
Search UX design: query input, zero-results states, and result presentation is a free Muse skill that helps your Muse design the full retrieval experience, from forgiving autocomplete and search-as-navigation to results layouts, relevance ranking, faceted refinement, zero-results retention design, and search analytics covering queries, refinements, and abandonment.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 9a6930cStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: a product with search (or one being built) to design or review — the skill is guidance the agent follows, not software to install Install "Search UX design: query input, zero-results states, and result presentation" for me. It gives my agent @owl-listener's search-UX playbook: forgiving query input and autocomplete, search-as-navigation patterns, results layouts and ranking, faceted refinement, zero-results retention design, and search analytics (top queries, zero-result queries, refinement rate, click position, abandonment). MIT licensed. Repository: https://raw.githubusercontent.com/owl-listener/designer-skills/9a6930cf84a822eb458624bd11c61aac5bbdf224/interaction-design/skills/search-ux/SKILL.md Pinned version: install the code at commit 9a6930cf84a822eb458624bd11c61aac5bbdf224 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "search-ux". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. point the agent at the search experience to design or review; it covers the UX only, not the search backend — implement ranking and indexing separately). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 9a6930c · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.