unit-test

Neo.mjs Playwright unit-test author/executor workflow. Standard Playwright patterns will fail. Triggers: Use before writing, modifying, fixing, or explicitly running unit tests. Do not trigger solely because PR review inspects a diff containing, adding, or moving tests, or checks placement; pr-review owns review evidence.

Quality

83%

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

78%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 SKILL.md body is an efficient, well-structured pointer that delegates detail to a single clearly-signaled reference file. Its only weakness is that the body itself carries no executable test-authoring guidance or validation steps, relying entirely on the reference.

Suggestions

Add a one-line inline summary of the core workflow (e.g. the analyze→plan→implement→verify loop) so the body is actionable without immediately opening the reference.

Surface the key execution command (e.g. `npm run test-unit -- <path>`) inline so the most common action is executable from SKILL.md alone.

Mention the critical import constraint (import `src/Neo.mjs` + `src/core/_export.mjs`) briefly in the body, since it is the most common failure mode noted in the reference.

Dimension	Reasoning	Score
Conciseness	The two-sentence body is lean and assumes Claude's competence; every token earns its place and nothing over-explains concepts Claude already knows.	5 / 5
Actionability	The body gives a concrete pointer ('read and follow `.agents/skills/unit-test/references/unit-test.md`') but the executable test-authoring detail is delegated to the reference, leaving the body itself incomplete as standalone guidance.	3 / 5
Workflow Clarity	A clear single action with a well-defined trigger and an explicit boundary clause ('Review-only placement/idiom audits stay under `pr-review`'), though validation checkpoints live only in the referenced file rather than the body.	4 / 5
Progressive Disclosure	The body is a clean overview pointing to one real, one-level-deep bundle file (references/unit-test.md) via an exact, clearly signaled path; content is appropriately split and easy to navigate.	5 / 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 concise, concrete, and explicitly pairs a clear 'what' with an explicit 'Triggers' clause plus a well-drawn boundary against the pr-review skill. It is a strong, low-conflict trigger description.

Dimension	Reasoning	Score
Specificity	Names the domain ('Neo.mjs Playwright unit-test author/executor workflow') and lists several concrete actions ('writing, modifying, fixing, or explicitly running unit tests') plus the concrete warning 'Standard Playwright patterns will fail', with only minor coverage gaps.	4 / 5
Completeness	It explicitly answers both what ('Neo.mjs Playwright unit-test author/executor workflow; Standard Playwright patterns will fail') and when ('Triggers: Use before writing, modifying, fixing, or explicitly running unit tests') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user phrases like 'writing', 'modifying', 'fixing', and 'running unit tests' appear with an explicit 'Triggers:' clause; a few common synonyms are absent, so it sits just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	A clear niche (Neo.mjs Playwright unit tests) with an explicit non-trigger boundary ('Do not trigger solely because PR review inspects a diff... pr-review owns review evidence'), minimizing conflict with the pr-review skill.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: neomjs/neo
Path: .agents/skills/unit-test/SKILL.md
Commit: 210c03c

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.