CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-jest-migration

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

63

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

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
SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A highly actionable migration guide with excellent before/after code and command coverage, weakened by duplicated quick/step-by-step sections, contradictory timer API guidance, and a progressive-disclosure section that points to a reference file that is missing from the bundle.

Suggestions

Merge "Quick Migration" and "Step-by-Step Migration" into a single sequenced section to remove the duplicated remove-deps/update-script/run-tests steps.

Create the referenced `references/compatibility-matrix.md` (currently absent from the bundle) and move the full API compatibility tables and Common Errors table into it, keeping only the frequently-needed mappings in SKILL.md.

Resolve the timer guidance contradiction: the "Requires Changes" table, the Timer Migration section, and the "Timer Functions Missing" issue section give three inconsistent accounts of jest.useFakeTimers/advanceTimersByTime support.

DimensionReasoningScore

Conciseness

Mostly lean migration-delta tables and code, but "Quick Migration" and "Step-by-Step Migration" repeat the same sequence (remove Jest deps, update test script, run tests), the mock examples restate the API compatibility table, and the timer guidance is internally contradictory ("Requires Changes" vs "Now supported" vs "timer support is limited").

3 / 5

Actionability

Fully executable, copy-paste-ready commands (`bun remove jest ts-jest ...`, `bun test --update-snapshots`) and complete before/after code for imports, mocks, spies, timers, snapshots, and config translation cover the common migration cases.

5 / 5

Workflow Clarity

The Step-by-Step Migration section gives a clear 5-step sequence ending in "Run and fix" with a first-errors command, plus a Common Errors lookup table, but there is no explicit validate-then-proceed feedback loop for a workflow that removes dependencies, matching anchor 4 rather than 5.

4 / 5

Progressive Disclosure

The "When to Load References" section is clearly signaled, but the referenced `references/compatibility-matrix.md` does not exist (no references/ directory is bundled), and the full API compatibility tables that belong in such a reference are inlined in SKILL.md.

3 / 5

Total

15

/

20

Passed

Description

78%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.

A concise, third-person description with an explicit and specific 'Use when' trigger covering a well-defined niche. Its main weakness is that capabilities are listed as topics (import compatibility, mocks, config) rather than concrete actions, leaving the 'what' implicit.

DimensionReasoningScore

Specificity

Names the domain and several concrete capability areas ("test runner, import compatibility, mocks, and config"), but these are topic nouns rather than explicit verb actions, so coverage is good but not fully comprehensive as anchor 5 requires.

4 / 5

Completeness

An explicit "Use when migrating from Jest to Bun's test runner" clause answers 'when' concretely, and the topic list answers 'what', but the what is embedded in the when-clause rather than stated as separate explicit capabilities, matching anchor 4 rather than 5.

4 / 5

Trigger Term Quality

"migrating", "Jest", "Bun's test runner", "mocks", and "config" are natural terms users would say, but common synonyms and extensions (e.g. "bun:test", "porting tests", "snapshot") are missing.

4 / 5

Distinctiveness Conflict Risk

"migrating from Jest to Bun's test runner" defines a clear niche with distinct triggers and minimal overlap risk with any other skill.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

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

Revision

8837836

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill