browser-debug-setup

One-time setup for a persistent debug browser on `127.0.0.1:9222` for `dev-browser --connect`. Use when browser work is needed but no reusable debug browser is running yet.

Quality

84%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

81%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is highly actionable with executable commands and strong validation/feedback loops, but it repeats the core 'don't reuse the Default profile' caution several times, slightly diluting token efficiency.

Suggestions

Consolidate the repeated 'do not point 9222 at the daily Default profile' warning into a single Rules entry and reference it once, instead of restating it in Google Chrome Path and After Setup.

Consider noting Linux/Windows equivalents (or explicitly scoping the skill to macOS) since the launch command and profile paths are macOS-only.

Dimension	Reasoning	Score
Conciseness	Mostly efficient with executable code, but the 'do not point 9222 at your daily Default profile' guidance is restated three times across the Rules, Google Chrome Path, and After Setup sections.	3 / 5
Actionability	Provides copy-paste ready curl, dev-browser, python3, rsync, and open -na commands covering the common macOS Chrome setup case end to end.	5 / 5
Workflow Clarity	Numbered Google Chrome Path sequence is paired with explicit validation (curl /json/version, 404/empty-output handling) and feedback loops (websocket fallback, lsof/kill/relaunch when the wrong Chrome steals 9222).	5 / 5
Progressive Disclosure	Well-organized self-contained sections with clear headers and no nested references; the small skill has no bundle files, so structure is good but there is nothing to progressively disclose.	4 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, distinct, and explicitly answers both what the skill does and when to use it. Minor expansion of natural trigger synonyms would round it out.

Dimension	Reasoning	Score
Specificity	Names the concrete target (persistent debug browser on 127.0.0.1:9222 for dev-browser --connect) rather than vague actions, but lists the single setup action rather than multiple comprehensive actions.	4 / 5
Completeness	Clearly states what it does (one-time setup for a persistent debug browser on 127.0.0.1:9222) and when to use it ('Use when browser work is needed but no reusable debug browser is running yet').	5 / 5
Trigger Term Quality	Includes natural phrases ('browser work', 'debug browser', 'dev-browser --connect') and an explicit 'Use when' clause, missing only a few common synonyms.	4 / 5
Distinctiveness Conflict Risk	The 127.0.0.1:9222 + dev-browser --connect niche is highly specific with a clear trigger, minimizing conflict with other skills.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: udecode/plate
Path: templates/plate-playground-template/.agents/skills/browser-debug-setup/SKILL.md
Commit: 9ec2c8e

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.