bun-jest-migration

Use when migrating from Jest to Bun's test runner, import compatibility, mocks, and config.

Quality

75%

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 ./plugins/bun/skills/bun-jest-migration/SKILL.md

Quality

Content

80%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 content is highly actionable with executable code throughout and a clear step-by-step migration flow, organized into well-labeled sections with a signaled reference. It loses a little on conciseness from minor duplication and on workflow clarity from a thin verification loop for a batch operation.

Suggestions

Strengthen the final migration step into an explicit validate-then-retry loop: run `bun test`, list the categories of failures to fix, and re-run until green, rather than only inspecting the first 50 lines.

Move the full 'API Compatibility' tables into references/compatibility-matrix.md and keep only the highest-churn items inline to reduce duplication with the 'Common Errors' table.

De-duplicate module mocking guidance that currently appears under both 'Mock Migration' and 'Common Migration Issues'.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean—tables, short code blocks, and minimal prose—and largely avoids explaining concepts Claude already knows, with only minor repetition (e.g., module mocking shown in both 'Mock Migration' and 'Common Migration Issues').	4 / 5
Actionability	Copy-paste ready bash and TypeScript snippets cover the common migration cases (package removal, import swaps, mock/spy/timer conversion, config translation, and error fixes), with a concrete error-to-cause-to-fix table.	5 / 5
Workflow Clarity	The 'Step-by-Step Migration' section gives a clear numbered sequence ending in 'Run and fix', but the verification step is a single `bun test 2>&1 \| head -50` rather than explicit validate-then-retry feedback loops for what is effectively a batch refactor.	4 / 5
Progressive Disclosure	The body is well-sectioned into a quick overview and a clearly signaled one-level reference ('Load references/compatibility-matrix.md when: ...'), though the referenced bundle file is not present to confirm and some detailed compatibility content remains inline that could live in that reference.	4 / 5
	Total	17 / 20 Passed

Description

70%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, uses the required third-person voice with an explicit 'Use when' trigger, and occupies a distinct niche. It is moderately specific—naming migration areas rather than concrete actions—and would benefit from sharper action verbs.

Suggestions

Replace area nouns ('import compatibility, mocks, and config') with concrete actions such as 'convert jest.config.js to bunfig.toml, replace jest.mock() with mock.module(), and update imports from @jest/globals to bun:test'.

Add a trigger synonym such as 'when converting a Jest test suite to Bun' to widen natural phrasing coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Jest-to-Bun migration) and several concrete migration facets ('import compatibility, mocks, and config'), but these are areas rather than distinct executable actions like 'convert jest.config.js to bunfig.toml'.	3 / 5
Completeness	Explicit 'Use when...' trigger ('Use when migrating from Jest to Bun's test runner') pairs a clear what with a clear when, though the 'when' is a single clause without enumerating concrete trigger phrases.	4 / 5
Trigger Term Quality	'Jest', 'Bun's test runner', 'mocks', and 'config' are natural terms users would say when migrating, though common phrasings like 'migrate Jest tests' and synonyms are only partially covered.	4 / 5
Distinctiveness Conflict Risk	The Jest-to-Bun migration niche is narrow and specific, with triggers unlikely to collide with other skills.	5 / 5
	Total	16 / 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
referenced_paths_exist	Referenced path issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-jest-migration/SKILL.md
Commit: ad16332

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