Methodology

The labeling policy behind every badge on this site.

Plugin ecosystems that are days old produce two failure modes: link farms full of dead repos, and "reviews" written by people who never ran the thing. This site exists to be the counter-example. Every entry carries exactly one of four statuses, and the status means what it says:

The four statuses

Tested — we ran it hands-on and published a field note with screenshots, commands or timings. The DeepSeek Harness onboarding walkthrough is the current example.

Install-tested — we installed it into a real DSH profile on our machine via the official CLI. The install log (including warnings) is public. Install-tested does not claim the plugin's features work — only that it installs and registers as described.

Install failed — we attempted an install on our machine and it failed. The error output is published verbatim. A failure is a real data point about the plugin and the ecosystem, not a reason to hide the entry.

Listed — curated from research, verified to exist as a public GitHub repo at listing time, but not yet touched by us. No hands-on claim is implied.

What we never do

Data freshness

Star counts, descriptions and push dates are pulled live from the GitHub API at build time — the refresh date is shown on the homepage. Our hands-on statuses are immutable facts with dates: a plugin marked Install failed on 2026-08-14 may work flawlessly next week, and we'll re-test and update rather than delete history.

Re-testing

Entries get re-tested when there's a reason to: a new release, a status-changing event, or a reader report. Updates are appended with dates, not silently rewritten.