bun-runtime
Use for Bun runtime, bunfig.toml, watch/hot modes, env vars, CLI flags, and module resolution.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/bun/skills/bun-runtime/SKILL.mdQuality
Discovery
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 (Bun runtime) with good trigger terms that developers would naturally use. However, it lacks concrete action verbs describing what the skill actually does (e.g., configure, troubleshoot, optimize) and the 'when' guidance is more of a topic list than explicit trigger scenarios. It reads more like a tag cloud than a functional description.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Configures Bun runtime settings, troubleshoots module resolution, sets up watch/hot reload modes'.
Expand the 'Use for' clause into a more explicit 'Use when...' with trigger scenarios, e.g., 'Use when the user asks about Bun configuration, bunfig.toml setup, environment variable handling, or Bun-specific CLI flags'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Bun runtime) and lists several specific areas (bunfig.toml, watch/hot modes, env vars, CLI flags, module resolution), but these are more like topic areas than concrete actions. It doesn't describe what actions are performed (e.g., 'configure', 'debug', 'set up'). | 2 / 3 |
Completeness | Has a 'Use for...' clause which partially addresses 'when', but the 'what does this do' part is weak — it lists topics but not concrete actions. The 'when' is implied through the 'Use for' prefix but doesn't clearly articulate trigger scenarios beyond topic matching. | 2 / 3 |
Trigger Term Quality | Includes strong natural keywords users would actually say: 'Bun', 'bunfig.toml', 'watch mode', 'hot mode', 'env vars', 'CLI flags', 'module resolution'. These cover common terms a developer working with Bun would use. | 3 / 3 |
Distinctiveness Conflict Risk | Bun runtime is a clearly distinct niche. The specific mentions of bunfig.toml, watch/hot modes, and Bun-specific CLI flags make it very unlikely to conflict with Node.js, Deno, or other runtime skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with strong actionability and good progressive disclosure. The main weaknesses are some unnecessary content (globals table, introductory description) that Claude already knows, and a lack of validation/feedback loops in multi-step scenarios. The reference loading guidance at the end is a standout feature.
Suggestions
Remove or significantly trim the Globals table — Claude already knows about standard web/Node.js globals; only Bun-specific globals (like `Bun`) need mention.
Remove the introductory sentence explaining what Bun is and its performance characteristics — this is background knowledge, not actionable guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient with good use of tables and code blocks, but includes some unnecessary content like the Globals table (Claude already knows about standard web/Node globals) and explanations of what Bun is. The 'Bun is a fast all-in-one JavaScript runtime built on JavaScriptCore' intro adds little actionable value. | 2 / 3 |
Actionability | Provides fully executable, copy-paste ready commands throughout. CLI flags are concrete, code examples are real and runnable, and the flag ordering gotcha ('Put Bun flags immediately after bun') is a specific, actionable detail that prevents real errors. | 3 / 3 |
Workflow Clarity | Individual commands and modes are clearly explained, but there are no validation checkpoints or feedback loops. The debugging section lists commands without a workflow for diagnosing issues. The common errors table is helpful but reactive rather than integrated into workflows. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear overview and well-signaled references to deeper content (bunfig.md, cli-flags.md, module-resolution.md) with specific trigger conditions for when to load each. Content is appropriately split between the main skill and reference files. | 3 / 3 |
Total | 10 / 12 Passed |
Validation
100%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
- secondsky/claude-skills
- Commit
88da5ff
- 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.