dsh-plugin-development

Coordinates planning, scaffolding, implementation, composition, testing, and release of standalone DSH Cordis plugins.

1|Updated Aug 13, 2026
One-click install
npx skills add https://github.com/a179-sanae/dsh-code-check --skill dsh-plugin-development-a179-sanae
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dsh-plugin-development
Source: https://github.com/a179-sanae/dsh-code-check/tree/main/.agents/skills/dsh-plugin-development
Command: npx skills add https://github.com/a179-sanae/dsh-code-check --skill dsh-plugin-development-a179-sanae

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Building a standalone DeepSeek Harness (DSH) Cordis plugin involves many error-prone stages—planning the plugin form, scaffolding the package, implementing behavior, composing profile bundles, testing, and preparing for release. This Skill orchestrates that entire workflow through staged sub-skills so nothing is skipped and every stage has explicit exit conditions. ## Core Features & Use Cases - Staged workflow orchestration: Sequences six stage skills (plan, scaffold, implement, compose, test, release) with defined entry and exit conditions for each. - Shared handoff contract: Maintains a structured handoff (objective, packageName, pluginId, pluginForm, config, invariant, testTiers, distribution) across stages so decisions are never lost. - Hard-stop guardrails: Enforces rules such as function plugins named-exporting name/inject/Config/apply, never mixing plugin forms, never committing credentials, and never claiming unrun checks passed. - Use Case: You want to create a new DSH plugin package from the template repository. Load this Skill, answer the required-input questions, and it walks you through planning, scaffolding, implementation, profile composition, testing, and release readiness with verifiable checks at each step. ## Quick Start Use the dsh-plugin-development skill to develop a new standalone DSH plugin from planning through verified release readiness.

Frequently Asked Questions about dsh-plugin-development

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a standalone DSH Cordis plugin?▼

Load the dsh-plugin-development skill, which sequences six stage skills: plan, scaffold, implement, compose, test, and release. Establish required inputs first—objective, package name, plugin id, target profile, and distribution channel—then follow each stage's exit conditions.

What is the difference between a function plugin and a service plugin in Cordis?▼

A function plugin named-exports name, inject, Config, and apply with no default export, while a service plugin default-exports its service class. The two forms must never be mixed in one plugin.

Can I skip the planning or composition stages when developing a DSH plugin?▼

Planning is never skipped. Composition may be omitted only for a package that deliberately declares no bundle and is tested through its actual consumer; all other stage exit conditions still apply even if stages run in one coding pass.

When should I not use the dsh-plugin-development skill?▼

Do not use it for SDK DSL-only projects or for changes to the DSH host source. It is scoped to standalone ESM Cordis plugin packages based on the template repository, including profile bundle patches.

Does the skill publish or push the plugin to Git or npm automatically?▼

No. Publishing, pushing, tagging, or configuring a remote requires an explicit user request. Release readiness checks—placeholders, exports, files list, build artifacts—never imply permission to publish.