bun-test-basics

Use for bun:test syntax, assertions, describe/it, test.skip/only/each, and basic patterns.

Quality

63%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-test-basics/SKILL.md

Quality

Content

77%

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

This is a solid reference skill with excellent actionability—every section provides executable, concrete code examples. The main weakness is that the body content is longer than necessary, particularly the common matchers and CLI options sections which duplicate content that should primarily live in the referenced files. Trimming these inline sections to just the most essential items would improve both conciseness and progressive disclosure.

Suggestions

Trim the Common Matchers section to only the 5-6 most essential matchers (toBe, toEqual, toThrow, not) and move the comprehensive list to references/matchers.md

Reduce the CLI Options section to the 3-4 most common flags and defer the full list to references/cli-options.md

Remove the introductory sentence explaining what Bun's test runner is—Claude already knows this

Dimension	Reasoning	Score
Conciseness	The content is mostly efficient with good code examples, but includes some unnecessary explanations Claude already knows (e.g., 'Bun ships with a fast, built-in, Jest-compatible test runner' and 'Tests run with the Bun runtime and support TypeScript/JSX natively'). The common matchers section is quite extensive and could be trimmed or moved to a reference file. The common errors table adds modest value but some entries are obvious.	2 / 3
Actionability	All code examples are concrete, executable, and copy-paste ready. The CLI commands are specific with real flags and values. The test patterns, modifiers, parameterized tests, and matchers all provide fully working TypeScript examples.	3 / 3
Workflow Clarity	This is a reference/pattern skill rather than a multi-step workflow skill. The single-task nature (writing and running bun tests) is unambiguous. The CLI section clearly shows how to run tests, and the writing section clearly shows how to structure them. No destructive or batch operations require validation checkpoints.	3 / 3
Progressive Disclosure	The skill references `references/matchers.md` and `references/cli-options.md` with clear loading criteria, which is good. However, the inline content is quite long (~150+ lines) with extensive matcher and CLI listings that overlap with the referenced files. The matchers section and CLI options could be significantly trimmed since they're covered in references, making the main file more of an overview.	2 / 3
	Total	10 / 12 Passed

Description

50%

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 identifies a clear domain (bun:test) and lists relevant API features, which helps with selection. However, it lacks explicit actions the skill performs (e.g., 'write', 'debug', 'explain') and the trigger guidance is merged with capability listing rather than providing distinct 'when to use' guidance. The phrase 'basic patterns' is vague and doesn't aid selection.

Suggestions

Add explicit actions describing what the skill does, e.g., 'Generates and explains bun:test unit tests including syntax, assertions, describe/it blocks, test.skip/only/each patterns.'

Separate the 'when' clause more explicitly, e.g., 'Use when the user asks about writing or debugging Bun tests, bun:test syntax, or mentions test runners in a Bun project.'

Replace 'basic patterns' with specific terms like 'lifecycle hooks', 'expect matchers', or 'mock functions' to improve trigger term coverage and reduce vagueness.

Dimension	Reasoning	Score
Specificity	Names the domain (bun:test) and lists some specific features like assertions, describe/it, test.skip/only/each, but 'basic patterns' is vague and the description doesn't explain what concrete actions the skill performs (e.g., 'write tests', 'debug test failures').	2 / 3
Completeness	Has a 'Use for...' clause that partially addresses when to use it, and the listed items imply what it does, but the 'what' is weak—it doesn't clearly state what actions the skill performs (e.g., writing tests, explaining syntax). The 'when' is present but blended with the 'what'.	2 / 3
Trigger Term Quality	Includes relevant keywords like 'bun:test', 'assertions', 'describe/it', 'test.skip', 'test.only', 'test.each' which users might mention, but misses common variations like 'unit testing', 'test runner', 'bun testing', 'expect', or 'mock'.	2 / 3
Distinctiveness Conflict Risk	Specifying 'bun:test' helps distinguish it from generic testing skills, but 'assertions', 'describe/it', and 'basic patterns' could overlap with Jest or other test framework skills since these are common testing concepts.	2 / 3
	Total	8 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: secondsky/claude-skills
Commit: 5e92b71

Reviewed: about 2 months 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.