use-devbox

Run commands inside a devbox environment when a directory provides one. If a `devbox.json` exists in the current directory (or an ancestor/subdir root), devbox can supply tools and scripts the bare shell lacks — e.g. psql, python, gcloud, node. If a binary is provided by devbox, prefer it over the system binary.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Critical

Do not install without reviewing

Quality

Content

86%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 with copy-paste commands and clearly sequenced workflows including a confirmation gate on package installation. The only weakness is mild redundancy in the closing 'Key facts' recap; progressive disclosure and structure are clean for a single-file skill.

Suggestions

Trim or remove the 'Key facts' section since it restates points already covered in 'Check it's installed', 'How to detect', and 'How to run'.

Consider folding the confirmation guidance for 'devbox add' into the 'Choosing where a binary comes from' steps as an explicit checkpoint to tighten the workflow.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and devbox-specific (Nix registry, packages available inside the environment not the bare shell), but the 'Key facts' section largely restates points already made in the body, adding minor redundancy that could be trimmed.	4 / 5
Actionability	Fully executable, copy-paste-ready commands throughout (command -v devbox, the install curl, ls/find detection, devbox run psql "$MASTER_DB_URL" -c '…', devbox search/add, devbox services ls) covering the common cases.	5 / 5
Workflow Clarity	Clear sequenced procedures (check→install→PATH, detect, run, and an ordered 1/2/3 binary-source decision) with a confirmation checkpoint on the project-modifying 'devbox add', though there is no explicit validate→fix→retry loop.	4 / 5
Progressive Disclosure	A single self-contained file with well-organized section headers, no nested references, and no bulk reference material that needs splitting into deeper files; navigation is easy.	5 / 5
	Total	18 / 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.

The description is concrete and complete, clearly stating both what the skill does and the precise condition under which to use it (a devbox.json present). It is highly distinct with low conflict risk; the only minor gap is limited synonym coverage for trigger terms.

Dimension	Reasoning	Score
Specificity	Names the devbox domain and several concrete actions ('Run commands inside a devbox environment', 'supply tools and scripts… e.g. psql, python, gcloud, node', 'prefer it over the system binary') with named tool examples, leaving only minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Run commands… supply tools and scripts… prefer it over the system binary') and when with a concrete trigger phrase ('when a directory provides one. If a devbox.json exists in the current directory (or an ancestor/subdir root)').	5 / 5
Trigger Term Quality	Good coverage of natural triggers a user would say ('devbox', 'devbox.json') plus concrete tool names, though synonym variation is limited by the niche nature of the tool.	4 / 5
Distinctiveness Conflict Risk	devbox is a sharply niche tool gated on a devbox.json trigger, giving it a clear distinct trigger with minimal overlap risk against other skills.	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: jetify-com/devbox
Path: .agents/skills/use-devbox/SKILL.md
Commit: 277290e

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