en un clic
browseruse-agent-bench
browseruse-agent-bench contient 6 skills collectées depuis lexmount, avec une couverture métier par dépôt et des pages de détail sur le site.
Skills dans ce dépôt
Create and integrate new modular agents for browseruse-bench (BaseAgent in browseruse_bench/agents/, registry import in __init__.py, entry in configs/agent_registry.yaml, runtime config in root config.yaml agents section). Use when a user asks to add/register a new agent, scaffold a custom agent, or implement a new agent based on external docs.
Generate and maintain PR review checklists from GitHub review threads for the current branch PR or a specified PR. Use when you need reviewer comments with exact code locations, nearby code snippets, and raw thread chat logs, and when you want continuously updated .pr/<pr_number>/review_checklist.md and .pr/<pr_number>/unresolved_checklist.md.
Use this skill whenever the user describes a benchmark experiment using any combination of these parameters — agent (e.g. browser-use, skyvern), model (e.g. deepseek, minimax, claude, gemini, gpt), data/benchmark (e.g. LexBench-Browser), browser (e.g. Chrome-Local, lexmount), and tasks (specific IDs or "all"). Trigger phrases include "跑实验 agent=xxx model=xxx", "跑实验 agent xxx model xxx", "run [model] on [tasks]", "eval [model] results", "re-run [model]", or any request that specifies an agent + model + task set to execute or evaluate. Also triggers on requests to chain run→eval pipelines, check experiment progress, or read final results.
Create GitHub pull requests for browseruse-bench with clear conventional-commit style titles and a review-ready body.
Update Mintlify documentation in docs/ for browseruse-bench, including adding new pages, enforcing .mdx files, and keeping English/Chinese navigation parity. Use when adding or editing docs pages, fixing missing/incorrect language variants, or updating docs/docs.json navigation.
Draft and track fixes for unresolved PR review threads. Use when you need to generate a solution draft markdown for the latest/current PR unresolved threads and keep `.pr/<pr_number>/review_checklist.md` plus `.pr/<pr_number>/unresolved_checklist.md` checkbox states synchronized as issues are fixed.