Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →nvidia/holohub-app-lifecycle
Use for non-failing HoloHub app work with ./holohub: scaffold, build, run, test, visual evidence, lint, and flow benchmarking.
Passed 15 of 20 test cases with the skill, and 3 of 20 without it.
and 15 more in the full report
13 fixed3 passed either way6 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.
We want to speed up local iterative testing on our C++ HoloHub application after verifying that the initial container build and run cycle succeeded. Which flag should be passed to `./holohub` to skip rebuilding the container image?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies using the --no-docker-build flag to bypass image rebuilding. | Missed | Passed |
| The response conditions using the flag on having already executed at least one successful matching build and run cycle. | Missed | Passed |
The instructions your model reads when the skill loads.
Take a non-failing application request from checkout selection to reviewable,
finite evidence through the public ./holohub workflow.
Require the task, checkout or starting workspace, and finite acceptance check. Take remaining values from the request or selected checkout; do not guess data rights or sensitive-data constraints. Benchmark details are optional unless performance work is requested.
Route a concrete failing or wrong ./holohub command to
holohub-debug-build-run, reusable Module or DEB/WHEEL work to
holohub-module-lifecycle, and first-time SDK host installation to
holoscan-setup. If the matching skill is unavailable, preserve the handoff
context and name the skill to install instead of improvising its workflow.
The selected checkout's AGENTS.md, local ./holohub help, schemas, and
contribution guide are the live technical authority where they do not conflict
with user, system, or safety constraints.
test cases passed, vs 3 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.