setup-osn

Use when setting up or repairing a development environment for this repository on a machine — Bun at the pinned version, the GitHub CLI and its auth, SSH commit signing and the recommended git config, workspace dependencies, lefthook hooks and the portless dev proxy — and verifying it with the type-check, lint and format gates. Also the place to start when bun, gh, turbo or a hook is missing or the wrong version.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

88%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 well-structured, actionable setup runbook with executable commands, explicit validation gates, and thoughtful fallbacks for non-macOS/no-sudo/no-network/non-interactive contexts. The only soft spot is minor conciseness trim and slightly uneven reference signaling, neither of which undermines usability.

Suggestions

Tighten the git-config "Why" column to a short phrase per row to reduce tokens without losing the rationale.

Standardize the inline repo-file references (e.g., always link or always backtick-quote paths like `lefthook.yml` and `CLAUDE.md`) so navigation cues are uniform.

Consider promoting the three gates and the final report-table contract into a short checklist near the top so the validation requirements are scannable before the steps.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with most prose earning its place; the git-config "Why" column and a few rationale clauses add slight over-explanation that could be trimmed without losing clarity.	4 / 5
Actionability	Fully executable guidance throughout — `bun --version`, the `curl -fsSL https://bun.sh/install \| bash -s "bun-v$(cat .bun-version)"` pin, `gh auth status`/`gh auth refresh -s repo`, `git config --global ...`, `bash scripts/setup.sh`, and `bunx portless ...` are copy-paste ready and cover the common cases.	5 / 5
Workflow Clarity	A clear nine-step sequence with explicit validation gates (`bun run check`, `bun run lint`, `bun run fmt:check`), per-environment fallback handling, and feedback loops ("Never claim a gate passed that did not run here"; paste decisive lines and keep going on failure).	5 / 5
Progressive Disclosure	Well-organized into clearly headed sections with one-level-deep pointers to repo files (`.bun-version`, `lefthook.yml`, `scripts/setup.sh`, `CLAUDE.md`); no bundle files exist, and the self-contained body is appropriately not over-split, though a couple of inline references could be signaled more uniformly.	4 / 5
	Total	18 / 20 Passed

Description

92%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, concrete description with an explicit "Use when" trigger and a complementary "place to start when" clause. It names the specific tools and gates involved and is clearly distinguishable from other skills; only minor synonym coverage in trigger terms keeps it from a perfect mark there.

Dimension	Reasoning	Score
Specificity	Enumerates many concrete actions — "Bun at the pinned version, the GitHub CLI and its auth, SSH commit signing and the recommended git config, workspace dependencies, lefthook hooks and the portless dev proxy" plus "verifying it with the type-check, lint and format gates" — giving comprehensive concrete coverage rather than abstract language.	5 / 5
Completeness	Explicitly answers both what (the enumerated setup and verification tasks) and when ("Use when setting up or repairing a development environment" plus "Also the place to start when bun, gh, turbo or a hook is missing") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers like "setting up or repairing a development environment" and "when bun, gh, turbo or a hook is missing or the wrong version" match what a user would say, with strong tool-name keywords, but a few common synonyms/phrasings are absent.	4 / 5
Distinctiveness Conflict Risk	A distinct repo-specific dev-environment niche with named tools (Bun, gh, lefthook, portless) gives clear triggers and minimal overlap with unrelated skills.	5 / 5
	Total	19 / 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: 3 missing	Warning

	Total	15 / 16 Passed

Repository: xchromo/osn
Path: .claude/skills/setup-osn/SKILL.md
Commit: 5438649

Reviewed: 13 hours 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.