Using the Add-Skill Action
The quickest way to add a skill is using the/add-skill command in your conversation with OpenHands. This command fetches skills from GitHub repositories and installs them in your workspace.
Basic Usage
Simply provide a GitHub URL pointing to a skill:- Parse the URL to identify the repository and skill path
- Fetch the skill files from GitHub
- Install the skill in
.agents/skills/directory - Verify the installation
- Make the skill immediately available
Supported URL Formats
The/add-skill command accepts various GitHub URL formats:
- Full GitHub tree URL:
https://github.com/OpenHands/extensions/tree/main/skills/codereview - Repository path:
https://github.com/OpenHands/extensions/skills/codereview - Short form:
github.com/OpenHands/extensions/skills/codereview - Shorthand:
OpenHands/extensions/skills/codereview
Examples
Add the code review skill:Skill Storage Locations
Skills are stored in different locations depending on the platform and scope:- CLI
- SDK
- Local GUI
- OpenHands Cloud
The CLI supports two skill locations:User-level skills (global, available in all conversations):Project-level skills (specific to current directory):Skills added via
/add-skill are installed in .agents/skills/ of your current workspace, making them available for that project.To add skills globally, manually place skill directories in ~/.openhands/skills/.Manual Installation
You can also manually install skills by copying skill directories into the appropriate location.For Project-Level Skills
-
Create the skills directory if it doesn’t exist:
-
Copy or clone the skill directory:
-
Verify the skill structure:
For User-Level Skills (CLI Only)
-
Create the global skills directory:
-
Add skills to this directory:
~/.openhands/skills/ are available in all your conversations when using the CLI.
Verifying Installation
After adding a skill, verify it’s available:-
Check the file exists: The skill directory should contain at least a
SKILL.mdfile -
Test the trigger: For keyword-triggered skills, use one of the trigger words in your prompt:
- Check skill loading: OpenHands will indicate when a skill is loaded in response to your prompt
Skill Updates
To update a skill to the latest version:-
Remove the old version:
-
Add the updated version:
Authentication for Private Skills
If you need to add skills from private repositories:-
Set GITHUB_TOKEN: Ensure the
GITHUB_TOKENenvironment variable is set with a token that has access to the private repository -
Use the same
/add-skillcommand: The command will automatically use the token for authentication
/add-skill as normal with private repository URLs.
Skill Conflicts
If a skill with the same name already exists, OpenHands will warn you before overwriting. To resolve conflicts:- Rename the existing skill: Move or rename the existing skill directory
- Choose a different installation location: Install at user-level vs project-level
- Overwrite: Confirm the overwrite when prompted
Next Steps
- Browse available skills in the official registry
- Create your own skills for custom workflows
- Learn about keyword triggers to make skills activate automatically
- Understand skill structure for the AgentSkills format

