What problem does it solve? Releasing a DSH plugin through a packed tarball, Git source, or npm registry involves many failure points: leftover template placeholders, broken prepare scripts, missing declaration files, and incomplete packed archives. This Skill provides a structured audit that proves a plugin artifact can actually be consumed through the chosen channel before any release happens. ## Core Features & Use Cases - Channel-specific validation: Checks packed local artifacts, Git-source installs with prepare scripts, and npm/tarball distributions against their distinct requirements. - Identity and portability audit: Greps for template markers, stale package names, absolute paths, credentials, and forbidden link:/file: dependencies across manifests and source. - Archive and consumer verification: Runs typecheck, tests, prepare, build, and pnpm pack dry-runs, then validates public exports by installing the tarball into a clean consumer. - Use Case: Before publishing a Cordis plugin, run this Skill to confirm the packed tarball contains every runtime and declaration file promised by package.json exports, and that a fresh Git clone installs and activates correctly in an isolated DSH profile. ## Quick Start Use the dsh-plugin-release skill to check whether this plugin is ready for Git and npm distribution without publishing it.