Install any skill in seconds. Free to start, no credit card required.
Get Started Free →julialang/doctests
Write and verify Julia `jldoctest` code blocks.
Passed 21 of 23 test cases with the skill, and 6 of 23 without it.
and 16 more in the full report
15 fixed6 passed either way2 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 15 test cases the skill fixed. Same model, same prompt, with and without the skill.
I just updated a few `jldoctest` examples in the Julia codebase. Could you provide the exact terminal command to run and verify these doctests using my local in-tree Julia build?
| Checked | Without skill | With skill |
|---|---|---|
| Prescribes running `make -C doc doctest=true revise=true` for in-tree doctest verification. | Missed | Passed |
| Advises against passing additional make flags or options beyond doctest=true and revise=true. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this whenever you add or modify any jldoctest code block.
Before writing new doctests, review doc/src/devdocs/contributing/jldoctests.md
for best practices (filters, labels, setup code).
If you changed any jldoctest block you MUST verify it. Follow these steps for
EVERY doctest change:
doc/src/devdocs/contributing/jldoctests.md. In particular, determine
if any of the changed doctests require filters, labels or setup code.make -C doc doctest=true revise=true JULIA_EXECUTABLE=$HOME/.juliaup/bin/juliamake -C doc doctest=true revise=true. Do not pass any other options.test cases passed, vs 6 / 23 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.