Name: headless-testing
Rating: 59.2 (1 reviews)
Author: membranedev

headless-testing

Headless Testing integration. Manage Tests, Projects, Environments, Users, Roles. Use when the user wants to interact with Headless Testing data.

Quality

68%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/headless-testing/SKILL.md

Quality

Content

75%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 a validated connection state-machine, but it spends tokens explaining headless testing itself and leaves a dangling Step 2 reference that slightly muddies the workflow.

Suggestions

Remove or trim the introductory paragraph defining headless testing and the skeletal Overview section, since Claude already knows this.

Label the "Searching for actions" section as "Step 2" (or reword the "skip to Step 2" cues) so the cross-references resolve.

Consider moving the 17-row actions table into a referenced file (e.g. ACTIONS.md) to keep SKILL.md a lean overview.

Dimension	Reasoning	Score
Conciseness	Mostly efficient command-and-table reference, but the opening paragraph ("Headless Testing is a tool for automated website testing in a browser environment without a graphical user interface...") explains a concept Claude already knows, and the sparse "Headless Testing Overview" section adds little.	3 / 5
Actionability	Provides copy-paste-ready, executable commands for the full workflow (install, login, connection ensure, action list/run, request proxy) with a 17-row actions table and a flags table covering the common cases.	5 / 5
Workflow Clarity	The connection flow has explicit state validation and feedback loops (READY / CLIENT_ACTION_REQUIRED / CONFIGURATION_ERROR with re-polling), but the repeated "skip to Step 2" references point to a Step 2 that is never labeled, a minor sequence gap.	4 / 5
Progressive Disclosure	Well organized into clear section headers with no nested references, but the sizeable inline "Popular actions" table and proxy flags could live in a separate reference file; the sparse Overview section is a minor organization gap.	4 / 5
	Total	16 / 20 Passed

Description

62%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 clearly identifies the product and includes an explicit Use-when clause, but it leans on one generic verb and a circular trigger, leaving the specificity and trigger-term coverage at the midpoint.

Suggestions

Replace the generic verb "Manage" with distinct concrete actions (e.g. "Run headless browser tests, review test runs, manage builds and screenshots").

Expand the trigger phrase with natural synonyms users say, e.g. "Use when the user wants to run headless browser tests, automate website testing in CI/CD, or take cross-browser screenshots."

Tighten the when clause so it references concrete intents rather than restating "Headless Testing data".

Dimension	Reasoning	Score
Specificity	Names the domain ("Headless Testing integration") and enumerates concrete entities ("Tests, Projects, Environments, Users, Roles") but relies on a single generic verb ("Manage"), so the actions themselves are not distinct or comprehensive.	3 / 5
Completeness	Answers both what ("Manage Tests, Projects, Environments, Users, Roles") and when ("Use when the user wants to interact with Headless Testing data"), but the when clause is somewhat circular and lacks multiple concrete trigger phrases.	4 / 5
Trigger Term Quality	Contains the core term "Headless Testing" and entity names, but misses natural synonyms a user would say (e.g. "browser testing", "automated testing", "screenshot testing") and file/format extensions.	3 / 5
Distinctiveness Conflict Risk	The named product "Headless Testing" gives a clear niche and the trigger is product-specific, though the generic CRUD entities ("Manage Tests, Projects...") carry minor overlap risk with other management skills.	4 / 5
	Total	14 / 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/headless-testing/SKILL.md
Commit: f484c82

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