New:Socket for Asana Is Now Available.Learn more
Get Started

dsh-technical-writer

Package Overview
Dependencies
Maintainers
1
Versions
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

dsh-technical-writer

DSH bundle plugin for technical writing — guides, API docs, READMEs, tutorials, reference pages, and release notes.

latest
npmnpm
Version
0.1.0
Version published
Weekly downloads
54
-56.8%
Maintainers
1
Weekly downloads
 
Created
Source

dsh-technical-writer

A DeepSeek Harness bundle plugin that provides a technical writing skill for producing clear, well-structured documentation.

What It Does

This plugin injects the technical-writer skill into your DSH agent, enabling it to produce:

  • Guides and tutorials (learning-oriented)
  • API docs and reference pages (information-oriented)
  • How-to guides (task-oriented)
  • READMEs and release notes (all types)

The skill is based on the Diátaxis framework — a systematic approach to technical documentation that classifies content by reader need.

Installation

From Local Directory

dsh plugin --profile <your-profile> add ./dsh-technical-writer

From Git Repository

dsh plugin --profile <your-profile> add "github:<owner>/<repo>#main&path:/plugins/dsh-technical-writer"

Structure

dsh-technical-writer/
├── package.json              # dsh.bundle manifest
├── cordis.patch.yml          # Plugin registration
├── index.js                  # Plugin entry point
├── README.md                 # This file
└── skills/
    └── technical-writer/
        └── SKILL.md          # The technical writing skill

How It Works

  • The plugin declares itself as a dsh.bundle in package.json
  • cordis.patch.yml registers the plugin with the DSH container
  • index.js provides the plugin entry point
  • skills/technical-writer/SKILL.md contains the full skill documentation

Skill Usage

When installed, the agent can load the technical-writer skill on demand. The skill guides the agent through:

  • Identifying the reader — Who is this for? What do they need?
  • Choosing document type — Tutorial, how-to, reference, or explanation
  • Planning architecture — Information flow and structure
  • Writing drafts — Clear, concise, example-driven prose
  • Editing for clarity — Plain language, active voice, short sentences
  • Verifying quality — Readability, link checks, example testing

License

MIT

Keywords

dsh

FAQs

Package last updated on 24 Aug 2026

Related posts