For creators
Update a skill without surprising existing users
Prepare a candidate, keep the approved workflow live, and make releases easy to review.
Quick answer
Treat a skill update as a new candidate version. Submit it for scanning and human review while the approved version remains available. Once approved, a later load can receive the new release. A conversation that already received earlier instructions does not silently replace that text.
Separate the draft from the release
Use the creator editor to save unfinished work privately. A submission moves through scanning and review before it can become live. Do not change the description to promise a feature that exists only in a pending draft. Buyers should be able to understand the workflow they can actually load.
Give reviewers a meaningful change
A useful update changes a decision, supported input, output format, or dependency. Test that change with a representative example and a failure case. For example, adding a cancellation-policy check should improve the normal reply and also stop the workflow when the policy is missing.
Before submitting, compare the new instructions with the current approved version. Look especially for new destinations, credentials, permissions, or claims. A small text edit can create a large behavioral change if it alters an approval boundary.
Understand what “latest version” means
A new retrieval can select the current approved release. Existing conversation text remains part of that conversation. If you want to use a newer method for the same task, ask the AI to load it again and explain that the new workflow replaces the previous one.
| Situation | Expected behavior |
|---|---|
| Draft saved | No change to the current approved instructions |
| Update in review | Existing approved version remains available |
| Update approved | New loads can receive the approved release |
| Earlier instructions already in chat | Ask explicitly to load the updated workflow |
Rollback is a release action
Restore only a version that was previously approved and remains acceptable under current checks. Re-running the scan matters because an old release is not automatically safe forever. Keep the original review record and record the restoration separately so the history explains both decisions.
Common questions
Will a pending update interrupt buyers?
It should not replace the approved workflow. A separate safety or access restriction can still make a skill unavailable.
Can I restore a rejected draft?
It must be corrected and reviewed. Rollback is reserved for an eligible previously approved version, not an unreviewed alternative.
Should I tell users about material changes?
Yes. Explain changes to inputs, outputs, dependencies, and approval steps in the description or release communication. Do not present them as silent cosmetic edits.
Put a workflow to work.
Connect your library to your AI, or turn your method into a skill.