Repository navigation
Conversation
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.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Pi prints
[Skill conflicts]→description exceeds 1024 characters (1028)for browserwright on every start. This trims the frontmatter description to 916 characters.Why it matters
The overrun does not fail the load — the skill still works. But the warning sits in the same panel Pi uses to report real skill collisions (two skills claiming one name, where one silently loses). A permanent false alarm in that panel trains people to scroll past it, which is exactly when a real collision goes unnoticed.
What changed
Only the frontmatter
description:value, and only its last sentence.The old tail was
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.— it restated the opening sentence almost clause for clause. Replaced withDrives 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.So: 471 → 290 characters in that sentence, 1028 → 916 overall, 108 characters of headroom for the next trigger someone adds. Body of the skill is untouched.
Every trigger phrase is preserved verbatim, verified programmatically against the original list. Triggers are what decide whether the skill is discovered at all, so they were the one thing not traded away.
Test proof
Then the actual claim, checked against Pi's own skill loader rather than a hand-rolled YAML parse — loading this worktree's
skill/directory in isolation, the diagnostic is gone:Before the change, the same call against
mainreportedwarning description exceeds 1024 characters (1028).Interface evidence
N/A — no UI change. The evidence this warrants is the loader diagnostic above, which is the exact code path Pi's startup warning prints from (
dist/core/skills.js→validateDescription).Note on rollout
~/.agents/skills/browserwrightis a symlink to this repo's checkout, so the warning clears once this merges and the localmainpicks it up. No reinstall or republish needed — but the skill bundled into the published package tracksmain, so it should ride the next release rather than be hotfixed.