Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/optimize-agent-browsing
Analyze an OpenClaw agent's browser usage and recommend browsy migration
Passed 21 of 22 test cases with the skill, and 4 of 22 without it.
and 24 more in the full report
17 fixed4 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 17 test cases the skill fixed. Same model, same prompt, with and without the skill.
What specific configuration key must be enabled in the OpenClaw plugin settings after installing `openclaw-browsy` for the agent in `agents/bot.yaml`?
| Checked | Without skill | With skill |
|---|---|---|
| The migration requirements specify configuring `preferBrowsy: true` in the plugin setup. | Missed | Passed |
The instructions your model reads when the skill loads.
Analyze an OpenClaw agent's browser tool usage patterns and identify which calls can be migrated from Playwright/CDP to browsy for faster, lighter execution.
/optimize-agent-browsing path/to/agent-config.yaml
Reviews how an agent uses browser tools and produces a migration plan:
browser, web_browser, playwright_browser, browse_web)tables/find toolsbrowser.navigate(url) → browsy_browsebrowser.click(selector) → browsy_click (by element ID instead of CSS selector)browser.type(selector, text) → browsy_type_textbrowser.get_text(selector) → browsy_findbrowser.screenshot() → keep Playwright (browsy has no pixel rendering)test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.