What is the recommended way to share a plugin across an entire enterprise organization?	Through the organization's private marketplace.
Which plugin installation level is reserved for compliance or work that must run the same way?	Required.
If a plugin is set to "Available," where does it appear for users?	In the company Directory, where people can choose to install it.
If a plugin is set to "Installed by default," what can a teammate do with it?	They can use it, but they can also turn it off.
If you are the admin, where do you go to create or manage the private marketplace?	Organization settings → Plugins.
If the private marketplace already exists (Path A), what is the individual contributor's next step?	Hand the plugin off to the marketplace owner (e.g., team lead, enablement, or IT).
If the private marketplace is not set up (Path B), who should you ask to check its status?	IT, an enablement lead, or the owner of software tools.
What is the most critical habit for maintaining a shared plugin over time?	Having one designated owner who reviews changes and runs evals.
What must be done before every plugin publish to ensure quality?	Run evaluations (evals).
Why is it important to name skills and plugins specifically (e.g., "sales-customer-renewal-prep")?	To prevent naming collisions with other plugins in the directory.