Turn a default-on catalog skill off for this workspace, or back on

A trusted, listed, portable catalog skill runs for every workspace with NO install row at all. This is how a workspace stops one, and how it gives it back.

enabled: false writes the suppressing row (creating the install if there is none) and stamps the pause in ONE transaction. That is why this is a route rather than two client calls: an install row alone does not suppress anything (a never-activated row reads as an unfinished install, deliberately), so a client that installed and then failed the second call would leave the skill running behind a switch drawn as off. The activation route cannot do the second half anyway — a portable skill compiles no activate action.

enabled: true DELETES the suppressing row, returning the skill to the exact state a workspace that never touched it is in: running on the catalog's active version. It refuses (409 SKILL_IS_KILLED) when a KILLED team row holds the slot: the emergency stop on the skill's own page is what clears that, not this switch. A personal or staff copy answers changed: false whatever its state.

Both directions are idempotent apart from that refusal. Both require skills:install, because this changes what the whole team runs.