open-source
Skill1 starsChanged 6 months agoNo licenceView on GitHub
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browser_use, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle hooks, MCP server setup, or monitoring/observability with Laminar or OpenLIT. Also trigger for questions about browser-use installation, prompting strategies, or sensitive data handling. Do NOT use this for Cloud API/SDK usage or pricing — use the cloud skill instead. Do NOT use this for directly automating a browser via CLI commands — use the browser-use skill instead.
- Reads credentials
- Installs packages
4 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TangleML/tangle-uitheir own version, first seen Oct 8, 2026
- igarbayo/open-sourcetheir own version, first seen Aug 19, 2026
- browser-use/browser-useedited, first seen May 22, 2026
- hunkdl/yeti-agentword for word, first seen Mar 22, 2026
Other versions4 projects use a version of this.
Word for word · 1
- hunkdl/yeti-agent★ 1100% same
Edited · 1
- browser-use/browser-use★ 120k97% same
Wrote their own version · 2
- TangleML/tangle-ui★ 104same name
- igarbayo/open-source★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository19 other files it gives its agents.
- brainstormingSkill
- copywritingSkill
- docxSkill
- find-skillsSkill
- frontend-designSkill
- humanizer-zhSkill
- karpathy-guidelinesSkill
- lark-baseSkill
- lark-docSkill
- lark-driveSkill
- lark-openapi-explorerSkill
- lark-sharedSkill
- mem-searchSkill
- pdfSkill
- pptxSkill
- self-improving-agentSkill
- skill-creatorSkill
- web-accessSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.