Prerequisites
- Role: Admin, Platform Admin, or Project Admin
- Permission: Studio > Skills > Manage
- Compute Sandbox must be enabled for your tenant (see Compute Sandbox)
- Tools that require external authentication need credentials configured in Credential Management
Create a repository
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
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
- Open the repository’s detail view
- Navigate the directory tree to the location where you want to add or edit a file
- Click New File or select an existing file to open the editor
- Write or paste file content directly in the browser
- Click Save
Upload a zip archive
If you have existing code you want to bulk-load:- Open the repository’s detail view
- Click Upload
- Select a
.zipfile from your machine - 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:- Open the repository’s detail view
- Select the folders or files you want to export
- Click Export — the selection is downloaded as a
.ziparchive
Control access to a repository
By default, all project members can access a repository. You can restrict it to specific users or groups:- Open the repository’s detail view
- Navigate to Access
- Add specific users or groups — only they will have access to this repository
- 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.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.
How repositories connect to the sandbox
When Airia Agent executes a tool call in the sandbox:- The platform resolves which Skills Repository is associated with the active project
- The repository files are mounted into the sandbox container’s file system
- Any scripts or data files in the repository are accessible to the executing tool
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 |
