Skip to main content
Agent skill

Deepseek Harness Setup

Install and operate Everything Claude Code (ECC) on the DeepSeek Harness (DSH): native skill roots (/.dsh/skills, .agents/skills), the @deepseek-ai/dsh-hooks-claude-code bridge for command hooks, bare-insert patch mounting, generator usage, event-support limits, and update workflow. Use when setting up ECC on DeepSeek Harness, wiring ECC hooks into a DSH profile, or debugging why ECC skills or hooks do not appear in a DSH session.

Get started

Get the complete skill folder, including its scripts and reference files.

When to use this skill

Use Deepseek Harness Setup when an AI agent needs a reusable SKILL.md workflow for this job: Install and operate Everything Claude Code (ECC) on the DeepSeek Harness (DSH): native skill roots (/.dsh/skills, .agents/skills), the @deepseek-ai/dsh-hooks-claude-code bridge for command hooks, bare-insert patch mounting, generator usage, event-support limits, and update workflow. Use when setting up ECC on DeepSeek Harness, wiring ECC hooks into a DSH profile, or debugging why ECC skills or hooks do not appear in a DSH session.

When not to use it

Skip Deepseek Harness Setup when the task is outside the coding category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.

How to install

Where will you use it?

Install scope
Claude Code folder setup
mkdir -p ~/.claude/skills/deepseek-harness-setup
# Save SKILL.md to ~/.claude/skills/deepseek-harness-setup/SKILL.md
  1. Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/deepseek-harness-setup/SKILL.md. For a shared project, commit the folder at .claude/skills/deepseek-harness-setup/ instead.
  2. Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
  3. For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.

Full install guide for Claude, Cursor, and Codex →

Try a starter prompt

After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.

Starter prompt
Use the Deepseek Harness Setup skill for this task: Installing ECC skills or hooks on a DeepSeek Harness install. Confirm any required inputs or files before making changes.

What supports this recommendation?

81/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
87/100
Practical detail
92/100
Source evidence
63/100
Source signals
72/100
Model compatibility evidence
  • claudeinferred

    The skill text mentions Claude or a closely associated term. This is keyword-derived compatibility; no hands-on model test is recorded.

  • chatgptuntested

    No model-specific signal or recorded compatibility test was found.

  • geminiuntested

    No model-specific signal or recorded compatibility test was found.

  • copilotuntested

    No model-specific signal or recorded compatibility test was found.

  • llamauntested

    No model-specific signal or recorded compatibility test was found.

  • perplexityuntested

    No model-specific signal or recorded compatibility test was found.

  • mistraluntested

    No model-specific signal or recorded compatibility test was found.

  • grokuntested

    No model-specific signal or recorded compatibility test was found.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

What this skill does

# DeepSeek Harness Setup

Run ECC on the DeepSeek Harness. Full guide: `docs/DEEPSEEK-HARNESS-GUIDE.md`.

## When to Use

- Installing ECC skills or hooks on a DeepSeek Harness install. - Deciding which ECC surfaces work on DSH and which do not. - Debugging a DSH session that does not show ECC skills or does not fire ECC hooks.

## How It Works

1. **Skills need no conversion.** DSH reads `SKILL.md` frontmatter (name/description) from native skill roots. Link the ECC catalog once:

```bash ln -s /path/to/ECC/skills/<skill-name> ~/.dsh/skills/<skill-name> ```

Root priority (project `.dsh` and `.agents` roots beat `~/.dsh`): skip linking skills whose names already exist in a higher-priority root. Substitute real skill names for the placeholders; the angle brackets are not shell syntax.

2. **Hooks go through the first-party bridge.** Generate a DSH-format config from the canonical ECC hooks file:

```bash node scripts/dsh/generate-hooks-config.js --ecc-root /path/to/ECC --out ~/.dsh/ecc/hooks-dsh.json ```

The generator lower-cases tool-name matchers, prefixes `CLAUDE_PLUGIN_ROOT`/`ECC_PLUGIN_ROOT` inline (the bridge does not export the plugin root), preserves timeouts, and skips events DSH cannot bridge: `PreCompact`, `PostToolUseFailure`, `SessionEnd`.

3. **Mount with a bare insert** in `~/.dsh/profiles/<profile>/cordis.patch.yml`:

```yaml - insert: - id: ecc-hooks-claude-code name: "@deepseek-ai/dsh-hooks-claude-code" config: configPath: /absolute/path/to/hooks-dsh.json ```

Loader rules that cost debugging time when learned the hard way: a plain `- id:` top-level entry is silently dropped; `insert` under an existing non-group id is rejected as "not a group"; first-party plugin packages need no profile `package.json` entry.

4. **Validate by composing, then verify live.**

```bash cd ~/.dsh && dsh --profile web --dump-config > /tmp/dump.yml grep ecc-hooks /tmp/dump.yml ```

Compose exit status stays 0 even when the loader drops or rejects an entry — those problems are only reported on stderr. Confirm the entry id appears in the dump and stderr is empty. A live GateGuard denial on the session's first edit/write/bash is the visible signal the bridge is active.

## Updating

`git pull` reflects into linked skills immediately; regenerate the hooks config with the same generator command. If the ECC checkout moves, regenerate (the path is embedded in every hook command) and relink skills.

## Limits

| Surface | Status on DSH | |---------|---------------| | Skills | Native discovery; workflows may require host adaptation | | Hooks | 23 command hooks on 5 of 7 bridge events | | Slash commands | Not available (Claude Code mechanism); workflows covered by skills | | Agents | Native dispatch unverified; use canonical prompt guidance only after review |

The validated setup here targets the CLI/web profile. Desktop profiles have a separate installation-owned runtime and skill discovery must be verified there independently. Generate hooks only from a reviewed ECC checkout; the linked checkout supplies their runtime.

Intended uses

  • Installing ECC skills or hooks on a DeepSeek Harness install.
  • Deciding which ECC surfaces work on DSH and which do not.
  • Debugging a DSH session that does not show ECC skills or does not fire ECC hooks.

Implementation notes

  • Review the source instructions and adapt inputs before running the workflow.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.