bun

Use Bun instead of Node.js, npm, pnpm, or vite. Provides command mappings, Bun-specific APIs, and development patterns.

2.02x

Quality

86%

Does it follow best practices?

Impact

99%

2.02x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Quality

Content

100%

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

This is an excellent skill file that efficiently maps Node.js/npm patterns to Bun equivalents. It's highly actionable with executable code examples, well-organized with tables for quick reference, and appropriately concise without explaining concepts Claude already knows. The progressive structure from basic commands to frontend development is logical and easy to follow.

Dimension	Reasoning	Score
Conciseness	Extremely lean and efficient. Uses tables for command mappings, no unnecessary explanations of what Bun is or why to use it. Every line provides actionable information Claude wouldn't inherently know.	3 / 3
Actionability	Provides concrete, executable code examples for testing and server setup. Command mappings are copy-paste ready, and the HTML imports example is complete and runnable.	3 / 3
Workflow Clarity	For a simple reference skill, the workflow is clear: use these commands instead of those, use these APIs instead of those. The frontend development section shows a complete setup flow with server and HTML file.	3 / 3
Progressive Disclosure	Well-organized with clear sections (Command Mappings, APIs, Testing, Frontend). Appropriately references external docs at the end without deep nesting. Content is right-sized for a SKILL.md.	3 / 3
	Total	12 / 12 Passed

Description

72%

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 effectively identifies its niche and includes strong trigger terms that users would naturally mention. However, it lacks an explicit 'Use when...' clause and could be more specific about the concrete actions it enables (e.g., 'run scripts', 'install dependencies', 'bundle applications').

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user wants to use Bun instead of Node.js, or mentions bun commands, package installation with Bun, or Bun-specific features.'

Replace abstract terms like 'development patterns' with concrete actions such as 'run scripts, install packages, bundle code, execute TypeScript directly'.

Dimension	Reasoning	Score
Specificity	Names the domain (Bun runtime) and mentions some capabilities ('command mappings, Bun-specific APIs, and development patterns'), but these are somewhat abstract rather than listing concrete actions like 'run scripts', 'install packages', or 'bundle code'.	2 / 3
Completeness	The 'what' is partially addressed (command mappings, APIs, patterns), but there is no explicit 'Use when...' clause or equivalent trigger guidance explaining when Claude should select this skill.	2 / 3
Trigger Term Quality	Excellent coverage of natural terms users would say: 'Bun', 'Node.js', 'npm', 'pnpm', 'vite' - these are exactly the keywords a user would mention when needing this skill.	3 / 3
Distinctiveness Conflict Risk	Very clear niche - specifically about using Bun as an alternative to other JS runtimes/package managers. The explicit mention of Node.js, npm, pnpm, and vite as alternatives creates distinct boundaries.	3 / 3
	Total	10 / 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: brianlovin/claude-config
Commit: 1a9819e

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