FAQ

DeepSeek Plugin Questions

Practical answers about discovery, trust, compatibility, installation, removal, publishing, and this directory's data boundaries.

01What does “DeepSeek plugin” mean on this site?

It means a community extension intended for the DeepSeek Harness plugin system. It does not include every package that calls the DeepSeek API, every editor extension with DeepSeek support, or plugins for unrelated frameworks.

02Is DeepSeekPlugins an official DeepSeek website?

No. DeepSeekPlugins is an independent community directory. DeepSeek AI owns and maintains the official DeepSeek Harness repository.

03Are listed plugins reviewed or safe?

A listing confirms only that the record passed the directory data validator or exists in the local reviewed snapshot. It does not certify code safety, identity, compatibility, production readiness, or install success.

04Why can a plugin break after a Harness update?

The official Harness repository currently describes the project as a developer preview with expected compatibility-breaking changes. Test an exact Harness revision and plugin revision together.

05What are profiles and bundles?

A profile is a named Harness runtime configuration. A bundle is an installable group of plugin configuration. Community install commands often target the Web profile so the plugin is added to that specific runtime setup.

06How do I install a plugin?

Open the plugin detail page, inspect the linked repository and its manifest, then use the maintainer-approved source and version. The directory displays the command recorded by the registry and does not run it for you.

07How do I remove a plugin?

Follow the current Harness CLI and the repository's removal instructions. Before installation, check whether the plugin creates files, modifies profile configuration, launches processes, stores data, or requires a separate cleanup step.

08Why do some fields say that data is unavailable?

The community registry supplies a compact discovery record. Rich fields such as forks, language, license, and source activity are included only when captured in the local repository snapshot or supplied by a validated source.

09How are Popular picks selected?

The search landing page shows a small curated set ordered by available repository visibility while keeping category coverage useful. It is a discovery aid and carries no safety or quality judgment.

10Why are Use Cases used instead of Occupations?

The current DSH registry does not include creator occupations or a formal job taxonomy. Use Cases group real plugin categories around user tasks without inventing creator professions.

11How can I publish a plugin?

Follow the official plugin development and publishing guides, document your bundle and configuration, add the dsh-plugin GitHub topic, and follow the contribution process of the community registry.

12Can I use the catalog in another product?

The public JSON endpoint is available for lightweight discovery use. Preserve provenance and fallback status, link to source, cache politely, and do not imply endorsement or security certification.