Contributing
Contribute Browser Skills
Want to add a skill, fix a bug, or improve the docs? Here's how:
- Fork the repo — Clone browser-use/browser-skills and create a new branch.
- Add your skill — Create a folder in
skills/with aSKILL.mdfile. - Open a PR — Submit a pull request and a maintainer will review it.
How to Add a New Skill
Adding a new skill takes a few steps:
1. Fork the Repository
Start by forking the Browser Skills repository on GitHub to create your own working copy.
2. Create a Skill Directory
Under the skills/ directory, create a new folder for your skill. Use a descriptive, lowercase name with hyphens (e.g., my-awesome-skill):
skills/
├── browser-use/
├── playwright/
└── my-awesome-skill/
└── SKILL.md
3. Create SKILL.md
The SKILL.md file defines your skill. It uses YAML frontmatter for metadata, followed by Markdown documentation.
Required Frontmatter
Every SKILL.md must include:
---
name: my-awesome-skill
description: Brief description of what this skill does and when to use it
license: MIT
icon: https://example.com/icon.svg
---
Field Details:
- name: The skill identifier (lowercase, hyphenated)
- description: 1-2 sentence summary explaining the skill's purpose and use cases
- license: License type (e.g., MIT, Apache-2.0, ISC)
- icon: URL to an SVG icon representing the skill
Content Structure
After the frontmatter, structure your SKILL.md with clear sections:
# Skill Title
## Overview
Brief introduction to the skill.
## Installation
Instructions for installing or setting up the skill.
## Usage
Examples and patterns for using the skill.
## Triggers
List the phrases or conditions that activate this skill.
## Workflow
Step-by-step guide for the skill's workflow.
## Examples
Real-world examples demonstrating the skill in action.
Pull Request Process
Once your skill is ready, submit a pull request:
-
Commit Your Changes: Use clear, descriptive commit messages:
codegit commit -m "Add my-awesome-skill: description of the skill"
-
Push to GitHub: Push your branch to your forked repository:
codegit push origin feature/my-awesome-skill
-
Create a Pull Request: Open a PR against the main repository with:
- Title: Clear description of the skill (e.g., "Add browser-automation-xyz skill")
- Description:
- What the skill does
- Use cases and triggers
- Any special setup or requirements
- Links to related documentation or resources
-
Review Process: A maintainer will review your PR and may request changes.
-
Merge: Once approved, your skill will be merged and available in the marketplace.
Skill Quality Standards
All submissions should:
- Have a complete SKILL.md with proper YAML frontmatter
- Include a descriptive title and clear use-case explanation
- Follow consistent formatting and markdown style
- Include practical examples in the documentation
- Specify a valid license
- Provide an SVG icon URL
- Use clear, professional language