udecode/plate

agent-browser-issue

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.

First seen Mar 30, 2026

Installation

$ npx skills add udecode/plate --skill agent-browser-issue

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from udecode/plate · top by installs.

npx skills add udecode/plate

Browse all from udecode/plate

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 16.6K
License LICENSE
Default branch main
Open issues 10
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

More metadata
skiller
{"source":".agents\/rules\/agent-browser-issue.mdc"}

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,443 B
  • docs SUMMARY.md 300 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 11 installs

SKILL.md

Agent Browser Issue

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-reviewer and 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