skills.rest
udecode
udecodeOFFICIAL
Explore all skills by this author →
WebsiteGitHub

agent-browser-issue

Create GitHub issues with minimal reproductions for browser automation blockers.

434|33|Updated Jul 27, 2025
Search Tags:#issue-tracking#browser-automation#bug-report#agent-browser#minimal-repro#tooling-blocker
One-click install
npx skills add https://github.com/udecode/kitcn --skill agent-browser-issue
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-browser-issue
Source: https://github.com/udecode/kitcn/tree/main/.agents/skills/agent-browser-issue
Command: npx skills add https://github.com/udecode/kitcn --skill agent-browser-issue

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open concise GitHub follow-ups for reusable dev-browser or agent-browser 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.

Core Features & Use Cases

  • Create a GitHub issue with a short, focused title and label agent:browser for browser-tooling blockers.
  • Collect a minimal repro: URL, action attempted, exact block, expected vs actual, reproducible steps, and a screenshot if signal is enhanced.
  • Provide a structured issue body with sections for URL, Action, Block, Expected, Actual, Repro steps.

Quick Start

Open a GitHub issue summarizing the browser/tool limitation with a minimal repro.

Frequently Asked Questions about agent-browser-issue

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I report browser automation blockers as GitHub issues?▼

To report browser automation blockers, create a GitHub issue with a focused title, label it `agent:browser`, and provide a minimal reproduction including the URL, attempted action, and expected versus actual behavior.

What information should a minimal reproduction include for agent-browser tooling bugs?▼

A minimal reproduction for agent-browser tooling bugs should include the target URL, the action attempted, the exact block encountered, expected versus actual behavior, reproducible steps, and a screenshot if it enhances the signal.

When should I open a GitHub issue for a browser automation failure?▼

You should open a GitHub issue for a browser automation failure when you encounter a repeatable, tool-side block during actions like clicks, dropdowns, file inputs, or focus traps that is worth fixing separately.

How do I structure a bug report for dev-browser focus traps and click failures?▼

Structure the bug report using sections for URL, Action, Block, Expected, Actual, and Repro steps to clearly document dev-browser focus traps and click failures, ensuring the issue is labeled `agent:browser`.

Can I use this approach for any browser automation bug I encounter?▼

This approach is specifically for reusable dev-browser or agent-browser limitations that are likely tool-side issues, not for general website bugs or one-off automation script failures.

Related Skills

Explore More Software Engineering Skills→
proffesor-for-testingproffesor-for-testing
436

bug-reporting-excellence

Create structured bug reports with reproduction steps and environment details.

Community
Advanced
muklesmukles

agent-browser-issue

Create labeled GitHub issues for repeatable browser automation failures.

Community
Intermediate
AllBeingsFutureAllBeingsFuture
9

browser-navigate

Navigate the browser to a specified URL with a required protocol.

Community
Basic
luongldptitluongldptit

project-flow-ops

Classify GitHub issues and pull requests into Linear execution lanes.

Community
Intermediate