CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

bun-file-io

Use for Bun file I/O: Bun.file, Bun.write, streams, directories, glob patterns, metadata.

60

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/bun/skills/bun-file-io/SKILL.md
SKILL.md
Quality
Evals
Security

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.

The body is highly actionable, lean code-first reference material with good sectioning. Its weaknesses are missing validation checkpoints around destructive/batch operations and broken/non-existent reference files that undermine progressive disclosure.

Suggestions

Create the referenced references/streams-advanced.md and references/performance.md (or remove the dangling references) so the 'When to Load References' navigation resolves.

Add validation/verification steps around destructive and batch operations, e.g. check existence before rmdir and verify copyDir results, to lift workflow clarity above the destructive-operation cap.

De-duplicate overlapping examples (file.writer() and Bun.write copy appear in multiple sections) to tighten conciseness toward the lean anchor.

DimensionReasoningScore

Conciseness

The body is mostly lean, executable code with brief inline comments and no concept padding, but a few sections repeat material (file.writer() in Appending and Write Stream; Bun.write copy reappearing in Pipe Streams), which is minor over-explanation that could be trimmed.

4 / 5

Actionability

Nearly every section is copy-paste-ready, executable TypeScript covering the common cases (read/write/JSON/binary, streaming, glob, metadata, path ops, copyDir), matching the fully-executable anchor.

5 / 5

Workflow Clarity

Content is organized as a topic reference rather than a sequenced workflow, and destructive/batch operations (rmdir with recursive, copyDir) lack validation checkpoints; per the rubric, missing validation for destructive/batch operations caps this dimension at 3.

3 / 5

Progressive Disclosure

Section structure is clean and a 'When to Load References' block clearly signals references with trigger criteria, but the referenced files (references/streams-advanced.md, references/performance.md) do not exist in the bundle and the ~326-line body inlines substantial API reference that belongs in those separate files, so organization is only partial.

3 / 5

Total

15

/

20

Passed

Description

67%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.

The description is a concise, Bun-scoped trigger statement that covers both what and when with specific API names. Its main weakness is generic trigger phrasing and missing natural synonyms, which keeps it at the 3-4 band rather than fully comprehensive.

Suggestions

Reword the trigger to surface natural user phrases, e.g. "Use when reading or writing files with Bun, working with streams, directories, glob patterns, or file metadata."

Add concrete verb-form actions (read, write, copy, stream, scan) alongside the API names to lift specificity toward comprehensive coverage.

Include common synonyms/extensions users say (e.g. "read/write files", ".json", ".txt") to improve trigger-term quality.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("Bun.file, Bun.write, streams, directories, glob patterns, metadata") naming the domain and multiple specific APIs, but they are API/feature names rather than verb-form actions, leaving minor coverage gaps relative to the comprehensive anchor 5.

4 / 5

Completeness

"Use for Bun file I/O: ..." provides an explicit trigger clause (when) alongside the enumerated feature list (what), but the 'when' is generic rather than tied to concrete user-mention trigger phrases, matching the 'both present, when could be more specific' anchor.

4 / 5

Trigger Term Quality

"Bun file I/O" is a natural trigger and "streams, directories, glob patterns, metadata" add relevant domain terms, but common natural synonyms users say ("read files", "write files", "save files", file extensions) are missing, so coverage is partial rather than comprehensive.

3 / 5

Distinctiveness Conflict Risk

Bun-specific API names (Bun.file, Bun.write) carve a clear niche, but the broad "file I/O" framing leaves minor overlap risk with a general Node/Bun file skill, so it is mostly distinct rather than fully minimal-conflict.

4 / 5

Total

15

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

secondsky/claude-skills

Path

plugins/bun/skills/bun-file-io/SKILL.md

Revision

8837836

Reviewed

Table of Contents

DiscoveryImplementationValidation

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.

Claim skill