SkillAgentSearch skills...

search-ux

Design search — query input, zero results, refinement, and result presentation

Install / Use

npx skills add Owl-Listener/designer-skills --skill search-ux

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

80/100

Supported Platforms

Universal

Our assessment of search-ux

search-ux scores 80/100 on our quality scale, 3637th of 4,700 Development & Engineering skills we index.

Its SKILL.md is 4.2 KB long, well organised into 14 sections and no code examples: a solid amount of guidance for an agent.

With 2,736 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
13/20
Description
12/15
Adoption
15/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated about 2 months ago, so search-ux is actively maintained.
  • Our last check on 2026-11-08 found the source still online.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

search-ux compared with similar skills

All 4 of these similar skills score higher than search-ux; compare them before choosing.

SkillScoreStarsUpdatedFormat
search-ux (this skill)by Owl-Listener802.7k2mo agoSKILL.md
taste-skillby Leonxlnx100116.8k8d agoCLAUDE.md
ai-job-searchby ai-job-search-dev10072.1ktodayCLAUDE.md
claude-howtoby luongnv8910047.3k2d agoCLAUDE.md
Claude-Code-Game-Studiosby Donchitos10039.7k7d agoCLAUDE.md

Frequently asked questions

How do I install search-ux?
Run npx skills add Owl-Listener/designer-skills --skill search-ux. The install tabs above show the steps for each supported agent.
Which AI agents does search-ux work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is search-ux safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is search-ux still maintained?
The repository was last updated about 2 months ago, so search-ux is actively maintained.

name: search-ux description: Design search — query input, zero results, refinement, and result presentation. Use when users retrieve rather than browse. For browse structure, use navigation-patterns.

Search UX

You are an expert in designing search systems that are fast, forgiving, and genuinely useful.

What You Do

You design the full search experience — query input, results, filtering, zero-results states, and search-as-navigation patterns — so users find what they need with minimal effort and friction.

Search Entry

The Search Input

  • Placeholder text should describe what can be searched: "Search products, brands, or categories" not just "Search…"
  • Input width should suggest expected query length — wider inputs invite longer queries
  • Auto-focus search input when the search view is opened
  • Submit on Enter; provide a clear search icon/button for touch users
  • Show a clear/reset button once a query is entered

Autocomplete and Suggestions

  • Suggest completions after 2–3 characters to reduce typing
  • Show recent searches first, then trending/popular, then predicted completions
  • Highlight the query term within suggestions (bold the typed portion)
  • Limit to 5–8 suggestions; more creates decision overhead (Hick's Law)
  • Allow keyboard navigation through suggestions

Search-as-Navigation

Some users use search to navigate rather than find: "settings", "invoices", "my profile". Design for this:

  • Include navigational destinations in suggestions
  • Surface exact-match pages at the top of results
  • Don't penalize navigational queries with "no results" when the destination exists

Results

Results Layout

  • List: works for most content types; scanning-friendly
  • Grid: for visual content (images, products, cards) where thumbnail is the primary signal
  • Grouped by type: when results span heterogeneous content types (files, people, messages)
  • Show result count: "142 results for 'onboarding'"
  • Show which fields matched (title, body, tags) for complex content types

Result Items

Each result should show:

  • Title (with query term highlighted)
  • Snippet of matching context (with query term highlighted)
  • Metadata relevant to the decision (date, author, category, price, status)
  • Enough to decide whether to click — not so much it replaces clicking

Ranking and Relevance

  • Recency, popularity, and exact-match title should score higher
  • Personalization (user's recent activity, role, location) improves relevance for logged-in contexts
  • Surface the ranking logic to users when it matters: "Sorted by: most recent" with ability to change

Filtering and Refinement

  • Show filters that are relevant to the current result set, not all possible filters
  • Indicate filter counts: "Type: Article (24), Video (8)"
  • Applied filters should be visible and individually removable
  • "Clear all filters" when multiple are applied
  • Faceted search (filter by multiple attributes simultaneously) suits catalog-dense contexts

Zero-Results State

The most critical and most often neglected state:

  • Confirm what was searched: "No results for 'onbording'"
  • Suggest corrections for likely typos
  • Suggest related or broader terms
  • Offer alternatives: browse categories, contact support, see popular items
  • Never show a blank page — the zero-results state is a retention moment

Search Analytics

  • Top queries: what are users searching for? Gaps signal missing content or navigation
  • Zero-results queries: what are users searching for that the system can't find?
  • Refinement rate: how often do users modify their query or apply filters?
  • Click position: which result position is clicked most? Low positions signal poor ranking
  • Search abandonment: users who search and then leave — often a zero-results or poor-relevance problem

Best Practices

  • Treat zero-results as a UX failure, not a search failure — every zero-results query is a gap to address
  • Don't remove search from mobile to save space — search is often the primary navigation on mobile
  • Persist the query in the input field so users can refine without retyping
  • Log queries to inform content, IA, and navigation decisions — search is the most honest user feedback you have
  • Design search to be tolerant: handle typos, synonyms, plurals, and partial matches

Related Skills

View on GitHub
GitHub Stars2.7k
CategoryDevelopment
Updated2mo ago
Forks388

Languages

Markdown

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions