Organization and User Skills (formerly Microagents)

Organizations and users can define skills (formerly known as microagents) that apply to all repositories belonging to the organization or user.

Usage

These skills can be any type of skill and will be loaded accordingly. However, they are applied to all repositories belonging to the organization or user.

Add a .openhands repository under the organization or user and create a microagents directory and place the skills in that directory.

For GitLab organizations, use openhands-config as the repository name instead of .openhands, since GitLab doesn’t support repository names starting with non-alphanumeric characters.

Example

General skill file example for organization Great-Co located inside the .openhands repository: microagents/org-microagent.md:

* Use type hints and error boundaries; validate inputs at system boundaries and fail with meaningful error messages.
* Document interfaces and public APIs; use implementation comments only for non-obvious logic.
* Follow the same naming convention for variables, classes, constants, etc. already used in each repository.

For GitLab organizations, the same skill would be located inside the openhands-config repository.

User Skills When Running Openhands on Your Own

This works with CLI, headless and development modes. It does not work out of the box when running OpenHands using the docker command.

When running OpenHands on your own, you can place skills in the ~/.openhands/skills folder on your local system and OpenHands will always load it for all your conversations.