Plugin directory / Developer / dshbase-catalog
dshbase-catalog
Verified · install-tested on dsh ylwl1997
What it does
Search the dshbase plugin directory from inside DSH — find plugins by keyword, get install commands and test status.
Works — verified, early-stage project
Search the dshbase plugin directory from inside DSH — find plugins by keyword, get install commands and test status. It installs cleanly and boots without issues in our testing. It's early-stage but functional.
“Verified” means our automated CI actually ran dsh plugin add in a clean profile and it booted — nothing more. Feature descriptions and version compatibility are the author’s claims. This is not a security audit and not an endorsement of third-party code.
README
dshbase-catalog
Query the dshbase plugin directory from inside DeepSeek Harness 锟斤拷 search, list, and get install commands for 1,100+ community plugins without leaving your session.
Install
dsh plugin add dshbase-catalog
Tools
| Tool | Description |
|---|---|
search_dsh_plugins |
Full-text search across plugin name + description |
get_dsh_plugin |
Look up one plugin: install command, verification status, stats |
list_dsh_plugins |
List plugins by category |
get_dsh_stats |
Catalog totals (plugins, npm vs git, verification) |
get_dsh_categories |
All categories with counts |
Data
The catalog snapshot is regenerated daily from the live dshbase directory (see scripts/sync-catalog.py), so the built-in index stays current.
License
MIT
Install
Web profile:
dsh plugin --profile web add dshbase-catalog Headless (CLI) profile:
dsh plugin --profile headless add dshbase-catalog Package
npm: dshbase-catalog · version 0.1.0 · tested on dsh 0.1.0-rc.6
Test report
Verified end-to-end: L1 install + L2 load + L3 runtime Q&A on dsh 0.1.0-rc.6.
When to use it
Extend the agent's coding surface — give it a new tool, workflow, or integration so it handles a dev task it couldn't before.
Who it's for
Developers who want dsh to behave like a teammate on real codebases — editing, running, and verifying changes rather than just answering.
For developers — extending it
The tool/command surface is the seam: expose more of the SDK, add smarter context wiring, or tighten the loop between code changes and verification.