What problem does it solve? Publishing a DSH plugin without verification risks broken installs, missing declaration files, leaked credentials, or template placeholders reaching consumers. This Skill provides a structured audit that proves a plugin artifact actually works through its intended distribution channel before any release happens. ## Core Features & Use Cases - Channel-specific validation: Verifies packed local tarballs, Git-source installs with prepare scripts, and npm/tarball packages 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. - Full verification pipeline: Runs lockfile install, typecheck, tests, prepare, build, public export imports, and pnpm pack dry-run inspection of the post-lifecycle file list. - Use Case: Before publishing a Cordis-based DSH plugin to GitHub, run this Skill to confirm the prepare script builds declarations on a clean clone, the tarball contains every exported runtime file, and README install instructions match reality. ## Quick Start Use the dsh-plugin-release skill to check whether this plugin is ready for Git distribution without publishing it.