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, insertions, and activation are verified instead of 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 replacement, insert rows, !!js usage, empty patches, and credential handling before installation. - Isolated profile installation: Uses a dedicated DSH_HOME, installs packed artifacts or approved Git specs via dsh plugin, and handles pnpm allowBuilds prompts correctly. - Activation proof: Dumps effective configuration, boots the real runner, and distinguishes bundle presence from actual plugin behavior. - Use Case: After building a DSH Web plugin, use this Skill to pack it, install it into a throwaway profile, inspect the effective config dump, and confirm the plugin mounts and disposes through its real entry path. ## Quick Start Use the dsh-plugin-compose skill to install this plugin into an isolated DSH profile, inspect the effective configuration, and prove activation.