cargo-diagnostics

SKILLWorkflowcommunauté
v0.0.0getcargohqMITMis à jour il y a 1 moisSource →

Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, 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

Community-submitted skill. Not yet reviewed by the Forge team. Full prompt content may not be available.Request review →
15Étoiles du dépôt
1Clients
1Formats
il y a 1 moisDernière mise à jour
Skill
Auteurgetcargohq
Version0.0.0
LicenceMIT
CatégorieWorkflow
Formatsskill.md
PromptNon publié
Compatibilité
Claude✓ Pris en charge
Cursor—
Copilot—
ChatGPT—
Gemini—
À propos

Explain what a Cargo run or batch actually did, after the fact — trace one run node by node, 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 muc

Mots-clés
skillclaude

Aucune couverture des dépendances

Cette entrée ne publie aucun paquet npm : Forge n'a donc pas d'arbre de dépendances pour elle. C'est une lacune de couverture — pas une affirmation qu'elle n'a aucune dépendance.