Repositories

​

Overview

Use repositories to give agents access to shared files from source code repositories, S3 buckets, or uploaded archives. A repository can serve two independent purposes: hosting remote skills for your agents, or providing searchable reference content that agents can query during a session. You can enable either or both. You create and manage repositories from Tools > Repositories in the Poolside Console. After you create a repository, enable its skills and indexed content separately when you configure a managed agent.

​

When to use a repository

Use a repository when you want agents to:

• Use skills stored in a shared repository
• Search source code, documentation, configuration, or other text-based reference files
• Reference shared team or organization content outside the local workspace
• Keep reusable skills and reference content in a managed shared resource

Do not use a repository for:

• Frequently changing or transactional data
• Binary assets like images, videos, or executables
• Data that requires write access
• Actions, tool invocation, or API calls (use an MCP server instead)

​

Source types

Each repository connects to one source type: After you create a Git or S3 repository, you can sync it from its source. To update a manually uploaded repository, upload a new archive version.

​

What agents can use

These two capabilities are independent. You can use a repository for skills, indexed content, or both. Repositories can support two related workflows:

• Skills: Poolside automatically discovers skills in the repository that follow the Agent Skills format. Each skill is a directory with a SKILL.md file and can include supporting files such as scripts/, references/, and assets/. For Poolside-specific guidance, see Skills. For the full format, see the Agent Skills specification. To make discovered skills available to an agent, create or edit a managed agent and enable the skills in the agent’s Skills section.
• Searchable reference content: When you select Index repository for knowledge extraction, Poolside indexes text files so agents can search and read relevant content. To make indexed content available to an agent, create or edit a managed agent and enable the repository in the agent’s Knowledge Sources section.

After you add a repository, open it to review its status and discovered skills. If you enabled indexing, use the Knowledge Base tab to review Index Statistics, including files seen, files indexed, files ignored, indexed extensions, and ignored extensions. The repository details page uses Knowledge Base for index statistics. Managed agent configuration uses Knowledge Sources for enabling indexed repositories.

​

Limits

• Manual upload files must use .tar.gz or .zip and be 512 MB or smaller.
• Files in Git repositories larger than 2 MB are not included.
• Files in S3 larger than 2 MB are not included.
• Git repository submodules and symbolic links are not included.

​

Access and security

Role-based permissions and agent configuration determine who can access a repository and how agents can use it.

​

Role-based permissions

Role permissions determine whether you can create, use, or manage repositories. You must have the Use Repositories permission to allow an agent to search and retrieve content from a repository. For a complete list of permissions, see Permissions reference.

​

Agent access

Agents require explicit access to each repository.

• For remote skills, enable one or more skills from the repository in the agent’s Skills section.
• For searchable reference content, enable the indexed repository in the agent’s Knowledge Sources section.
• Agents get read-only access.

An agent can use a repository only if:

• For skills: at least one skill from the repository is enabled in the agent’s Skills section
• For indexed content: the repository is enabled in the agent’s Knowledge Sources section
• The user running the agent has permission to use the repository

Enabling a repository for an agent does not grant you permission to use it.

​

Create a repository

Prerequisites

• You have the Create Repositories permission.
• For a private Git repository, create a Username / Password credential before you add the repository.
• For Manual Upload, prepare a .tar.gz or .zip archive that is 512 MB or smaller.
• For S3 Repository, have the S3 URI for the bucket or path you want to add.

Steps

1. In the Poolside Console, navigate to Tools > Repositories.
2. Click New Repository.
3. Select the repository type:
   • Manual Upload: Upload a tar or zip file that contains your repository files.
   • Git Repository: Connect a Git repository from an HTTP or HTTPS remote URL.
   • S3 Repository: Connect files from an S3 bucket or path.
4. Complete the fields for the repository type you selected.
   • Manual Upload
   • Git Repository
   • S3 Repository

   • Name: Enter a name for the repository.
   • Description (optional): Enter a description.
   • File: Choose a .tar.gz or .zip archive.

   • Name: Enter a name for the repository.
   • Description (optional): Enter a description.
   • Remote URL: Enter the Git remote URL. The URL must use http:// or https://.
   • Branch: Enter the branch to use. The default branch value is main.
   • Credential: For a private repository, select a Username / Password credential. Public Git repositories can use None (public repository).

   • Name: Enter a name for the repository.
   • Description (optional): Enter a description.
   • S3 URI: Enter the S3 URI. The URI must start with s3://.
   • S3 Prefixes (optional): Enter a comma-separated list of prefixes.
5. Optional: Select the Index repository for knowledge extraction checkbox if you want agents to search and read repository content as reference material. Leave the checkbox clear if the repository only provides skills.
6. Click Create Repository.

Next steps

1. Open the repository and review its status and discovered skills.
2. If you enabled indexing, use the Knowledge tab to review the number of files seen, indexed, and ignored, and the indexed and ignored extensions.
3. To use discovered skills, create or edit a managed agent. In the agent’s Skills section, find the repository, then click Enable all or click Show skills to enable individual skills.
4. To use indexed content, create or edit a managed agent and enable the repository in the agent’s Knowledge Sources section.
5. Test the repository by running an agent that has access to it.

​

Edit a repository

Prerequisites

• You have the Manage Repositories permission.

Steps

1. In the Poolside Console, navigate to Tools > Repositories.
2. Select the repository.
3. Update the fields you want to change.
4. Click Save Changes.
5. For Git or S3 repositories, click Sync to update the repository from its source.

​

Delete a repository

Deleting a repository removes it from all agents that reference it. Agents configured to use the deleted repository can no longer use its skills or searchable reference content until you update the agent configuration. Prerequisites

• You have the Manage Repositories permission.

Steps

1. In the Poolside Console, navigate to Tools > Repositories.
2. Select the repository.
3. Click Delete.