Introduction

After an agent completes a task, it often outputs a technical text containing file names, code, paths, and terminology. If you do not read code, it is hard to quickly determine whether the task succeeded or which step to follow up on. dsh-plugin-brief converts each agent response into briefing slides: conclusion first, followed by steps, and ending with questions that require your attention. The original text is always retained on the side for reference when needed.

Plugin Overview

This is a DeepSeek Harness plugin designed to provide a more readable response view for Harness users who do not read code. It reformats the original technical text into a slide format and provides a “plain language” rewriting feature.

  • Maintainer: dangxinxing090-svg
  • License: MIT
  • Catalog page: https://www.skillhub.cn/plugins/dangxinxing090-svg/dsh-plugin-plain-slides
  • Source: https://github.com/dangxinxing090-svg/dsh-plugin-brief

Core Features

  1. Slide-based display: The response content is split into several slides. The first slide is the conclusion, the middle slides are execution steps, and the final slide contains outstanding questions or requests.
  2. Plain language rewriting: Provides a “plain language” button to translate the conclusion and steps into plain language. Rewriting applies only to the report content and does not include the work process.
  3. Local layout, zero cost: By default, slides are automatically formatted locally from the original text, without consuming model calls.
  4. On-demand rewriting: A model call is made only when you click the “plain language” button. After a successful rewrite, the result is retained, so additional viewings require no extra cost.
  5. Dual-version retention: The card retains both the original version and the plain-language version, and you can switch between them with the button. The original version is always available by clicking to view.

Installation and Enabling

Before installing, make sure DeepSeek Harness (dsh) is installed on your machine.

  1. Run the following command to install the plugin:
dsh plugin --profile web add github:dangxinxing090-svg/dsh-plugin-brief

After installation, the plugin is mounted automatically; no configuration file is required.

  1. If you want to specify a version, append a tag:
dsh plugin --profile web add github:dangxinxing090-svg/dsh-plugin-brief#v0.1.0
  1. Restart the dsh process to activate the plugin.

In --profile web, the web part can be replaced with another configuration profile name you use (such as tui).

Typical Usage

After installation, every agent response is displayed as slides on the response card.

  1. View the default layout: The card is shown by default in the “original” slide layout.
  2. Request a rewrite: Click the “plain language” button on the card. The card title displays “Plain language…”.
  3. View the result:
    • If the rewrite succeeds, the button becomes “Original”, indicating that the current view is the plain-language version. Click it to switch back to the original version.
    • If the rewrite fails, the button returns to “plain language”, but the layout remains (without simplification).
  4. View the full original text: Click the “Full original text” button at the top of the card to view the complete Markdown original, including the technical summary (elapsed time, operation count, Token usage).

How It Works and Costs

  1. Rendering takeover: The plugin takes over the response renderer, changing the original direct Markdown rendering into slide cards.
  2. Collapsing work process: The plugin hides noisy information such as tool lines, reasoning collapses, and injected context, retaining only necessary interaction details (such as failure information and approval requests). This information is retained in the Trajectory view.
  3. Cost control:
    • Viewing slides by default incurs no cost.
    • A model call is made only when you click “plain language” to translate the report content.
    • After a successful rewrite, the result is cached, so no additional model call is required when viewing it again or after restarting DSH.

Notes

  1. Config file editing: Do not manually edit cordis.yml (this file is system-generated). Edit cordis.patch.yml instead.
  2. Release consistency: If you fork the plugin and publish your own version, the name in package.json must match the name in cordis.patch.yml; otherwise the loader cannot resolve the module.
  3. Security check: The plugin runs with the permissions of the current DSH process. Before installation, review the source code and license.