bun-shell

Bun shell scripting with Bun.$, Bun.spawn, subprocess management. Use for shell commands, template literals, or command execution.

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-shell/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

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

The content is a well-organized, highly actionable catalog of executable Bun shell patterns with no explanatory padding. Its main weaknesses are missing validation feedback loops in the script workflows and dangling reference pointers to files that do not exist, alongside a large inline reference that should be split out.

Suggestions

Create the referenced `references/advanced-scripting.md` and `references/cross-platform.md` files (or remove the dangling 'When to Load References' section) so progressive disclosure points at real material.

Move the bulk of the Bun.$/Bun.spawn API catalog into a reference file and keep SKILL.md as a concise overview with one or two quick-start examples.

Add explicit validation checkpoints to the deploy script workflow (e.g. 'only proceed when `bun test` passes') to close the feedback-loop gap for batch/destructive operations.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code with one-line comments and no concept-explanation fluff, but it repeats `import { $ } from "bun"` across many sections and presents a large volume of examples that could be tightened or offloaded, matching the level-2 'could be tightened' anchor rather than the lean level-3.	2 / 3
Actionability	Examples are fully executable, copy-paste ready, and cover specific real patterns (piping, stdio, streaming, kill/timeout, parallel commands), matching the level-3 anchor.	3 / 3
Workflow Clarity	The deploy example lists sequenced steps with a pre-check, but most operations lack explicit validation checkpoints or error-recovery feedback loops (e.g. no 'only proceed when tests pass' gate), so it sits at the level-2 anchor with validation gaps.	2 / 3
Progressive Disclosure	A 'When to Load References' section signals references, but the cited files (`references/advanced-scripting.md`, `references/cross-platform.md`) do not exist in any bundle directory, and ~380 lines of API reference that belong in separate files are inline, matching the level-2 anchor.	2 / 3
	Total	9 / 12 Passed

Description

75%Weight 40%Scale 1-3

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 cleanly states what the skill does and when to use it with an explicit trigger clause and a distinctive Bun-specific niche. It is slightly weaker on action specificity and natural-term coverage, listing APIs and a few technical terms rather than a comprehensive set of user-facing verbs.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bun shell scripting') and concrete APIs ('Bun.$, Bun.spawn, subprocess management'), but lists API surface rather than comprehensive concrete actions, so it stops short of the level-3 anchor.	2 / 3
Completeness	Explicitly answers both what ('Bun shell scripting with Bun.$, Bun.spawn, subprocess management') and when via the 'Use for shell commands, template literals, or command execution' trigger clause, matching the level-3 anchor.	3 / 3
Trigger Term Quality	Includes relevant natural terms ('shell commands', 'command execution', 'template literals'), but misses common variations users would say like 'run commands', 'bash', or 'execute commands', placing it at the level-2 anchor.	2 / 3
Distinctiveness Conflict Risk	The Bun-specific API names ('Bun.$', 'Bun.spawn') carve out a clear niche unlikely to trigger for non-Bun shell skills, matching the level-3 anchor.	3 / 3
	Total	10 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 2 missing	Warning

	Total	15 / 16 Passed

Repository: secondsky/claude-skills
Path: plugins/bun/skills/bun-shell/SKILL.md
Commit: 4867baa

Reviewed: 6 days 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.