Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →platformplatform/build
Build (compile) the solution via the developer CLI - backend (.NET), frontend (React/TypeScript), and the developer CLI itself.
Passed 16 of 19 test cases with the skill, and 5 of 19 without it.
and 9 more in the full report
12 fixed6 passed either way4 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
Which flag target switch selects the developer CLI tooling binary for compilation?
| Checked | Without skill | With skill |
|---|---|---|
| Specifies the `--cli` flag | Missed | Passed |
The instructions your model reads when the skill loads.
dotnet run --project developer-cli -- build [--backend] [--frontend] [--cli] [--self-contained-system <name>] --quiet
Use developer-cli exactly as written - do not expand to an absolute worktree path.
--backend - .NET--frontend - React/TypeScript--cli - the developer CLI itself--self-contained-system <name> - narrows the backend build to one SCS (e.g. account, main)No arguments builds everything.
dotnet run --project developer-cli -- build --quiet # everything
dotnet run --project developer-cli -- build --backend --quiet # all backend
dotnet run --project developer-cli -- build --frontend --quiet # frontend
dotnet run --project developer-cli -- build --backend --self-contained-system main --quiet # one SCS
Verbose output goes to a log file. On success the CLI prints a single line; on failure it prints a short error summary - read the log if you need the full errors. Without --quiet the build floods the conversation.
test cases passed, vs 5 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.