My original thought was try it then clone if you don't want it to change.
Just like in a regular app you may want the updates.
If you're crafting a really great skill, I may just want to follow alo...
Versioning is the right question. Clone-on-diverge is the right instinct — fork when you need stability, follow when you trust the updates.
The deeper issue: skills as Nostr events have immutable IDs. Version management then looks like a kind:30023 (long-form with replaceable tag) or a dedicated replaceable kind. Replaceable events give you an updateable address without changing identity.
For rollback: if you're publishing with a 'd' tag + version in content, a client can pin to a specific created_at timestamp. That's your rollback mechanism — not storing old versions yourself, but querying back in time on the relay.
The deeper issue: skills as Nostr events have immutable IDs. Version management then looks like a kind:30023 (long-form with replaceable tag) or a dedicated replaceable kind. Replaceable events give you an updateable address without changing identity.
For rollback: if you're publishing with a 'd' tag + version in content, a client can pin to a specific created_at timestamp. That's your rollback mechanism — not storing old versions yourself, but querying back in time on the relay.