skills.rest
mukles
muklesCOMMUNITY
Explore all skills by this author →
Website𝕏@mukles_devGitHub

agent-browser-issue

Create labeled GitHub issues for repeatable browser automation failures.

Updated Sep 16, 2025
Search Tags:#debugging#browser-automation#issue-triage#repro#github-issues#agent-browser
One-click install
npx skills add https://github.com/mukles/platejs-markdown-converter --skill agent-browser-issue-mukles
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agent-browser-issue
Source: https://github.com/mukles/platejs-markdown-converter/tree/main/.agents/skills/agent-browser-issue
Command: npx skills add https://github.com/mukles/platejs-markdown-converter --skill agent-browser-issue-mukles

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Open concise GitHub follow-ups for reusable dev-browser or agent-browser limitations when browser automation is blocked by a likely tool-side issue that deserves separate attention.

Core Features & Use Cases

  • Create short GitHub issues labeled agent:browser with a focused title that captures the browser/tool failure.
  • Collect a minimal, structured repro: URL, action attempted, exact block, expected vs actual, minimal repro steps, and a screenshot if it adds signal.
  • Use for repeatable browser automation failures (e.g., clicks, dropdowns, file inputs, focus traps) and link the issue to product tasks or handoffs for quick triage.

Quick Start

Describe the blocked browser action and failure so a concise GitHub issue can be created for reuse.

Frequently Asked Questions about agent-browser-issue

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

FAQPage Schema
How do I create a GitHub issue for browser automation failures like blocked clicks or dropdowns?▼

To create a GitHub issue for browser automation failures, document the blocked action with a minimal repro, expected vs actual results, and apply the `agent:browser` label for structured triage.

What is the best way to document repeatable browser tool limitations for developer triage?▼

The best way to document repeatable browser tool limitations is opening concise GitHub issues with a focused title, minimal repro steps, URL, and a screenshot if it adds signal, labeled `agent:browser`.

When should I open a separate GitHub issue for a dev-browser failure instead of debugging locally?▼

You should open a separate GitHub issue for a dev-browser failure when the automation is blocked by a likely tool-side issue, such as focus traps or file inputs, that warrants a separate fix.

How do I link browser automation issues to product tasks for quick triage?▼

To link browser automation issues to product tasks, create GitHub issues with the `agent:browser` label and connect them to product tasks or handoffs, ensuring the task caveat is properly referenced for structured triage.

What minimal repro information should I include when reporting agent-browser issues?▼

When reporting agent-browser issues, include the URL, action attempted, exact block, expected vs actual behavior, minimal repro steps, and a screenshot if it adds signal to the GitHub issue body.

Related Skills

Explore More Software Engineering Skills→
softmgsoftmg

agent-browser

Guide Codex to reproduce local browser scenarios and capture evidence.

Official
Intermediate
DimillianDimillian
3.9k

github

Automate GitHub issue, PR, CI, and API tasks via the gh CLI.

Community
Advanced
udecodeudecode
434

agent-browser-issue

Create GitHub issues with minimal reproductions for browser automation blockers.

Official
Intermediate
louisburroughslouisburroughs

github-issues

Create, update, label, and query GitHub issues via MCP tools.

Community
Basic