DeepSeek Harness: contribute

The source of truth is github.com/deepseek-ai/deepseek-harness. Use Discussions for questions, Issues only if the project currently accepts them, and pull requests that match the repo’s contributing notes.

Developer preview means APIs break. Pin the version you tested, quote the exact CLI error, and include Node.js version (^22.19.0 or >=24.0.0 per upstream). Do not paste API keys.

Official product copy also lives on deepseek.com/harness. This community site is not a second official channel.

If you are adding a tool, skill, skin, or provider, ship a package — do not wait for this portal to “list you”.

1. Follow the plugin guide (Cordis register + disposer, document secrets and filesystem scope).
2. Add GitHub topic dsh-plugin when the repo is meant to be discovered.
3. Prefer dsh plugin add github:owner/repo in the README so operators can copy one line.
4. Test in Minimal or Creative before you tell people to load it in Standard.

We may later add a rewritten card to the curated community plugins list. Curation is slow on purpose: we will not scrape thousands of thin pages. Full discovery remains the GitHub topic.

harness-ds.com rewrites install, modes, comparison, and SEO-oriented explainers. If a command here lags GitHub README, the README wins.

Useful contributions: broken trailing-slash links, locale mistakes (especially zh-tw vs zh-cn), outdated npx flags, and missing internal links. Do not send us “generated” pages that copy dshbase or official docs verbatim.

We are not affiliated with DeepSeek or Hangzhou DeepSeek. Do not imply that a merged docs PR here is an official product decision.

No fake contributor rankings, no paid “verified author” slots, no AggregateRating stars, and no screenshots that claim unpublished benchmarks. If you need a people directory, use GitHub commit graphs and topic pages — those update themselves.

Next: install, plugin guide, UI skins.