browser-use

Automates browser interactions for social media management across Instagram, LinkedIn, and X. Handles posting, DMs, connection requests, lead scraping, and monitoring. Use when the user needs to navigate, interact with, or extract data from approved websites.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

77%

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

The content is highly actionable with clear, validated workflows, but it leans long for a single file and does not leverage progressive disclosure to offload detailed per-platform workflows into separate reference files. Tightening prose and splitting reference material would lift conciseness and progressive disclosure.

Suggestions

Trim repeated prose in the Autonomy Rules, Rate Limiting, and Troubleshooting sections to concrete rules only; the core command reference already carries the actionable detail.

Move the per-platform Common Workflows (LinkedIn post, Instagram DMs, X monitoring) into a separate `WORKFLOWS.md` referenced one level deep from the body, keeping SKILL.md as an overview.

Consolidate the Domain Allowlist, Always Blocked, and Prompt Injection Defense sections, which overlap on the same trust-boundary rules, to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	The body is dense with executable commands and largely assumes Claude's competence, but at ~450 lines it carries repeated prose around autonomy, security, and troubleshooting that could be tightened; it is mostly efficient but includes some unnecessary elaboration.	2 / 3
Actionability	It provides fully executable, copy-paste-ready `browser-use` commands with concrete flags and indices throughout the Commands and Common Workflows sections, matching the anchor for specific, executable examples.	3 / 3
Workflow Clarity	Workflows are clearly sequenced with explicit validation checkpoints — 'screenshot before and after', `wait text` confirmations after posting, and a STOP-and-confirm feedback loop with a screenshot for destructive actions.	3 / 3
Progressive Disclosure	The skill is a single ~450-line file with no bundle references and only one external README URL; sections are well-organized, but the per-platform workflow and reference-style content is kept inline where it could be split into one-level-deep reference files.	2 / 3
	Total	10 / 12 Passed

Description

100%

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 strong: it names concrete capabilities, uses natural trigger terms, includes an explicit 'Use when...' clause, and occupies a distinct niche. It avoids verbosity and over-claims. No changes needed.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete actions — 'posting, DMs, connection requests, lead scraping, and monitoring' — matching the anchor for listing several specific actions rather than vague language.	3 / 3
Completeness	It states both what the skill does ('Handles posting, DMs, connection requests, lead scraping, and monitoring') and when to use it via an explicit 'Use when the user needs to navigate, interact with, or extract data from approved websites.' clause.	3 / 3
Trigger Term Quality	It uses natural terms a user would say — 'social media management', 'Instagram, LinkedIn, and X', 'posting, DMs', 'lead scraping' — giving good coverage of common phrasings.	3 / 3
Distinctiveness Conflict Risk	The niche is clear — browser automation for social media management across three named platforms — making it unlikely to trigger for unrelated skills.	3 / 3
	Total	12 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: wanikua/danghuangshang
Path: skills/browser-use/SKILL.md
Commit: acea185

Reviewed: about 13 hours 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.