> ## Documentation Index
> Fetch the complete documentation index at: https://explore.airia.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Skills Repositories

> Create and manage collections of code and data files that are available to Airia Agent during sandboxed execution.

A Skills Repository is a named, project-scoped archive of files — scripts, configuration files, lookup tables, prompt templates — that are mounted into the [Compute Sandbox](/admin-hub/airia-agent/compute-sandbox) when Airia Agent executes tool calls. This gives Airia Agent access to custom logic and data without requiring you to publish that logic as a formal tool.

## Prerequisites

* **Role**: Admin, Platform Admin, or Project Admin
* **Permission**: Studio > Skills > Manage
* **Compute Sandbox** must be enabled for your tenant (see [Compute Sandbox](/admin-hub/airia-agent/compute-sandbox))
* Tools that require external authentication need credentials configured in [Credential Management](/admin-hub/account_settings/credential-management)

## Create a repository

<Steps>
  <Step title="Open the Skills page">
    Navigate to your project, then select **Skills** from the left navigation.
  </Step>

  <Step title="Create a new repository">
    Click **New Repository**. Provide:

    * **Name**: A short, descriptive identifier (e.g., `data-utilities`, `finance-scripts`)
    * **Description**: What the repository contains and what it is used for
  </Step>

  <Step title="Save">
    Click **Create**. The repository is created and you are taken to its detail view.
  </Step>
</Steps>

## Manage files

Once a repository exists, you can add and edit files through the browser UI or by uploading a zip archive.

### Add or edit individual files

1. Open the repository's detail view
2. Navigate the directory tree to the location where you want to add or edit a file
3. Click **New File** or select an existing file to open the editor
4. Write or paste file content directly in the browser
5. Click **Save**

### Upload a zip archive

If you have existing code you want to bulk-load:

1. Open the repository's detail view
2. Click **Upload**
3. Select a `.zip` file from your machine
4. The contents are extracted and added to the repository, preserving the archive's directory structure

### Export files

To back up a repository or migrate it to another project:

1. Open the repository's detail view
2. Select the folders or files you want to export
3. Click **Export** — the selection is downloaded as a `.zip` archive

## Control access to a repository

By default, all project members can access a repository. You can restrict it to specific users or groups:

1. Open the repository's detail view
2. Navigate to **Access**
3. Add specific users or groups — only they will have access to this repository
4. Click **Save**

### What access means

Access controls who can **browse and edit** the repository's file contents through the UI or API. They do not block sandbox execution: when the sandbox mounts a repository during a tool call, it does so at the platform level regardless of individual user access settings. A user without repository edit access can still benefit from skills mounted in the sandbox during their conversation.

If a project has no repositories configured, the sandbox proceeds without any skills mounted — tool calls still execute in the isolated container, but no custom files are available.

<Note>
  Repositories are project-scoped. If you need the same skills available in multiple projects, export the repository as a zip and import it into each project separately.
</Note>

## How repositories connect to the sandbox

When Airia Agent executes a tool call in the sandbox:

1. The platform resolves which Skills Repository is associated with the active project
2. The repository files are mounted into the sandbox container's file system
3. Any scripts or data files in the repository are accessible to the executing tool

The first available repository for the project is used automatically. If you have multiple repositories in a project, the platform selects one consistently — to use a specific repository, ensure it is the only one configured for that project.

## Use cases

| Use case                  | What to put in the repository                                              |
| ------------------------- | -------------------------------------------------------------------------- |
| Custom data processing    | Python or JavaScript utility scripts                                       |
| Domain-specific lookups   | CSV or JSON reference files (product catalogs, org charts, pricing tables) |
| Reusable prompt templates | Markdown or text files with structured prompts                             |
| Configuration             | YAML or TOML files that tools read at execution time                       |
| Proprietary algorithms    | Source files for logic you do not want to expose as a public tool          |