Name: browserstack
Rating: 55.2 (1 reviews)
Author: membranedev

browserstack

BrowserStack integration. Manage data, records, and automate workflows. Use when the user wants to interact with BrowserStack data.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/browserstack/SKILL.md

Quality

Content

76%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 and well-structured, with executable commands and a clear connection workflow. Its main weakness is the absence of validation/confirmation safeguards around the destructive delete operations, which caps workflow clarity.

Suggestions

Add an explicit validation/confirmation step before destructive actions (e.g. list the build/project and confirm with the user before running delete-build/delete-project) to raise workflow clarity above the cap.

Consider moving the 20-row "Popular actions" table into a separate reference file with a one-line pointer, keeping SKILL.md as a leaner overview.

Trim the opening descriptive paragraph about what BrowserStack is, since Claude already knows the platform.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean command examples and tables, with only minor over-explanation such as the opening paragraph defining what BrowserStack is and the "rather than auth plumbing" phrasing Claude could do without.	4 / 5
Actionability	It provides copy-paste-ready commands for install, login, connection ensure/get, action list/run, and proxy requests, plus a concrete action-key table and proxy flag table that cover the common cases.	5 / 5
Workflow Clarity	The connection-readiness flow is well sequenced with state handling and a poll-again feedback loop, but destructive operations (delete build/project/app/session) are listed with no validation or confirmation steps, capping this dimension at 3 per the destructive-operations rule.	3 / 5
Progressive Disclosure	Structure is clean with well-labeled sections and no nested references, and no bundle files are needed; the large inlined 20-row action table is the only content that arguably belongs in a separate reference file.	4 / 5
	Total	16 / 20 Passed

Description

48%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 pairs an explicit use-trigger with a distinctive product name, but its capability statement relies on generic abstractions ("manage data, records, automate workflows") instead of concrete BrowserStack actions. Tightening the what-clause with real operations would lift specificity and completeness.

Suggestions

Replace "Manage data, records, and automate workflows" with concrete BrowserStack actions such as listing builds/sessions, uploading apps, and retrieving device/network logs.

Broaden trigger terms beyond the product name to include natural task phrases users say, e.g. cross-browser testing, mobile device testing, BrowserStack builds and sessions.

Make the "when" clause more specific by tying it to testing scenarios (e.g. "Use when running or debugging tests on BrowserStack browsers and devices").

Dimension	Reasoning	Score
Specificity	It names the domain ("BrowserStack integration") but the actions are generic and abstract ("Manage data, records, and automate workflows") rather than concrete BrowserStack operations like builds, sessions, or device testing.	2 / 5
Completeness	It has an explicit "Use when the user wants to interact with BrowserStack data" trigger, but the "what" ("Manage data, records, and automate workflows") is vague, so it does not reach the clear-what-plus-clear-when of anchor 4.	3 / 5
Trigger Term Quality	"BrowserStack" is a strong natural proper-noun trigger a user would actually say, but coverage is narrow — only the product name repeats, with no task-level synonyms (cross-browser testing, builds, sessions, devices).	3 / 5
Distinctiveness Conflict Risk	The BrowserStack proper noun gives it a clear niche with minimal conflict risk, though the generic "data, records, workflows" phrasing introduces minor overlap with other data-management skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/browserstack/SKILL.md
Commit: f484c82

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.