bun
Use Bun instead of Node.js, npm, pnpm, or vite. Provides command mappings, Bun-specific APIs, and development patterns.
Overall
score
82%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
54%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 has strong trigger term coverage by naming Bun and its alternatives (Node.js, npm, pnpm, vite), making it highly discoverable. However, it lacks explicit 'Use when...' guidance and the capabilities listed are somewhat abstract rather than concrete actions. Adding trigger conditions and more specific actions would significantly improve skill selection accuracy.
Suggestions
Add a 'Use when...' clause specifying triggers like 'when the user mentions Bun, wants to migrate from Node.js/npm, or asks about Bun-specific features'
Replace abstract terms like 'command mappings' and 'development patterns' with concrete actions such as 'run scripts with bun run, install packages with bun install, bundle code with bun build'
| 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 | Describes what it does but completely lacks a 'Use when...' clause or any explicit trigger guidance. Per rubric guidelines, missing explicit trigger guidance caps completeness at 2, and this description has no 'when' component at all. | 1 / 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 | 9 / 12 Passed |
Implementation
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 concise, actionable, and well-structured with tables for quick reference and complete code examples where needed. The content respects Claude's intelligence by focusing only on Bun-specific knowledge.
| 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 frontend development. Command mappings are specific and copy-paste ready. The server example is complete and runnable. | 3 / 3 |
Workflow Clarity | This is a reference/mapping skill rather than a multi-step workflow skill. The single-task patterns (run server, run tests) are unambiguous. No destructive operations requiring validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections (Command Mappings, APIs, Testing, Frontend). Appropriately references external docs for detailed API information. Content is appropriately scoped for a skill file. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
68%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 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
description_trigger_hint | Description may be missing an explicit 'when to use' trigger hint (e.g., 'Use when...') | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 11 / 16 Passed | |
- 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.