agent-browser-issue

Create GitHub issues for browser limitations using the GitHub API.

Updated Jul 2, 2026
One-click install
npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill agent-browser-issue-krishna-cyber
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser-issue
Source: https://github.com/krishna-cyber/plate_js_rich_text_editor/tree/main/.agents/skills/agent-browser-issue
Command: npx skills add https://github.com/krishna-cyber/plate_js_rich_text_editor --skill agent-browser-issue-krishna-cyber

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps to quickly and effectively create GitHub issues for browser-related limitations, streamlining the process of reporting and addressing tooling bugs.

Core Features & Use Cases

  • Concise Issue Creation: Automatically generates a GitHub issue with structured information about browser failures.
  • Specific Issue Reporting: Focuses on tool-side issues, excluding auth gates, product bugs, or one-off flakiness.
  • Use Case: When your automation tool fails on a browser due to a known issue like clicks or dropdowns, use this Skill to create a GitHub issue with all necessary details.

Quick Start

Generate a GitHub issue for a browser issue by providing a brief summary of the blockage.

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 a browser automation limitation?

To create a GitHub issue for browser automation limitations, you provide a brief summary of the blockage, and the tool generates a structured issue using the GitHub API and predefined templates to capture necessary details.

What types of browser issues should be reported as GitHub issues?

Browser issues suitable for GitHub issue reporting include tool-side failures such as broken clicks or dropdown malfunctions. Auth gates, product bugs, and one-off flakiness are explicitly excluded from issue creation.

How do I report a browser-use tool failure on GitHub?

You report a browser-use tool failure by providing a concise summary of the blockage. The tool then automatically generates a structured GitHub issue targeting the specific tool-side limitation.

Does this issue creation tool report product bugs and authentication gates?

No, this issue creation tool does not report product bugs or authentication gates. It specifically targets tool-side browser limitations and excludes auth gates, product bugs, and one-off flakiness from issue creation.

What is the best way to track browser-use limitations on GitHub?

The best way to track browser-use limitations is using structured issue templates via the GitHub API. This ensures concise reporting of tool-side failures like click or dropdown issues with all necessary details.

Do I need a GitHub API token to generate browser issue reports?

Generating browser issue reports requires the GitHub API and structured issue templates to accurately document tool-side limitations. You provide a brief summary of the blockage to initiate the issue creation process.