rust-system-calls

Guides using bun_sys for system calls and file I/O in Rust. Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc.

Quality

85%

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

Quality

Content

83%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 tight, highly actionable reference with concrete executable code and useful guardrails, assuming Claude's competence throughout. The main weakness is the absence of an explicit validation/retry loop for destructive file operations, which caps workflow clarity.

Suggestions

Add a short validate-fix-retry pattern for destructive calls (e.g., after write/unlink, check the returned Error errno and retry/branch explicitly) to lift workflow clarity above the destructive-ops cap of 3.

Verify src/CLAUDE.md exists in the bundle or rephrase the closing pointer to a path that is present, so the one-level reference resolves.

Consider a brief ordered checklist for the common end-to-end task (open -> read/write -> handle Maybe<Error> -> Drop) to give the guide a clearer procedural spine.

Dimension	Reasoning	Score
Conciseness	Lean and code-heavy with no padding or basic-concept explanations; every section (comparison table, error handling, key types, path buffers, common mistakes) earns its place and assumes Claude's Rust competence.	5 / 5
Actionability	Provides copy-paste-ready, executable Rust examples covering the common cases (open/read/write, Maybe<T> propagation, errno branching, path buffers), plus a concrete API/function inventory.	5 / 5
Workflow Clarity	This is a reference/patterns guide rather than a sequenced workflow, and the destructive operations it demonstrates (write_file, unlink) lack an explicit validate-fix-retry feedback loop, which caps the score per the rubric's destructive-ops guidance.	3 / 5
Progressive Disclosure	Well-organized into clear section headers with one signaled one-level reference ("See src/CLAUDE.md for the full ... reference"); no bundle files exist, and that external reference target is not verifiable within the skill bundle, a minor organization gap.	4 / 5
	Total	17 / 20 Passed

Description

87%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 concise, third-person description that clearly states both capability and trigger conditions with concrete, contrastive keywords. It is well above the midpoint on every dimension, with only minor synonym/coverage room for improvement.

Dimension	Reasoning	Score
Specificity	Names the library and several concrete actions across the what/when clauses ("system calls and file I/O", "file operations, opening fds, ... syscall path"), with only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ("Guides using bun_sys for system calls and file I/O in Rust") and when ("Use when implementing file operations, opening fds, or any syscall path instead of std::fs or libc") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage for the niche ("file operations", "opening fds", "syscall path", "std::fs", "libc"); a few synonyms a user might say are absent but the domain has little synonym surface.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (bun_sys) with distinct, contrastive triggers ("instead of std::fs or libc"), making conflict with other skills unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: oven-sh/bun
Path: .claude/skills/rust-system-calls/SKILL.md
Commit: abe2ad4

Reviewed: 1 day 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.