Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/audit
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md.
Passed 7 of 15 test cases with the skill, and 6 of 15 without it.
and 2 more in the full report
5 fixed7 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
In the Security category findings, there are 2 P1 vulnerabilities and 0 P0 critical flaws. Should this category be marked as 'Fail' on the summary dashboard?
| Checked | Without skill | With skill |
|---|---|---|
| Assigns a health rating of Warn for categories containing P1 findings without P0 findings. | Missed | Passed |
The instructions your model reads when the skill loads.
Project-wide health audit. Fans out to all analysis skills, evaluates findings, and writes .turbo/audit.md and .turbo/audit.html. Analysis-only — does not apply fixes.
At the start, use update_plan to track each phase, restating any remaining steps of a parent workflow alongside them:
$evaluate-findings skillIf $ARGUMENTS specifies paths, use those directly (skip the question).
Otherwise, use request_user_input to confirm scope:
Once scope is determined:
node_modules/, dist/, build/, vendor/, __pycache__/, .build/, DerivedData/, target/, .tox/, and others appropriate to the project).request_user_input to narrow scope. If a single directory contains 50+ files, sub-partition it by its immediate subdirectories.Check whether .turbo/threat-model.md exists. When it exists, collect each surface's cited paths from Entry points and sinks and Hot files, ignoring any :line suffix. Treat the model as superseded when a surface has no cited path that still resolves. When it exists and is not superseded, continue to Step 3.
If missing or superseded, use request_user_input to ask whether to create one before proceeding. The security review benefits from threat model context, but creating one adds time.
$create-threat-model skill by reading and following the installed skill instructions. Wait for completion before continuing.test cases passed, vs 6 / 15 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.