DeepSeek Harness Plugin

tt-a1i/archify#integrations/deepseek-harness

Stars ★ 13494 Category Skills Added 2026-08-17 npm @tt-a1i/archify-dsh

Generate validated, self-contained interactive architecture, workflow, sequence, data-flow, and lifecycle diagrams from repositories or system descriptions.

Install

# from npm (prebuilt)

dsh plugin --profile web add @tt-a1i/archify-dsh

# from GitHub (first run asks for allowBuilds approval — follow the hint, retry)

dsh plugin --profile web add github:tt-a1i/archify#path:/integrations/deepseek-harness

Any plugin you install runs third-party code with your own permissions — it can read your files, use your credentials, and reach the network, and tool approvals don’t sandbox it. GitHub-sourced plugins also run build scripts at install time. Only install sources you trust, and pin a commit (github:owner/repo#sha).

README

Community DeepSeek Harness integration for Archify. This is not an official DeepSeek product and does not imply DeepSeek endorsement.

v0.1.0 is experimental compatibility with developer-preview @deepseek-ai/dsh@0.1.0-rc.6 on Node.js ^22.19.0 || >=24.0.0. It is not a stable cross-version guarantee.

The package is a Skill-only bundle: it inserts one filesystem Skill provider named archify-plugin and exposes a clean copy of the existing Archify Skill. It does not register native render/validate/deliver tools, a custom Web client, Produced Files chips, telemetry, network access, credentials handling, background services, or prepare / install / postinstall hooks.

Install

Use the prebuilt npm package with an exact version. Do not install from Git source.

dsh plugin --profile web add @tt-a1i/archify-dsh@0.1.0

Invoke

Ask DSH to load Archify by name:

Use the archify skill to map this repository's runtime architecture.
Show 8–12 core components, one primary path, external dependencies, and trust boundaries.
Put supporting detail in cards instead of adding more edges.
After delivery, return the exact workspace paths of the specification JSON and the HTML artifact.

Archify then runs through DSH's ordinary Skill, shell, and filesystem paths. Generated JSON and HTML are normal workspace files.

Produced Files limitation

Files created by shell commands do not automatically appear in the Web Produced Files strip. Ask the agent to return the exact workspace paths of the specification JSON and the HTML artifact, then open those files from the workspace.

Uninstall

dsh plugin --profile web remove @tt-a1i/archify-dsh

The standard plugin command removes the adapter dependency and bundle layer. The base profile remains usable.

Security posture

  • No telemetry, network client, credentials handling, or background service
  • No prepare, install, or postinstall scripts
  • Host-loaded adapter code does not spawn processes or open a second permission path
  • Package resolution, provider load, and composition errors fail during normal DSH boot

Content from the project README on GitHub ↗

Links

More in this category

View the whole category →