> For the complete documentation index, see [llms.txt](https://alludium.gitbook.io/alludium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://alludium.gitbook.io/alludium-docs/administration/10.-skills/10.3-importing-skills.md).

# Importing Skills from GitHub

Skills follow the open SKILL.md standard adopted by 26+ AI platforms, which means thousands of skills already exist in public GitHub repositories. You can import any public SKILL.md-based skill directly into your Alludium workspace.

***

#### Opening the Import Dialog

1. Navigate to **Skills** in the main navigation.
2. Click **Import** in the top right corner.

***

#### Import Fields

| Field              | Required | Description                                                                                                                                |
| ------------------ | -------- | ------------------------------------------------------------------------------------------------------------------------------------------ |
| **Skill name**     | Yes      | A name for the skill in your workspace library                                                                                             |
| **Description**    | No       | An optional summary of the imported skill                                                                                                  |
| **Repository URL** | Yes      | The root URL of the GitHub repository (e.g., `https://github.com/acme/skills`). Use the repository root, not a blob or tree URL.           |
| **Git ref**        | Yes      | The branch, tag, or commit SHA for the snapshot you want to import (e.g., `main`)                                                          |
| **Path**           | Yes      | The path to the skill folder or the exact `SKILL.md` entry file, relative to the repository root (e.g., `SKILL.md` or `research/SKILL.md`) |

***

#### What Gets Imported

The import flow accepts either a folder containing a `SKILL.md` file plus supporting files, or a direct path to a single `SKILL.md` file. The imported content is validated to ensure it is well-formed before saving.

**Important:** The import creates a **local snapshot** of the GitHub content. Alludium stores the imported skill locally — later edits happen in Alludium, not back on GitHub. The original GitHub provenance metadata is preserved for reference.

***

#### Re-importing and Updating

If you want to pull in a newer version of the skill from GitHub:

* Re-import is **explicit and overwrite-based**. Navigate to the skill and start a re-import to replace the local snapshot with the latest content from GitHub.
* Re-import does not happen automatically. You control when to update.

***

#### Current Limitations

* **Public repositories only** — Private or authenticated GitHub imports are not supported in this beta.
* **Import only** — There is no export or publish-back-to-GitHub flow.
* **Manual re-sync** — Automatic sync with upstream repositories is not available.
* **GitHub only** — GitLab and Bitbucket are not supported.

***

**Next Steps**

Continue to **Assigning Skills to Agents** to learn how to attach imported skills to your agents.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://alludium.gitbook.io/alludium-docs/administration/10.-skills/10.3-importing-skills.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.