AF cargo-diagnostics
Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, draw the graph it executed with the failing step marked, sweep a batch or play for errors grouped by root cause, and attribute credit spend down to the node and the provider. Triggers: "why did this fail", "it succeeded but the output is wrong", "half my rows are empty", "why is this column blank", "what broke in this batch", "why did that cost so much", "which node is burning credits", "it worked yesterday", "these results look wrong", "it went down the wrong path", "this step never ran", "show me what the run did". Skip when: setting up an alert for next time — use cargo-observability; just downloading the data — use cargo-analytics.
Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, draw the graph it executed with the failing step marked, sweep a…
As a process F 30/100 · Will not run — References files that are not bundled: ../cargo/references/prerequisites.md, ../cargo-orchestration/references/node-diagram.md, ../cargo-orchestration/references/examples/queries.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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../cargo/references/prerequisites.md - warning
missing-refreference to a missing file: ../cargo-orchestration/references/node-diagram.md - warning
missing-refreference to a missing file: ../cargo-orchestration/references/examples/queries.md - warning
missing-refreference to a missing file: ../cargo-orchestration/references/troubleshooting.md - warning
missing-refreference to a missing file: ../cargo/references/interaction.md - warning
missing-refreference to a missing file: ../cargo-gtm/references/cost-discipline.md - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 30/100
- 0Tools and files. 6 referenced file(s) missing: ../cargo/references/prerequisites.md, ../cargo-orchestration/references/node-diagram.md, ../cargo-orchestration/references/examples/queries.md
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1735 tokens
- 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
- +4Description does not say when NOT to use the skill (false activations)
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +5Description quotes 12 example trigger phrases
- +3Description length 736: enough signal without eating the budget
- +4Structure: 7 headings
- +4Has examples (3 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.