CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-package-manager

Bun package manager commands (install, add, remove, update), workspaces, lockfiles, npm/yarn/pnpm migration. Use for dependency management with Bun.

67

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An actionable, well-structured command reference with strong executable examples. Weaknesses are missing validation around the destructive lockfile-upgrade step and references to non-existent bundle files.

Suggestions

Add a validation checkpoint before 'rm bun.lockb' in the lockfile-upgrade sequence (e.g. verify bun.lock was generated and --frozen-lockfile passed).

Create the missing references/workspaces.md and references/migration.md files, or remove those load triggers so every cited reference resolves.

Move the bulky inlined reference tables (Overrides/Resolutions, Non-npm Dependencies, full flag lists) into references/cli-commands.md and link out from SKILL.md to keep the overview lean.

DimensionReasoningScore

Conciseness

Mostly lean — tables and copy-paste code blocks with little explanatory prose — but carries minor padding (the '25x faster' marketing claim) and version-number-laden default-flip prose that could be trimmed, fitting the efficient-but-not-perfect anchor.

4 / 5

Actionability

Fully executable bash, JSON, TOML, and YAML examples cover the common cases copy-paste ready, with a clear Core Commands table and per-topic snippets, matching the score-5 anchor.

5 / 5

Workflow Clarity

This is a command reference rather than a sequenced workflow; the destructive lockfile-upgrade sequence ('rm bun.lockb') and batch migration lack validation checkpoints, capping the score at 3 per the destructive/batch guidance.

3 / 5

Progressive Disclosure

Sections are well organized and the 'When to Load References' block signals references clearly, but 2 of 3 cited reference files (workspaces.md, migration.md) do not exist and substantial reference-grade content is inlined rather than split out, matching the score-3 anchor.

3 / 5

Total

15

/

20

Passed

Description

91%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 strong, specific description that names concrete commands and ecosystem terms in third person. The only weakness is the 'Use for' clause being broad rather than tied to specific user trigger phrases.

Suggestions

Tighten the 'Use for' clause with concrete triggers, e.g. 'Use when the user asks to install, add, remove, or update dependencies with Bun, manage monorepo workspaces, fix lockfile issues, or migrate from npm/yarn/pnpm.'

DimensionReasoningScore

Specificity

Lists multiple concrete actions (install, add, remove, update), workspaces, lockfiles, and npm/yarn/pnpm migration — comprehensive coverage of the Bun package manager surface, matching the score-5 anchor.

5 / 5

Completeness

Both 'what' (the command set) and 'when' ('Use for dependency management with Bun') are present, but the trigger clause is broad rather than tied to concrete user phrases, fitting the score-4 anchor where 'when' could be more explicit.

4 / 5

Trigger Term Quality

Includes natural user-facing terms — package manager, install/add/remove/update, workspaces, lockfiles, migration, dependency management — plus synonyms across npm/yarn/pnpm, matching the comprehensive coverage anchor.

5 / 5

Distinctiveness Conflict Risk

The Bun-specific niche with command and ecosystem triggers is clearly distinct from generic package-manager skills, with minimal conflict risk.

5 / 5

Total

19

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository
secondsky/claude-skills
Reviewed

Table of Contents

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.