dsh plugin market search: 5 ways to find a plugin

Two failures explain most "missing plugin" reports in dsh plugin market: the query was written in a form the index does not match, or the category filter never left Installed. A single plugin can have a Chinese name, an English name, a package name, a topic and an author, and only some of those strings are searchable from the toolbar. This article puts all five forms in one table, then walks from broad to narrow and ends with a recovery order for genuine zero-result searches (DSH Plugin Hub 2.2.5 index).

dsh plugin market search: one table for five query styles

A Chinese name suits "I know what it is called", an English name suits "I know roughly what it does", a package name suits "I know where it comes from", a topic suits "I only know the function", and author or category suits "I want to browse by source or field". The five styles are not mutually exclusive; combining them from broad to narrow beats swapping synonyms.

The toolbar that hosts all of this is described in your first five minutes in dsh plugin market, including the four tabs around the search box.

DSH plugin market search way 1: the Chinese name is a probe, not a guarantee

A Chinese name only matches when the card's display name is Chinese; if the display name is English, the Chinese wording may live only in the description and never reach the search index.

1. Type the phrase you would naturally use — the Chinese word for memory, theme or search.
2. Look at the result count. If it is zero, stop trying Chinese synonyms and switch to English immediately.
3. If several unrelated plugins appear, narrow with the category filter to the matching field, such as Memory or UI.
4. Open a detail view and confirm that the Chinese term in the description refers to the same plugin you have in mind.

Treat the Chinese query as the first probe. Its value is confirming what the thing is called locally, not guaranteeing a hit.

DeepSeek Harness search way 2: an English function word, never a sentence

The English query works when it is a single noun — memory, search, theme, office — not a sentence such as "a plugin that remembers things".

1. Compress the need into one English noun: long-term memory becomes memory, web lookup becomes search.
2. If the result count is too high, add a second word to narrow it, for example memory session or search web.
3. If the count collapses to almost nothing, remove the second word and keep the function word alone.
4. When a near-match appears, open its detail view and read the package name; the package name is usually more stable than the display name.

This style fits the stage where you know the job but not the product name. It hits more often than Chinese, but prefixes, plurals and hyphens can still break it.

dsh plugin market search way 3: the package name is exact and unforgiving

A package name is the unique identifier, so it is the most precise query and also the easiest to mistype: one wrong character in dsh-, @scope/ or a hyphen returns zero.

1. If you copied a package name from GitHub or a recommendation, paste it verbatim; do not add a dsh- prefix yourself.
2. If you only remember the tail, search the tail first — memory rather than a guessed full name — then read the complete package name from the results.
3. For scoped packages, include @scope/ in the query; searching only the part after the slash matches too many unrelated packages.
4. After a hit, open the detail view and compare the package name with the source repository so you do not install a same-named package from a different author.

Package search is about precision, not volume. Search one package name at a time and keep function words out of the same query.

DeepSeek Harness search way 4: topics when you only know the job

A topic describes what a plugin can do, which makes it closer to your actual need than a display name; searching mcp is more reliable than searching "MCP plugin".

1. Translate the need into one topic word: MCP becomes mcp, memory becomes memory, office documents become office, visual themes become theme.
2. Enter the topic and read the result count first. A large count means the field is crowded and needs a scenario word.
3. Open a detail view and confirm the topic matches the description; some plugins carry several topics, so do not judge by the first one.
4. If the topic returns nothing, fall back to the English name and narrow with the category filter.

Topics travel across languages, which is why an English topic still works for a Chinese-speaking user. It is the best entry point when the function is clear but the name is not.

DSH plugin market search way 5: author and category for source-first browsing

Author names are not guaranteed to be searchable card fields but categories always are, so browse by category first and verify the author inside the detail view.

1. Pick a large category such as Memory, UI or Tools and scan what exists in that field.
2. Sort the results by Recent or Star to move the plausible candidates to the front.
3. Open a detail view and read the source repository; if the owner is one you trust, return to the search box and try the author or repository name.
4. If the author query still fails, stop fighting it and keep using category plus the repository link from the detail page.

This is the broadest of the five styles. It suits "I want something from this team or this field", not "I know the plugin name". For more on browsing, see what dsh plugin market is and plugin search tips.

Recovery order when dsh plugin market returns nothing

Check the filter first, then spelling, then language, and only last suspect that the plugin was never listed; reversing that order wastes time on keywords.

1. Clear the search box and set the category back to All, confirming that Installed was not hiding the result.
2. Change the form: Chinese, then English, then package name, then topic — one attempt each.
3. Check spelling: the dsh- prefix, hyphens, plurals and any @scope/ segment.
4. Search GitHub for a repository under the same name and confirm the plugin is published and tagged with the dsh-plugin topic.
5. If GitHub has it but the market does not, it is simply not indexed yet; use Custom Install or wait for listing instead of cycling more keywords.

Notes: four query mistakes to avoid

1. Do not search with a full sentence. The box is not semantic search, and long phrases usually match nothing.
2. Do not search only in Chinese. Many display names are English, with Chinese confined to descriptions.
3. Do not ignore the category filter. Under Installed, a new plugin is guaranteed to return zero.
4. Do not install the moment you find it. Check package name, source repository, permissions and dependencies before you decide.

The five styles are not a checklist to run every time. Move down the ladder — Chinese name, English name, package name, topic, category — and most plugins appear within the first two steps. When they do not, the recovery order is far more useful than another synonym.