kgmkm/dsh-genspark

dsh-genspark

A plugin that brings Genspark's AI capabilities into DeepSeek Harness (DSH). Search, research, image/video/audio generation, media analysis, and social network search (X / Instagram / Reddit) can all be called from the composer with /genspark-* commands.

Japanese: README_ja.md

Getting started

1. Install the CLI and log in

npm install -g @genspark/cli
gsk login      # opens the browser → approve with your Genspark account
gsk me         # success if your email, plan, and remaining credits are shown

• Credentials are stored in ~/.genspark-tool-cli/config.json. This plugin never holds secrets (it only uses what the CLI has saved).

• On machines without a browser (CI, servers), you can authenticate with an API key instead.

  $env:GSK_API_KEY = "gsk_..."   # your Genspark API key
  

• To switch accounts, run gsk logout → gsk login.

• You can check the login state at any time with /genspark (or gsk me).

2. Install the plugin into a profile

powershell -ExecutionPolicy Bypass -File .\install-to-profile.ps1 -Profile "$env:USERPROFILE\.dsh\profiles\web" -Sync

To install it into the desktop app as well, run the same command against ...\.dsh\profiles\desktop.

3. Restart DSH

Reloading the page is not enough (the plugin is loaded only once, when the server starts). After restarting, run /genspark; if your account and remaining credits appear, you are ready to go.

Commands

Available from the composer's + menu, or by typing / at the start of a line. (When opening the menu with +, leave the input field empty — commands that take arguments only appear as suggestions when it is empty.)

Search and research

Create

Artifacts are saved to <working directory>/genspark-out/, and the save path and size are displayed.

Typical wait times (measured): images 15–40 s / audio 30–60 s / video 1–2 min (about 50 s for a 5-second 720p clip; longer videos take longer). Generation and analysis commands reply with "Sending to Genspark…" immediately after input, and the result arrives in the chat afterwards.

Understand

Social search

/genspark-social lets the AI decide which service to search and runs the appropriate search on X / Instagram / Reddit (the command itself calls no API, so credits are spent only on the searches that are actually performed).

• You can get the same results by asking the AI (e.g. "check what people say about Genspark on X" → genspark_x_search).
• By default, results show up to 25 items with author, date, reaction counts, and post URL (newest first).
• About 1.6 credits per call (measured). Instagram searches take 10–15 seconds, and Reddit's "post with comments" and "subreddit posts" can take around 40 seconds.
• On X, passing "@username" returns that user's posts, while passing a "topic" runs a post search. Instagram works the same way. Reddit accepts sort (top / new, etc.) and a time range.
• Search tips (measured): keep queries to 1–2 words / for Japanese topics use language="ja" (the AI adds it when you ask for results "in Japanese") / "#hashtags" do not narrow anything / on Reddit, naming a subreddit such as "in r/LocalLLaMA" tends to work better.
• If you see "failed to execute", it does not necessarily mean the feature is unsupported (transient failures do happen). The plugin retries automatically once. If it still fails, wait a while or change the wording.
• Comment fetching is often empty in practice (that is not a failure). Reddit search results do not include score (vote count), so results are ordered by date instead.

Advanced

Using attachments

The following 5 commands accept images, video, audio, and documents attached directly. When you attach something, the text in the input field is treated as the instruction or question.

Example: attach a photo of a cat and run /genspark-analyze-media What is it doing?

Choosing a generation model

Each command runs with a default model, but Genspark offers many models and you can switch between them.

How to use them:

• See the list — /genspark-models (filter by video, image, audio, transcribe, or part of an id)
• Ask the AI — "Which video models are available?" "List the audio models" → the AI returns the list via genspark_models
• Generate with a specific model — "Create a sunset video with gemini/veo3.1" → the AI runs it with the model argument set
• Model details — "Tell me the specs of kling/v3" → the AI reports supported aspect ratios, durations, and whether audio is available via get_model_info

Model names are not pinned in the plugin. The list is read from Genspark's catalog every time, so models that are added or retired are picked up automatically.

If you type "model list" or "usage" into a generation command (/genspark-image, /genspark-video, /genspark-audio), it returns the list or the usage without generating anything (no credits are spent). When you want to generate, just describe what you want.

Settings

You normally do not need to change anything. Only when necessary, add these to the plugin settings of your profile.

Replacing the built-in web_search (opt-in)

The built-in web_search asks the DeepSeek search API, so it needs a valid DeepSeek API key and fails every time when that key is missing or wrong (DeepSeek API error (HTTP 401)). With this option the same tool is answered by Genspark through the CLI you already use — the model keeps calling web_search, and only the backend changes.

Off by default. Nothing is registered and no setting is touched until you turn it on.

1. Open the Plugins panel in the sidebar (the same place the official Web search card lives) and find the Genspark web search card.
2. Turn on Use Genspark for web_search. Nothing else to do: the plugin registers a search provider with id genspark and points web.searchProvider at it. The change applies immediately (no restart).

The card is this package's browser half (lib/client.js). It has to be: the Web GUI has no page that renders a third-party plugin's schema by itself — a settings card is always a client-side contribution. The card appears only while the Host serves this plugin's settings namespace, so a profile without the plugin shows no trace of it.

To go back, turn the switch off. The selection is handed back — to the provider you had explicitly chosen before, or to the automatic one-provider selection.

How it works, and what it deliberately does not do:

• It uses ctx.web.registerSearchProvider(), the documented plugin API of @deepseek-ai/dsh-web. The two built-in DeepSeek backends are themselves ordinary plugins registering through the same call, so no DSH file is edited.
• web.searchProvider is a normal settings field — the same one the official Web search page writes. Turning the option off restores the previous value.
• web_fetch is not affected. The local HTTP fetch provider (dsh-web-fetch-http) ships with DSH base in both the desktop and the web profile, so fetching keeps working without any key.

Costs and trade-offs:

• Every search spends Genspark credits (the CLI bills per call) and waits for the gsk process to start — expect seconds, not milliseconds, per query.
• Failures are reported as WEB_PROVIDER_ERROR with the same wording the genspark_web_search tool uses (auth hint, timeout, raw stderr), so an error is never silently an empty result list.
• A query that returns nothing raises an error rather than an empty citation list.
• If you uninstall or disable the plugin while the option is still on, web_search will report WEB_PROVIDER_CONFIGURED_MISSING. Turn the option off before removing the plugin, or delete the searchProvider line from the profile patch afterwards.
• Prefer not to have the plugin write a setting? Set webSearch.autoSelect to false, then select the provider yourself with web.searchProvider: genspark in the profile patch or DSH_WEB_SEARCH_PROVIDER=genspark in the environment.

Troubleshooting

Learn more

• Tools (the functions the model calls), arguments, implementation notes, and verification steps → SKILL.md
• Design history and measurement records → ../docs/
• Changelog → end of SKILL.md