> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/stackai-tools/skill-management/roll-back-skill.md).

# Roll Back Skill

Restore the content of an earlier skill version when a newer version does not meet your needs. Rollback publishes the restored content as a new latest version.

## Before you start

You need permission to update the selected skill.

## Restore an earlier version

1. Use [List Skill Versions](https://docs.stackai.com/stackai-tools/skill-management/list-skill-versions.md) to find the earlier version, then inspect its content with [Get Skill](https://docs.stackai.com/stackai-tools/skill-management/get-skill.md).
2. Provide **Skill ID** and the historical **Version** to restore.
3. Run **Roll Back Skill** and check **Source Version** and the new **Version**.
4. Review the restored instructions, actions, and files before relying on them in an agent.

**Result:** A new latest version contains the selected historical version’s content.

## Behavior and troubleshooting

Rollback does not erase history or reuse the old version number. Built-in skills are read-only. Check that the restored skill still has the connections and actions required by your current workflow.

## Inputs

| Field               | Parameter  | Description                                                |
| ------------------- | ---------- | ---------------------------------------------------------- |
| Skill ID (required) | `skill_id` | The ID of the skill to roll back.                          |
| Version (required)  | `version`  | The prior version number whose content should be restored. |

## Outputs

| Field          | Parameter        | Description                                        |
| -------------- | ---------------- | -------------------------------------------------- |
| Summary        | `summary`        | One-line summary of the rollback.                  |
| Skill ID       | `skill_id`       | The skill that was rolled back.                    |
| Name           | `name`           | The published skill name.                          |
| Version        | `version`        | The NEW latest version number.                     |
| Source Version | `source_version` | The historical version whose content was restored. |
| Description    | `description`    | The restored description.                          |
| Actions        | `actions`        | Action refs stored with the restored version.      |
| Instructions   | `instructions`   | The restored SKILL.md body.                        |
| Frontmatter    | `frontmatter`    | The restored SKILL.md frontmatter.                 |
| Files          | `files`          | The restored file manifest (metadata only).        |

## Related guidance

[Skill Instructions, Files, and Action References](https://docs.stackai.com/technical-reference/models-agents-and-skills/skill-instructions-files-and-action-references.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.stackai.com/stackai-tools/skill-management/roll-back-skill.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
