Agent skill

Search UX

by Owl-Listener in Owl-Listener/designer-skills

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

MITAuto-check passed

Install Search UX

skills CLI
$ npx skills add Owl-Listener/designer-skills --skill search-ux -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Owl-Listener/designer-skills search-ux --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/interaction-design/skills/search-ux .claude/skills/search-ux && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
search-ux
GitHub stars
2.9k
Used in
1 other repo
Token cost
~1.1k tokens
SKILL.md length
571 words
Files
1
Skills in repo
107
Repo updated
First seen
Licence
MIT

At a glance

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

  • Users retrieve rather than browse
  • SKILL.md covers What You Do, Search Entry, Results and Filtering and Refinement, plus 3 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Search UX is an agent skill from Owl-Listener/designer-skills. Design search — query input, zero results, refinement, and result presentation. Use when users retrieve rather than browse. For browse structure, use navigation-patterns.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Designer Skills Collection: agentic skills, commands, and plugins for design — from research to systems, UI, interaction, and delivery. The licence is MIT.

When your agent uses it

  • Users retrieve rather than browse

Example prompts

  • “/search-ux”

What it can do on your machine

Read from SKILL.md and the folder at commit 9a6930c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Search UX loads about 1.1k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 571 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~46
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Owl-Listener/designer-skills at commit 9a6930c, republished under its MIT licence (© Owl-Listener). 571 words, ~1,079 tokens.

Download SKILL.mdSave it as .claude/skills/search-ux/SKILL.md (or your agent's skills folder).
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
Show full SKILL.md (244 more words)Show less

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

© Owl-Listener, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in interaction-design/skills/search-ux of Owl-Listener/designer-skills.

Open the folder on GitHubat commit 9a6930c

Used in 1 other repository

We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in Owl-Listener/designer-skills, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Search UX next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Search UX compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Search UX this skillOwl-Listener/designer-skills2.9k1 repos~1.1kAutomated safety check: PassMIT
Agent Refinementruvnet/ruflo74k2 repos~3.5kAutomated safety check: PassMIT
Refinewindmill-labs/windmill18k—~420Automated safety check: PassCustom licence
Refiner AutomationComposioHQ/awesome-claude-skills77k3 repos~730Automated safety check: PassNone
Search Inputthedaviddias/Front-End-Checklist74k—~402Automated safety check: PassMIT
Sparc Refineruvnet/ruflo74k—~1.5kAutomated safety check: NotesMIT

Similar skills

  • Agent Refinement

    ruvnet/ruflo

    Agent skill for refinement - invoke with $agent-refinement. An agent skill from ruvnet/ruflo.

    74k GitHub starsUsed in 2 repos~3.5k tokens
    DevelopmentAuto-check passed
  • Refine

    windmill-labs/windmill

    End-of-session reflection. An agent skill from windmill-labs/windmill.

    18k GitHub stars~420 tokensUpdated today
    Auto-check passed
  • Refiner Automation

    ComposioHQ/awesome-claude-skills

    Automate Refiner tasks via Rube MCP (Composio). An agent skill from ComposioHQ/awesome-claude-skills.

    77k GitHub starsUsed in 3 repos~730 tokens
    Productivity & AutomationAuto-check passed
  • Search Input

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Make search inputs accessible.

    74k GitHub stars~402 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed
  • Sparc Refine

    ruvnet/ruflo

    Run the SPARC Refinement and Completion phases — review code, improve test coverage, validate against specification, and generate documentation

    74k GitHub stars~1.5k tokensUpdated yesterday
    Testing & QAAuto-check: notes
  • Input Types

    thedaviddias/Front-End-Checklist

    A skill your agent uses when reviewing templates, rendered HTML, or shared components related to Use semantic input type attributes.

    74k GitHub stars~487 tokensUpdated 4 days ago
    Auto-check passed

More from Owl-Listener/designer-skills

All 107 skills in this repo
  • A B Test Design

    Owl-Listener/designer-skills

    Design an A/B experiment — hypothesis, variants, primary metric, and sample size.

    2.9k GitHub starsUsed in 1 repo~472 tokens
    Auto-check passed
  • Accessibility Test Plan

    Owl-Listener/designer-skills

    Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol.

    2.9k GitHub starsUsed in 1 repo~478 tokens
    Auto-check passed
  • Aesthetic Usability

    Owl-Listener/designer-skills

    Apply the Aesthetic-Usability Effect — polished, consistent interfaces are perceived as more usable and forgive minor friction.

    2.9k GitHub starsUsed in 1 repo~678 tokens
    Auto-check passed
  • Affinity Diagram

    Owl-Listener/designer-skills

    Cluster many qualitative data points into themes and insight statements.

    2.9k GitHub starsUsed in 1 repo~520 tokens
    Auto-check passed
  • Animation Principles

    Owl-Listener/designer-skills

    Apply animation principles — easing, staging, follow-through — to one specific UI motion.

    2.9k GitHub starsUsed in 1 repo~492 tokens
    Auto-check passed
  • Business Design

    Owl-Listener/designer-skills

    Read financials, map competitive landscapes, and argue design decisions in the language of value.

    2.9k GitHub starsUsed in 1 repo~1.1k tokens
    Auto-check passed

Questions about Search UX

What does Search UX do?

Design search — query input, zero results, refinement, and result presentation. Search UX is an agent skill from Owl-Listener/designer-skills. Design search — query input, zero results, refinement, and result presentation.

When should I use Search UX?

Search UX fits situations like: users retrieve rather than browse.

How do I install Search UX in Claude Code?

Run `npx skills add Owl-Listener/designer-skills --skill search-ux -a claude-code`. Or copy the skill folder (interaction-design/skills/search-ux in Owl-Listener/designer-skills) into .claude/skills/search-ux in your project. Claude Code loads it when a task matches its description.

How do I install Search UX in Codex?

Run `npx skills add Owl-Listener/designer-skills --skill search-ux -a codex`. Or copy the skill folder (interaction-design/skills/search-ux in Owl-Listener/designer-skills) into .agents/skills/search-ux in your project. Codex loads it when a task matches its description.

Can I use Search UX in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Owl-Listener/designer-skills --skill search-ux -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/search-ux, .gemini/skills/search-ux, .github/skills/search-ux and .opencode/skills/search-ux in your project.

What does Search UX need to run?

SKILL.md names no scripts, command-line tools or credentials: Search UX is instructions for the agent only.

Does Search UX access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Search UX safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Search UX use?

Search UX is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Search UX use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Search UX?

Skills that share tags, products or a category with Search UX: Agent Refinement (ruvnet/ruflo, 74k stars), Refine (windmill-labs/windmill, 18k stars), Refiner Automation (ComposioHQ/awesome-claude-skills, 77k stars) and Search Input (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Search UX?

Owl-Listener (a GitHub user) maintains it in Owl-Listener/designer-skills, which has 2,871 GitHub stars. The repository holds 107 skills in this directory. The repository was last updated on September 5, 2026.

Source: Owl-Listener/designer-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.