Agent Browser Issue
SkillWeb & browsingLets your agent file a GitHub issue documenting a browser automation problem it hit.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the Agent Browser Issue skill
About this capability
Open a concise GitHub follow-up for reusable browser-use limitations. Use when browser automation is blocked by a likely tool-side issue that is worth fixing separately, especially for clicks, dropdowns, file inputs, focus traps, or other repeatable agent/browser failures.
What this skill tells your AI
The instructions your AI receives, as published by udecode/plate in .agents/skills/agent-browser-issue/SKILL.md and read by ahel’s review.
Handle $ARGUMENTS.
Use this only for likely reusable agent/browser tooling bugs. Do not use it for:
- auth or SSO gates
- manual human gates
- product bugs on the site itself
- one-off flaky noise with no minimal repro
Collect
Capture only the minimum:
- page or URL
- action attempted
- exact block
- expected vs actual
- minimal repro
- screenshot only if it adds signal
Issue
Open a GitHub issue with:
- a short title focused on the browser/tool failure
- label
agent:browser - concise body
Body shape:
## URL
<url>
## Action
<what the agent tried>
## Block
<what failed>
## Expected
<what should have happened>
## Actual
<what happened instead>
## Repro
1. ...
2. ...
3. ...
After
- if the browser/tool failure exposes a user-action parity gap, load
agent-native-reviewerand note that gap in the issue - link the issue in the task caveat or handoff
- keep moving if the product task is still otherwise fixable
Signals
- GitHub stars
- 17k
- Forks
- 996
- Last commit
- Sep 2026
Others that do the same job
Advanced
- Catalog kind
- skill
- Gateway key
agent-browser-issue-udecode- Source
- github.com/udecode/plate