Summary
Please consider adding an oo skills unpublish capability for published skills.
The current CLI supports removing locally installed managed skills through oo skills uninstall/remove, but there does not appear to be a way for a publisher to unpublish a skill that has already been published to the registry.
Why this matters
Previously published skills remain visible even when they are no longer useful, were published by mistake, or have become obsolete. This can leave a user's skill list cluttered with old experiments or unwanted published skills.
For example, after publishing several related skills during iteration, some of them may later become outdated or redundant. Because they cannot be unpublished, they continue to remain in the published/cloud skill list.
Expected behavior
Provide a publisher-facing way to unpublish a skill, for example:
oo skills unpublish <skill>
oo skills unpublish <skill>@<version>
I do not think this needs to be as strict as npm's package unpublish policy, since oo skills currently appear to be closer to user-owned workflow artifacts than foundational ecosystem packages. Still, it may be useful to keep some safeguards, such as:
- only the publisher/owner can unpublish
- optionally restrict unpublish to skills with no dependent references, or low/no installs
- keep an audit record internally
- prevent accidental removal with a confirmation prompt unless
--yes is passed
Summary
Please consider adding an
oo skills unpublishcapability for published skills.The current CLI supports removing locally installed managed skills through
oo skills uninstall/remove, but there does not appear to be a way for a publisher to unpublish a skill that has already been published to the registry.Why this matters
Previously published skills remain visible even when they are no longer useful, were published by mistake, or have become obsolete. This can leave a user's skill list cluttered with old experiments or unwanted published skills.
For example, after publishing several related skills during iteration, some of them may later become outdated or redundant. Because they cannot be unpublished, they continue to remain in the published/cloud skill list.
Expected behavior
Provide a publisher-facing way to unpublish a skill, for example:
I do not think this needs to be as strict as npm's package unpublish policy, since oo skills currently appear to be closer to user-owned workflow artifacts than foundational ecosystem packages. Still, it may be useful to keep some safeguards, such as:
--yesis passed