Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →skilld-dev/skilld
Operate skilld CLI for Skill discovery, use, installation, inspection, updates, authentication, configuration, restoration, and removal, including Repository, curator, and collection refs.
Passed 18 of 21 test cases with the skill, and 3 of 21 without it.
and 20 more in the full report
16 fixed2 passed either way2 still failing1 broke3 errored
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
A newer attempt on gemini-3.8-flash on 10/21/2026 did not produce a publishable comparison (not comparable). The snapshot above is the previously measured run.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am inspecting the `data.files` list returned by `skilld run acme/tools/compiler --json`. A binary helper file `bin/helper` has `readable: false` and `kind: executable`. Can I read its content using `skilld run --file bin/helper`?
| Checked | Without skill | With skill |
|---|---|---|
| Explains that files with readable false cannot be printed via --file. | Missed | Passed |
| Informs the user that the skill requires installation to use the binary file. | Missed | Passed |
The instructions your model reads when the skill loads.
Use skilld CLI to find, load, install, inspect, restore, update, verify, and remove Skills.
Run a Skill first. Install a Skill only when the user asks to keep it. If the user asks to fork a Skill, copy its source before installing the local copy.
Use --json with search, run, and update --check.
Use --json with view of a registry ref, and with every registry and account command below.
Their data is the skilld.dev answer. A command whose answer has no body returns data: null.
Use --json with sync and sync --check for declared Skills.
Use doctor --json for read-only Skill discovery and cleanup findings.
The remaining commands do not support JSON output.
Use --plain when another command needs stable text.
Check the exit code before reading stdout.
Read JSON success data only when _tag is Success.
Read JSON failures from stderr.
Report the error code and message.
A failed skilld run ends with a Next step: line. In JSON, read error.nextStep.
Follow that step. It says whether to retry, when, and what to tell the user.
Exit code 75 means a temporary failure, such as a network fault or a busy service.
Exit code 1 means the same command gives the same result.
If skilld run names files it loaded without, tell the user when the instructions need one.
An update check can exit with code 1 and return valid JSON. Read its update relations before treating that exit as a failure. Never parse formatted terminal output.
Read Declared Skills when a project needs explicit Skill requirements.
Use .skills/skilld.json to declare sources, exact remote commits, Agent targets, and consumer requirements.
Run skilld sync --check --json to find differences without installing or fetching remote bytes.
Exit code 1 with success data means sync is needed.
Run skilld sync to install the full declaration in one transaction.
Use --global for global Agent targets.
Use --adopt only when migrating identical unmanaged symlinks.
test cases passed, vs 3 / 21 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.