agentleFS
Sign inStart free
udecodeudecode/better-convex/.agents/skills/agent-browser-issue/SKILL.md

agent-browser-issue

Skill452 starsChanged 23 days agoApache-2.0View on GitHub

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.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this only for likely reusable agent or browser tooling bugs.

    line 15
  2. Very specific:

    if the browser or tool failure exposes a user-action parity gap, load agent-native-reviewer and note that gap in the issue

    line 67
  3. Distinctive:

    keep moving if the product task is still otherwise fixable

    line 70

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Agent Browser Issue

Handle $ARGUMENTS.

Use this only for likely reusable agent or 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 or 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 or 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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free