Skip to content
Back to skills

Code Mate Deepseek Harness

ASecurity

Runs DeepSeek Harness headlessly for bounded repository tasks. Use when the user asks to delegate analysis or implementation to DeepSeek Harness.

  • 52,355 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added September 2, 2026
ai-agentsbashapi

Works with

  • api

Security analysis

A100/100

Scanned September 2, 2026

npx -y skills add CherryHQ/cherry-studio --skill code-mate-deepseek-harness --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Code Mate Deepseek Harness?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Code Mate Deepseek Harness
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cherryhq-code-mate-deepseek-harness/badge)](https://www.skillsdirectory.com/skills/cherryhq-code-mate-deepseek-harness)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: code-mate-deepseek-harness
description: Runs DeepSeek Harness headlessly for bounded repository tasks. Use when the user asks to delegate analysis or implementation to DeepSeek Harness.
---

# DeepSeek Harness

## Run

1. Set the Bash working directory to the exact project the user named and set a finite timeout, normally 10 minutes.
2. Check availability with `command -v dsh`. If it is missing, stop and ask the user to install DeepSeek Harness in Code Mate.
3. Run one headless task:

```bash
dsh --profile headless "<prompt>"
```

Pass the prompt as one quoted argument. Treat stdout as final text, not JSON. Exit zero means success; exit one means the task failed or did not complete. Never start the interactive UI or a login flow.

## Authentication And Permissions

If DSH reports a missing provider, model, or API configuration, stop and ask the user to configure DeepSeek Harness in Code Mate. Never request, read, print, or copy credentials.

Headless DSH can write to the workspace and creates a persistent session. For read-only work, explicitly tell it not to modify files and inspect the repository diff afterward. Allow modifications only when the user explicitly requested workspace changes, and restrict the working directory to the intended project.

Example: ask DSH to diagnose a test failure without editing, run it in the repository, confirm exit zero and a clean diff, then summarize its final text.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…