bun-shell

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

Quality

77%

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

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.

A highly actionable, code-first reference with clean sectioning, but it is weakened by a missing validation feedback loop in its deploy workflow and by reference pointers to files that are absent from the bundle.

Suggestions

Create the referenced files (references/advanced-scripting.md and references/cross-platform.md) or remove the 'When to Load References' section so signaled paths resolve to real files.

Add an explicit post-deploy verification step and a validate-fix-retry loop to the deploy script example to clear the destructive-operation workflow cap.

Move the large API catalog portions (e.g., full Bun.spawn/Bun.spawnSync options) into a reference file and keep SKILL.md as a tighter overview to improve progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-heavy with minimal prose and no over-explanation of basic concepts, though the repeated `import { $ } from "bun"` across every snippet is minor trimmable redundancy.	4 / 5
Actionability	Examples are fully executable, copy-paste-ready TypeScript covering the common cases (templating, piping, error handling, spawn, streaming, process management) with concrete commands and output methods.	5 / 5
Workflow Clarity	The deploy example has a pre-check for uncommitted changes but lacks post-deploy verification or a validate-fix-retry feedback loop; per the destructive-operation guideline this caps the score at 3.	3 / 5
Progressive Disclosure	Section organization is clear and the 'When to Load References' block signals load conditions well, but the referenced files (references/advanced-scripting.md, references/cross-platform.md) do not exist and the bulk API reference is inlined rather than split out.	3 / 5
	Total	15 / 20 Passed

Description

82%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 description that clearly answers both what the skill does and when to use it, with a distinct Bun-specific niche. The main gap is specificity, where API names stand in for a fuller enumeration of supported actions.

Suggestions

Expand the 'what' clause with a couple more concrete actions (e.g., piping commands, streaming output, managing subprocesses) to lift specificity toward comprehensive coverage.

Add one or two natural user phrasings such as 'run shell commands' or 'execute commands' alongside the existing trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain ('Bun shell scripting') and a few concrete constructs ('Bun.$', 'Bun.spawn', 'subprocess management'), but lists API names rather than a comprehensive set of actions like piping, streaming, or signal handling.	3 / 5
Completeness	Explicitly states both what it does ('Bun shell scripting with Bun.$, Bun.spawn, subprocess management') and when to use it ('Use for shell commands, template literals, or command execution') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger terms 'shell commands', 'template literals', and 'command execution' are present and would be said by users, though common synonyms like 'run a command' or 'execute shell' are missing.	4 / 5
Distinctiveness Conflict Risk	The Bun-specific niche and explicit API names make it clearly distinguishable from generic shell or scripting skills with minimal conflict risk.	5 / 5
	Total	17 / 20 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: ad16332

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