> 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-create.md).

# skills\_create

Create version 1 of an organization-scoped skill.

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

## Inputs

Choose one input mode. **Text mode** requires `name`, `description`, and `instructions`. **File mode** requires `files`. Do not combine the modes.

| Name           | Type                  | Requirement           | Description                                                                                                                                            |
| -------------- | --------------------- | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `name`         | string                | Required in text mode | Resource name.                                                                                                                                         |
| `description`  | string                | Required in text mode | Description of the resource or requested change.                                                                                                       |
| `instructions` | string                | Required in text mode | Full Markdown body of the skill instructions, required in text mode.                                                                                   |
| `actions`      | array of strings      | Optional              | Complete array of `provider_id.action_id` references. On skill update, omission or null clears the existing references.                                |
| `files`        | array of file objects | Required in file mode | Array of `{path, content_base64}`. Include a root `SKILL.md` with `name` and `description` frontmatter. Paths must be relative, with no `..` segments. |

Each file contains `path` (relative path) and `content_base64` (standard base64). File mode requires `SKILL.md` at the root. Its YAML frontmatter must include `name` and `description`.

## Example

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

```json
{
  "name": "Evidence-based answers",
  "description": "Answer questions using supplied evidence.",
  "instructions": "Use the supplied sources. Cite the relevant source for each material claim. State when the evidence is insufficient.",
  "actions": []
}
```

## Result

Abbreviated result example; unshown fields are omitted for clarity.

```json
{
  "skill_id": "<skill-id>",
  "name": "Evidence-based answers",
  "version": 1,
  "actions": [],
  "normalization": null
}
```

## Behavior

Use text mode (name, description, instructions) OR file mode (files with a root SKILL.md), never both.

Names must be unique within the organization. actions are catalog-validated provider\_id.action\_id references.

File mode reports frontmatter/tool normalization; inspect the normalization result.

## Troubleshooting

Choose text mode or file mode, not both. Use a name unique within the organization. Correct bundle findings before creating the skill.

## 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-create.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.
