CtrlK
BlogDocsLog inGet started
Tessl Logo

bun-file-io

Use this when you are working on file operations like reading, writing, scanning, or deleting files. It summarizes the preferred file APIs and patterns used in this repo. It also notes when to use filesystem helpers for directories.

61

Quality

71%

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 ./.openscience/skill/bun-file-io/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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 content is a concise, well-organized, actionable reference of Bun file APIs and repo patterns. Its only real weakness is the absence of validation/verification checkpoints for destructive and batch operations, which caps workflow clarity.

Suggestions

Add an explicit validation step for destructive operations (e.g., confirm via `Bun.file(...).exists()` / size check before and after `delete()` or large `Bun.write`).

Include one complete copy-paste code snippet covering a common read/write/scan flow to lift actionability to 5.

Add a brief verify step to the Quick checklist for delete and large-write cases.

DimensionReasoningScore

Conciseness

The body is a lean bullet reference of Bun APIs and repo patterns with no conceptual padding, assuming Claude knows the underlying concepts; every token earns its place.

5 / 5

Actionability

Concrete API signatures and method chains (e.g., `Bun.write(dest, input)`, `Array.fromAsync(glob.scan({ cwd, absolute, onlyFiles, dot }))`) give mostly executable guidance, but there are no complete copy-paste runnable snippets, leaving minor gaps.

4 / 5

Workflow Clarity

The skill covers destructive operations ("`Bun.file(...).delete()` deletes a file") and batch scans but provides no explicit validation/verification checkpoint for them; the destructive-operations cap holds this at 3 despite the simple, well-structured layout.

3 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed and is cleanly organized into well-labeled sections (Use this when, Bun file APIs, When to use node:fs, Repo patterns, Quick checklist), satisfying the simple-skill exception.

5 / 5

Total

17

/

20

Passed

Description

62%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 clearly states what the skill does and when to use it, with concrete actions and a repo-specific niche. It loses points for second-person voice, somewhat generic trigger terms, and a broad domain with minor overlap risk.

Suggestions

Rewrite in third person to avoid the specificity penalty (e.g., "Summarizes preferred file APIs... Use when working on file operations...").

Add natural synonyms and concrete trigger phrases users would say (e.g., "read, write, scan, or delete files", "Bun file I/O", "directory operations").

Tie the "when" clause to more specific user-mentioned contexts to lift completeness and distinctiveness toward 5.

DimensionReasoningScore

Specificity

The description names several concrete actions ("reading, writing, scanning, or deleting files") and what it summarizes ("preferred file APIs and patterns", "filesystem helpers for directories"), but uses second person ("Use this when you are working"), which per the rubric penalizes specificity by one; otherwise a 4.

3 / 5

Completeness

It has both a clear "what" (summarizes preferred file APIs/patterns, notes filesystem helpers) and an explicit "Use this when..." trigger; the "when" could be tied to more concrete user-mentioned phrases, keeping it below 5.

4 / 5

Trigger Term Quality

"file operations like reading, writing, scanning, or deleting files" provides some relevant, fairly natural keywords but lacks synonyms and file extensions, so it falls short of good coverage.

3 / 5

Distinctiveness Conflict Risk

The repo-specific framing ("preferred file APIs and patterns used in this repo") makes it mostly distinct, though the broad "file operations" domain still carries minor overlap risk with general filesystem skills.

4 / 5

Total

14

/

20

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
synthetic-sciences/openscience
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.