Introduction¶

When automating with DSH, a common problem is not “whether there are tools,” but “whether this capability is actually usable right now.” For the same task, an official DSH tool may already exist at the underlying level, but it may not be mounted in the current profile, may not be visible to the Agent, or may not meet provider conditions.

cyanseek/dsh-native-playbook is a community plugin for DeepSeek Harness. It provides a native_capability tool that routes tasks to official DSH tools, checks whether the full capability is operational, and safely activates reviewed native paths when possible.

It is suitable for checking whether DSH already has a usable native path before installing another plugin.

What This Is¶

dsh-native-playbook is a task-aware native capability manager. It performs capability checks, activation planning, and verification around the DSH profile.

The maintainer is cyanseek, and the license is MIT. The project requires Node.js 22 or 24, as well as DeepSeek Harness. It is explicitly marked as a community extension and is not affiliated with or endorsed by DeepSeek.

The currently supported DSH installation path is via GitHub commands; the npm package name is reserved for a future release.

Core Features¶

Routes Tasks to Official DSH Tools¶

The plugin provides the native_capability tool. Its focus is to first determine whether a task should use DSH’s built-in capabilities, rather than directly adding a new set of external tools.

Checks Whether the Capability Is Operational¶

It checks whether the full capability is operational and reports the following lifecycle facts:

• shipped
• mounted
• visible
• providerReady
• operational

These facts are used to distinguish between “present in the registry,” “mounted in the profile,” “currently visible to the Agent,” “provider conditions met,” and “currently usable.”

Covers Common Task Paths¶

It supports the following common task paths:

• Background commands
• Symbol navigation
• Previous session search
• Delegated investigation
• Fixed multi-step work

Safely Activates Reviewed Native Paths¶

When possible, it safely activates reviewed native paths. The activation surface is narrow:

• Limited to reviewed recipes in this repository only
• Requires an explicit DSH version compatibility gate
• Currently verified activation target is DSH 0.1.0-rc.6
• Changes pass through DSH checks and are reversible
• Verification failure preserves the original profile
• Deactivation restores saved content and refuses to overwrite subsequent user edits

Provides CLI and Node API¶

It provides the dsh-native CLI command, including:

lookup
status
list
explain
doctor
install
plan
activate
deactivate
verify

It also provides a Node API, such as:

• inspectDshProfile
• lookupNativeCapability
• planNativeActivation

Provides Agent Skill Installation¶

In addition to DSH plugin installation, it also provides an Agent Skill installation method for integrating the same native-first guidance into agent workflows.

Installation and Enabling¶

Install the plugin into the DSH profile:

dsh plugin --profile web add github:cyanseek/dsh-native-playbook

If you need to install it as an Agent Skill:

npx skills@latest add cyanseek/dsh-native-playbook --skill dsh-native-playbook --agent codex --yes

To remove the plugin:

dsh plugin --profile web remove dsh-native-playbook

Typical Usage¶

The following uses the web profile as an example.

Query which native path a task should use:

dsh-native lookup "<task>" [--profile <name>] [--json]

View the status of a profile:

dsh-native status --profile web --json

Generate an activation plan for session_search:

dsh-native plan session_search --profile web --json

In Node.js code, you can also first inspect the profile, then query the capability and generate a plan:

import {
  inspectDshProfile,
  lookupNativeCapability,
  planNativeActivation,
} from 'dsh-native-playbook'

const profile = await inspectDshProfile({ profile: 'web' })
const result = await lookupNativeCapability('run a long test in background', { profile })
const plan = await planNativeActivation('session_search', { profile: 'web' })

Through the steps above, you can first obtain the facts of “whether it is currently available” and “what is prepared for activation,” then decide whether to execute activate or verify.

Suitable Scenarios and Notes¶

Suitable for:

• Confirming whether DSH already has usable capabilities before adding another plugin
• Needing to check shipped, mounted, visible, providerReady, and operational separately
• Needing to perform plan, activate, deactivate, and verify on reviewed paths such as session_search
• Wanting to use JSON output for automated checks

Notes:

• It requires Node.js 22 or 24, as well as DeepSeek Harness
• Static lookup does not require DSH; real-time readiness checks require an existing DSH profile
• It does not collect telemetry; the API does not access credential storage or private session content
• Activation is limited to reviewed recipes and is constrained by an explicit DSH version compatibility gate
• The plugin runs with the current DSH process permissions; you should inspect the source code, license, and reviewed recipes before installation
• It is a community extension and is not affiliated with or endorsed by DeepSeek

Conclusion¶

The value of dsh-native-playbook is breaking down “whether it can be used, whether it should be enabled, and how to roll back” into checkable steps: first lookup, then status, then plan, and then activate under the premise of version compatibility, verifiability, and reversibility.

Project GitHub: https://github.com/cyanseek/dsh-native-playbook
Directory page reference: https://www.skillhub.cn/plugins/cyanseek/dsh-native-playbook