AF warp-eval
Evaluate whether an existing hot path is a credible NVIDIA Warp candidate. Use for irregular or spatial queries, particle or geometry simulation, branch-heavy loops, many small launches, host fallbacks, or large intermediates. CPU-only code and absent GPU dependencies are normal unless NVIDIA is prohibited. Exclude required cross-vendor or CPU-only deployment, vendor-lowered dense or NN layers, general Warp API questions, and already-selected Warp kernels. Contribution policy alone is not exclusion.
Evaluate whether an existing hot path is a credible NVIDIA Warp candidate.
As a process F 70/100 · Will not run — References files that are not bundled: references/evidence-and-reporting.md, references/authorization-checkpoint.md, references/target-patterns.md
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 · 0
✓ No critical or high findings
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: references/evidence-and-reporting.md - warning
missing-refreference to a missing file: references/authorization-checkpoint.md - warning
missing-refreference to a missing file: references/target-patterns.md - warning
missing-refreference to a missing file: references/rejection-gates.md - warning
missing-refreference to a missing file: references/benchmark-protocol.md - warning
missing-refreference to a missing file: references/semantic-contract.md - warning
missing-refreference to a missing file: references/baselines.md - warning
missing-refreference to a missing file: scripts/driver-template.py - warning
missing-refreference to a missing file: scripts/measure.py - warning
missing-refreference to a missing file: assets/warp-evaluation-report-template.md - warning
missing-refreference to a missing file: scripts/validate_report_schema.py
Process rating: all ten parameters 70/100
- 0Tools and files. 11 referenced file(s) missing: references/evidence-and-reporting.md, references/authorization-checkpoint.md, references/target-patterns.md
- 0Progress reporting. Says nothing while it works
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4678 tokens
- 100Steps. 68 steps
- 100Result and completion. Output format and completion criterion are stated
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (6 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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +3Description length 504: enough signal without eating the budget
- +4Structure: 20 headings
- +3Step-by-step instructions: 68 items
- +3Output format is stated explicitly
- +4Has examples (1 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.