javascript-testing-patterns

Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development. Use when writing JavaScript/TypeScript tests, setting up test infrastructure, or implementing TDD/BDD workflows.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

The body is a well-organized, highly actionable catalog of executable testing patterns, but it is a voluminous monolith with no progressive disclosure into reference files and no workflow sequencing or validation checkpoints. Strengths are actionability; weaknesses are conciseness, workflow clarity, and file structure.

Suggestions

Split the large per-framework and per-pattern code (e.g., integration suites, React/hooks examples, mocking recipes) into reference files under references/ and link to them from a concise SKILL.md overview to improve progressive disclosure and conciseness.

Deduplicate overlapping examples (UserService appears with two different shapes) and trim the full inline integration test suites to representative snippets to tighten the token budget.

Add a short workflow with validation/feedback checkpoints for the riskier flows (e.g., integration DB setup/teardown, mocking global fetch) so multi-step processes are explicitly sequenced and verified.

Dimension	Reasoning	Score
Conciseness	The body avoids concept-explanation fluff and is mostly executable code, but it is an ~1000-line monolith with duplicate UserService implementations and full inline integration suites, so not every token earns its place. It sits above the padded/verbose anchor (1) but below the lean-and-efficient anchor (3).	2 / 3
Actionability	Examples are fully executable, copy-paste-ready TypeScript (config files, unit/integration/frontend tests, mocking, fixtures) with concrete assertions, matching the executable-and-complete anchor.	3 / 3
Workflow Clarity	Content is organized into labeled pattern sections, but there is no multi-step sequencing or validation/feedback checkpoint guidance, and the DB/integration setup is risky enough to warrant it. This fits the "sequence present but checkpoints missing" anchor rather than the checkpoint-rich anchor (3) or the unclear anchor (1).	2 / 3
Progressive Disclosure	All content is inline in a single large file with no reference bundle files, and per-framework/per-pattern material that should be split remains inline; headings provide organization, but it is far over the 50-line simple-skill threshold, so it lands at 2 rather than 1 (organized) or 3 (split with signaled references).	2 / 3
	Total	9 / 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 specific, complete, and distinct: it names concrete actions and frameworks, provides an explicit "Use when..." trigger clause, and occupies a clear niche unlikely to conflict with other skills. It uses third-person imperative voice with no fluff.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with named frameworks — "Implement comprehensive testing strategies using Jest, Vitest, and Testing Library for unit tests, integration tests, and end-to-end testing with mocking, fixtures, and test-driven development" — matching the multi-action anchor rather than the partial anchor at 2.	3 / 3
Completeness	Explicitly answers both what (comprehensive testing with named frameworks across unit/integration/e2e, mocking, fixtures, TDD) and when via an explicit "Use when..." clause, so the when is stated rather than merely implied.	3 / 3
Trigger Term Quality	Natural user-facing triggers are present ("writing JavaScript/TypeScript tests", "setting up test infrastructure", "TDD/BDD workflows"), giving good coverage of phrases a user would actually say rather than mere jargon.	3 / 3
Distinctiveness Conflict Risk	A clear JS/TS-testing niche anchored to specific frameworks (Jest, Vitest, Testing Library) with distinct triggers makes it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 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
skill_md_line_count	SKILL.md is long (1022 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Commit: e9f9b67

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.