Real Skill packageSource verifiedClawHub registry

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 result…

Identity and source

Publisher attributionCargoregistry owner unverified by skillvetai
Functional categoryAwaiting category reviewreview pending · 0% rule confidence
Package forminstruction bundle6 recorded files
Canonical sourceClawHub registryclawhub:cargo-ai:cargo-diagnostics
Open canonical source ↗

Platform declarations

These states come from the source or distribution context. None of the entries below are SkillVetAI compatibility test results.

OpenClawnative officialProvenance: registry distribution

Independent structural checks

These checks parse the fixed package against dated platform rules. They do not execute the Skill or verify task behavior.

Claude Codepasses structure
Checker 0.1.0 · agent-skills-2026-08-13+claude-code-docs-2026-08-13 · 9/2/2026.claude/skills/cargo-diagnostics

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenAI Codexpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+codex-docs-2026-08-13 · 9/2/2026.agents/skills/cargo-diagnostics

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

OpenClawpasses structure
Checker 0.1.0 · agent-skills-2026-08-13+openclaw-docs-2026-08-13 · 9/2/2026skills/cargo-diagnostics

Runtime, accounts, dependencies, permissions, network behavior and task quality remain untested.

Installation and inspection

This command is recorded from the source ecosystem and resolves the registry's latest release. The fixed release shown on this page should be inspected before adoption.

clawhub install @cargo-ai/cargo-diagnostics
clawhub inspect @cargo-ai/cargo-diagnostics --version 1.4.0

Security evidence

SkillVetAI static result: no findings detected

This automated, non-executing scan is bound to this release hash. It is not a safety certification and may contain false positives or false negatives.

Status
completed
Coverage
full text content
Files
6 / 6 inspected as text
Checked
9/2/2026, 4:32:29 AM
Scanner
0.1.3
Policy
1.0.3
2 inferred permission indicators
  • network access — automatically inferred
  • filesystem write — automatically inferred
2 dependency and API indicators
  • api: clawhub.ai
  • api: github.com
External clawhub result: clean

This is registry-supplied evidence for the recorded release, not an independent SkillVetAI scan. Check the canonical source for the full report, scanner versions, scope, and current moderation state.

Evidence checked
9/1/2026, 11:33:01 PM
Release binding
Matches this record
  • vt: clean
  • skillspector: clean
  • llm: clean

Recorded files

The catalog stores hashes and an inventory summary for change detection. It does not republish the package contents.

Package content hashsha256:e08005e03abc865e93393afac8ac702051120a5564c666fe847ffa2866d22d1f
Show up to 6 recorded paths
  • references/batch-error-sweep.md
  • references/play-optimize-credits.md
  • references/run-trace.md
  • skill-card.md
  • skill-metadata.json
  • SKILL.md

Source changelog

cargo-diagnostics 1.4.0 - Adds explicit documentation of execution charge (0.01 credits per node execution) in cost attribution for play credit optimization. - Updates references/play-optimize-credits.md to reflect the above and clarify how execution charge is handled. - Updates version to 1.4.0 in skill metadata. - Removes the legacy skill-card.md file.

Release security diff

mediumCompared fixed releases 1.3.0 and 1.4.0; 0 finding and 0 permission indicators were added.

Both fixed releases were scanned under the current scanner and policy, so finding, permission and dependency changes are available.

Change reasons and limitations
  • content hash changed

Observed release history

These older immutable releases were observed by prior successful syncs. They remain recorded when a newer release becomes current.

1.3.08/16/2026sha256:ca87aa49f57e4a23010607cd903cb53f10db3b69d9e606ba7e3524975d0b76e7
1.2.08/15/2026sha256:aef874b6b5ee9c7b5279bd391196ccc0a2e2e60e3f0d1ae7f847530ee550a66b
1.1.08/14/2026sha256:e1d8336d9ea5cc4d834dd5464120a2d5cce70832917309ee03ea78d074d45050