What problem does it solve? Wiring a standalone DSH plugin into a profile involves fragile steps: declaring the bundle patch in package.json, writing correct cordis.patch.yml rows, installing through dsh plugin, and proving the plugin actually activated. This Skill guides that composition workflow so overrides are not silently skipped and activation is verified rather than assumed. ## Core Features & Use Cases - Bundle Declaration Verification: Checks that package.json declares dsh.bundle.patch and that cordis.patch.yml ships in the manifest files list. - Patch Semantics Review: Enforces rules for id-targeted config replacement, insert rows, empty patch handling, and credential hygiene before installation. - Isolated Profile Installation: Installs packed artifacts, registry versions, or approved Git specs into a dedicated DSH_HOME without touching live profiles. - Activation Proof: Uses config dumps and real runner boot to confirm the plugin reaches its entry path, not just package resolution. - Use Case: After packing a new DSH plugin with pnpm pack, use this Skill to install it into a temporary profile, dump the effective config, and confirm the plugin's rows and behavior appear before shipping. ## Quick Start Use the dsh-plugin-compose skill to install this plugin into an isolated DSH profile, inspect the effective configuration, and prove it activates.