BF rag-perf
Performance benchmarking for a deployed NVIDIA RAG Blueprint server: profiling pass + aiperf load test driven by a single YAML config. Not for accuracy / RAGAS scoring (use rag-eval) or for deploying / repairing services (use rag-blueprint).
Performance benchmarking for a deployed NVIDIA RAG Blueprint server: profiling pass + aiperf load test driven by a single YAML config.
As a process F 52/100 · Will not run — References files that are not bundled: ../../scripts/rag-perf/configs, references/output-and-analysis.md, references/output-and-analysis.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 1
✓ No critical or high findings
Medium and low: 1
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(curlallowed-tools: Read Grep Glob Bash(ls *) Bash(python3 *) Bash(uv *) Bash(cat *) Bash(curl *) Write Edit
Files scanned: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../scripts/rag-perf/configs - warning
missing-refreference to a missing file: references/output-and-analysis.md - warning
missing-refreference to a missing file: references/output-and-analysis.md - warning
missing-refreference to a missing file: ../../docs/performance-benchmarking.md - warning
missing-refreference to a missing file: ../../scripts/rag-perf/rag_perf/cli.py - warning
missing-refreference to a missing file: ../../scripts/rag-perf/rag_perf/config.py - warning
missing-refreference to a missing file: ../../scripts/rag-perf/rag_perf/runner.py - warning
missing-refreference to a missing file: ../../scripts/rag-perf/rag_perf/plugin/nvidia_rag.py - warning
missing-refreference to a missing file: ../../scripts/rag-perf/configs/ - warning
missing-refreference to a missing file: ../../scripts/rag-perf/examples/queries.jsonl - warning
missing-refreference to a missing file: ../../scripts/rag-perf/prompts/default_prompts.yaml - warning
missing-refreference to a missing file: references/config-schema.md - warning
missing-refreference to a missing file: references/synthetic-generation.md - warning
missing-refreference to a missing file: scripts/rag-perf/configs/ - warning
missing-refreference to a missing file: scripts/rag-perf/rag_perf/runner.py - warning
missing-refreference to a missing file: scripts/rag-perf/examples/queries.jsonl - warning
missing-refreference to a missing file: scripts/rag-perf/prompts/default_prompts.yaml - warning
missing-refreference to a missing file: scripts/rag-perf/ - warning
missing-refreference to a missing file: scripts/rag-perf/rag_perf/plugin/nvidia_rag.py - warning
missing-refreference to a missing file: scripts/rag-perf/rag_perf/cli.py - warning
missing-refreference to a missing file: scripts/rag-perf/rag_perf/config.py - warning
missing-refreference to a missing file: scripts/rag-perf/configs/{quick_profile,single_run,sweep}.yaml - warning
missing-refreference to a missing file: scripts/rag-perf/configs/<preset>.yaml
Process rating: all ten parameters 52/100
- 0Tools and files. 23 referenced file(s) missing: ../../scripts/rag-perf/configs, references/output-and-analysis.md, references/output-and-analysis.md
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 50When it triggers. No condition that starts the skill
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 47 steps, 1 vague phrases
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3665 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (7 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Output format is not stated: the model decides each time
- -2localhost URLs: will not work for another user
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 241: enough signal without eating the budget
- +4Structure: 11 headings
- +3Step-by-step instructions: 47 items
- +4Has examples (5 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.