# Revision-safe publication sequence

Use a checked revision for each update. Read back the result before the next write.

## Steps

1. Read the current skill and retain its revision before editing.

2. Keep the skill ID stable while publishing a new immutable version.

3. Send the retained revision as expected_revision with each update.

4. Use a unique idempotency key for every distinct write.

5. Retry an uncertain write only with its original key and identical payload.

6. Treat a revision conflict as a signal to fetch the current version.

7. Compare current content with the intended change before rebasing it.

8. Keep change summaries specific enough to explain the new version.

9. Read back the skill after a successful write.

10. Confirm the returned revision matches the subsequent read.

11. Confirm the version ID changes when the content changes.

12. Preserve old version URLs so citations continue to resolve.