Why classification matters
The `dsh-plugin` topic is a discovery signal, not a package format or compatibility test. A repository can use the topic for a native extension, a guide, a theme, an adjacent application, or an experiment that no longer matches the current harness.
DSHub uses separate relationship and category fields so users can distinguish what a project does from how strongly its DSH compatibility is supported.
Relationship labels
- Official: maintained by the official project owner and used as a primary reference.
- Plugin: has a documented install path and evidence that it extends a recognized harness surface.
- Compatible: works with dsh through a documented integration but is not presented as a native plugin.
- Ecosystem: relevant to dsh users, while native compatibility remains unverified or is not the project’s main purpose.
Category labels
- Agents coordinate goals, tasks, or multi-step execution.
- Skills package reusable instructions or domain behavior.
- Tools expose an external capability or data source.
- Interfaces change how users inspect or control the harness.
- Sandboxes isolate files, processes, or execution environments.
Automatic discovery is intentionally separate
New GitHub candidates enter a review queue first. Automated signals help prioritize review, while human-maintained evidence controls whether a candidate becomes a published plugin or compatible-project listing.