From 73cf32edc8e21e5611277cde44413e18304b19aa Mon Sep 17 00:00:00 2001 From: leeguooooo Date: Thu, 11 Jun 2026 18:30:29 +0900 Subject: [PATCH] docs(skill): encourage agents to file UX feedback to GitHub issues Add a prominent callout near the top of the core skill asking agents that hit a rough edge (confusing error, stale @ref, occluded click, flaky wait, missing feature) to open a quick issue at https://github.com/leeguooooo/agent-browser-stealth/issues with the command and expected-vs-actual. Agent-filed friction is the cheapest, highest-signal way to sharpen the tool (the Hermes dogfood runs already proved this). --- skill-data/core/SKILL.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/skill-data/core/SKILL.md b/skill-data/core/SKILL.md index e7394a5..c5ad2d5 100644 --- a/skill-data/core/SKILL.md +++ b/skill-data/core/SKILL.md @@ -15,6 +15,13 @@ Most normal web tasks (navigate, read, click, fill, extract, screenshot) are covered here. Load a specialized skill when the task falls outside browser web pages — see [When to load another skill](#when-to-load-another-skill). +> **Hit a rough edge? Please report it.** If a command surprised you — a +> confusing error, a stale `@ref`, an occluded click, a flaky wait, a missing +> feature, or anything that cost you extra turns — open a quick issue at +> **** with the exact +> command and what happened vs. what you expected. Agent-filed friction reports +> are how this tool gets sharper; a 30-second issue is genuinely valuable. + ## The core loop ```bash