Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →hashgraph-online/creating-julia-app
Use when you create a CLI written in Julia packages or MCP servers
Passed 22 of 22 test cases with the skill, and 9 of 22 without it.
and 14 more in the full report
13 fixed9 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 13 test cases the skill fixed. Same model, same prompt, with and without the skill.
I am building a command-line tool named `csv-tool` in Julia. Should I register the executable name under a `[bin]` table, `[executables]` table, or `[apps]` table in `Project.toml`?
| Checked | Without skill | With skill |
|---|---|---|
| Uses [apps] as the section header in Project.toml | Missed | Passed |
The instructions your model reads when the skill loads.
Apps are Julia packages that are intended to be run as "standalone programs" (by e.g. typing the name of the app in the terminal possibly together with some arguments or flags/options). This is in contrast to most Julia packages that are used as "libraries" and are loaded by other files or in the Julia REPL.
A Julia app is structured similar to a standard Julia library with the following additions:
A @main entry point in the package module (see the Julia help on @main for details)
An [apps] section in the Project.toml file listing the executable names that the package provides.
A very simple example of an app that prints the reversed input arguments would be:
# src/MyReverseApp.jl
module MyReverseApp
function (@main)(ARGS)
for arg in ARGS
print(stdout, reverse(arg), " ")
end
return
end
end # module
# Project.toml
# standard fields here
[apps]
reverse = {}
The empty table {} is to allow for giving metadata about the app.
After installing this app one could run:
$ ~/.julia/bin/reverse some input string
emos tupni gnirts
test cases passed, vs 9 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.