From 65207d1bd5d886fefce23b93d279c81e325d4ac8 Mon Sep 17 00:00:00 2001 From: Randy Date: Tue, 27 Oct 2026 18:33:03 +0800 Subject: [PATCH] fix(skill): keep the frontmatter description under Pi's 1024-char cap MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Pi warns at startup that browserwright's description exceeds 1024 characters (1028) in `[Skill conflicts]`. The description never fails the load, but a warning on every start trains people to ignore the panel that also reports real skill collisions. Drop only the trailing sentence's redundancy: it restated the opening paragraph ("Unified browser entrypoint... operate a user's real browser or an isolated Chrome... navigation, interaction, screenshots, crawling/scraping"). The replacement keeps the same two facts — extension backend or isolated Chrome over CDP, and the reusable site-skill layer — in 290 characters instead of 471. Every trigger phrase is preserved verbatim; they decide whether the skill is discovered at all. 1028 -> 916 characters, leaving 108 of headroom for the next trigger someone adds. --- skill/SKILL.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/skill/SKILL.md b/skill/SKILL.md index f570023..7990442 100644 --- a/skill/SKILL.md +++ b/skill/SKILL.md @@ -1,7 +1,7 @@ --- name: browserwright description: > - Unified browser entrypoint for code agents. Use when an AI/code agent needs to operate a user's real browser or an isolated Chrome: open pages, click, type, fill forms, submit workflows, capture screenshots, scrape/extract page data, inspect DOM/network state, summarize what is on a page, or automate reusable browser tasks. Triggers include "use the browser", "open this page", "operate my browser", "control my Chrome", "screenshot this URL/page", "scrape this page/site", "extract data from the page", "fill out this form", "click this button", "summarize this page", "test this web app in a browser", "help me with the page I'm on", "operate my current tab", "attach to my active page", "browserwright", and "browserwright-daemon". This is the standard browser automation surface for code agents: it can drive the user's current browser via extension backend or launch/drive an isolated Chrome via CDP, with primitives for navigation, interaction, screenshots, crawling/scraping, page inspection, and reusable site skills. + Unified browser entrypoint for code agents. Use when an AI/code agent needs to operate a user's real browser or an isolated Chrome: open pages, click, type, fill forms, submit workflows, capture screenshots, scrape/extract page data, inspect DOM/network state, summarize what is on a page, or automate reusable browser tasks. Triggers include "use the browser", "open this page", "operate my browser", "control my Chrome", "screenshot this URL/page", "scrape this page/site", "extract data from the page", "fill out this form", "click this button", "summarize this page", "test this web app in a browser", "help me with the page I'm on", "operate my current tab", "attach to my active page", "browserwright", and "browserwright-daemon". Drives the user's browser via the extension backend, or an isolated Chrome over CDP, with primitives for navigation, interaction, screenshots, crawling, and reusable site skills. allowed-tools: Bash(browserwright:*), Bash(browserwright-daemon:*) ---