> 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-mcp/tool-reference/skills-and-versions/skills-rollback.md).

# skills\_rollback

Restore a historical version by publishing its content as a NEW latest version.

**Effect:** This call saves data or changes configuration. Review the behavior below before using it.

## Inputs

| Name       | Type    | Requirement | Description                                                   |
| ---------- | ------- | ----------- | ------------------------------------------------------------- |
| `skill_id` | string  | Required    | Skill ID returned by `skills_list`.                           |
| `version`  | integer | Required    | Positive, 1-based version number from `skills_versions_list`. |

## Example

These are MCP tool arguments, not an HTTP request body. Replace bracketed IDs with values returned from your account.

```json
{
  "skill_id": "<skill-id>",
  "version": 1
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "skill_id": "<skill-id>",
  "version": 3,
  "source_version": 1
}
```

## Behavior

Existing history remains intact.

This can also restore the old name and changes what agents resolve immediately.

Inspect the target version first.

The current latest version cannot be a rollback target; repeated successful restores append versions.

## Troubleshooting

Select a historical version from `skills_versions_list`; the current latest version cannot be the target. Restoring creates a new version and changes live behavior immediately.

## Related resources

[Skills and versions](https://docs.stackai.com/stackai-mcp/tool-reference/skills-and-versions.md)

[Connection, permissions, pagination, and recovery](https://docs.stackai.com/stackai-mcp/best-practices-and-troubleshooting.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-mcp/tool-reference/skills-and-versions/skills-rollback.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.
