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

selenium

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

Quality

63%

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/selenium/SKILL.md

Quality

Content

68%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 concrete, executable CLI commands and a clear connection-state workflow. Its weaknesses are a concept-explaining intro and missing validation/verification steps around action execution.

Suggestions

Delete or trim the opening paragraph explaining what Selenium is and who uses it; Claude already knows this.

Add an explicit validation step after running actions (e.g. check the `output` field and confirm success) and a confirmation checkpoint before destructive/batch actions.

Consider moving the large flag-options table and detailed `clientAction` state reference into a separate reference file to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and command-driven, but the opening paragraph ("Selenium is a popular open-source framework for automating web browsers. Developers and QA engineers use it...") explains a concept Claude already knows, matching the anchor for mostly efficient content with some unnecessary explanation.	3 / 5
Actionability	The skill provides fully executable, copy-paste-ready commands throughout (npm install, membrane login, connection ensure/get, action list/run, request) plus a concrete flag-options table covering the common cases.	5 / 5
Workflow Clarity	The connection workflow has a clear sequence and state-based branching (READY/BUILDING/CLIENT_ACTION_REQUIRED) with polling, but running actions against external data has no validation/verification checkpoints, and the rubric caps workflow clarity at 3 for destructive or batch operations lacking validation.	3 / 5
Progressive Disclosure	No bundle files exist, so all content lives in a single SKILL.md with well-organized, clearly headed sections and no nested references; at ~150 lines it is a touch larger than ideal but well structured, fitting the anchor for good structure with minor organization gaps.	4 / 5
	Total	15 / 20 Passed

Description

57%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 successfully includes both a capability summary and an explicit use-trigger, anchored clearly to Selenium. Its main weakness is generic, non-concrete action verbs and missing natural synonyms a user would actually say.

Suggestions

Replace generic verbs with concrete Selenium actions, e.g. "automate browser interactions, run cross-browser web tests, and scrape page content".

Add natural trigger terms users say, such as "browser automation", "web testing", "QA", or "cross-browser tests".

Tighten the when-clause to specific intents, e.g. "Use when the user wants to automate browser actions or write/run Selenium web tests."

Dimension	Reasoning	Score
Specificity	The description names the Selenium domain but its stated actions ("Manage data, records, and automate workflows") are generic rather than concrete Selenium capabilities like browser automation or web testing, matching the anchor for naming the domain with minimal/generic actions.	2 / 5
Completeness	Both a "what" (Selenium integration, manage data/records, automate workflows) and an explicit "when" ("Use when the user wants to interact with Selenium data") are present, though the when-clause is somewhat generic rather than tied to concrete triggers.	4 / 5
Trigger Term Quality	"Selenium" and "interact with Selenium data" provide relevant keywords, but common natural variations users would say (browser automation, web testing, QA, cross-browser) are missing, fitting the anchor for some relevant keywords without synonyms.	3 / 5
Distinctiveness Conflict Risk	The "Selenium" anchor carves out a distinct niche with low conflict risk, though the generic "manage data, records, and automate workflows" phrasing leaves minor overlap with general automation skills.	4 / 5
	Total	13 / 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/selenium/SKILL.md
Commit: f484c82

Reviewed: 4 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.