What problem does it solve? Developing Cordis plugins requires knowing the exact runtime interfaces—Services, Events, Slots, theme tokens, and Tools—before writing any code, and guessing APIs leads to runtime failures. This Skill provides a disciplined inspect-then-define workflow for building dynamic plugins and durable distributable dsh bundles without inferring APIs from names or examples. ## Core Features & Use Cases - Inspect-driven development: Query live Providers with cordis_inspect_list and cordis_inspect_query before writing plain-JavaScript Host or Client plugin code. - Full plugin lifecycle: Define, run, approve, update, roll back, stop, and undefine plugins using cordis_define, cordis_run, and cordis_inspect_self with correct version semantics. - Distributable bundles: Ship persistent capabilities as packages with a dsh.bundle.patch self-patch, choosing a resolvable package scope for official dsh or ellamaka deployments. - Use Case: You want to add a custom settings panel to the dsh Client. Query Slots.listSubTree to find the right settings Slot, write a React.createElement-based Client plugin, define and run it, then package it as a distributable bundle for other sessions. ## Quick Start Ask the agent to create a Cordis plugin that registers a small UI panel, and it will inspect the available Slots and Services before defining and running the plugin.