skill-diagnosis

Diagnose skill execution failures and generate structured corrective action reports.

Updated Mar 21, 2026
One-click install
npx skills add https://github.com/debridge-finance/debridge-skills --skill skill-diagnosis
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-diagnosis
Source: https://github.com/debridge-finance/debridge-skills/tree/main/.claude/skills/skill-diagnosis
Command: npx skills add https://github.com/debridge-finance/debridge-skills --skill skill-diagnosis

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze execution failures and user corrections, determine the root cause, and take corrective action — either fix the skill in this repo or file a bug upstream.

Core Features & Use Cases

  • Identify when a skill execution fails or produces unexpected results and map the issue to a corrective action.
  • Classify root causes (skill-gap, skill-ambiguity, script-missing, script-bug, agent-drift, external-bug) and guide remediation.
  • Generate a structured report outlining fixes, bug reports, or upstream changes to ensure alignment with the skill's intended flow.

Quick Start

Diagnose a failed skill run by identifying what went wrong, the root cause, and the recommended action to restore correct behavior.

Frequently Asked Questions about skill-diagnosis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I diagnose why a skill execution failed or underperformed?

To diagnose skill execution failures, identify what went wrong, classify the root cause—such as skill-gap, script-bug, or agent-drift—and generate a structured report outlining recommended corrective actions.

What is root-cause analysis for agent behavior corrections?

Root-cause analysis for agent corrections maps unexpected skill execution results to specific failure categories, determining whether the issue stems from skill ambiguity, missing scripts, or external bugs to guide remediation.

How do I classify bug-tracking categories when a skill diverges from its prescribed flow?

Classify bug-tracking categories by identifying failures where ad-hoc commands were used or steps diverged, mapping them to root causes like skill-gap, script-missing, script-bug, agent-drift, or external-bug.

Can I generate a structured report for skill debugging and upstream bug filing?

Yes, skill debugging generates a structured action report that outlines fixes, bug reports, or upstream changes to restore correct behavior and ensure alignment with the intended execution flow.

What's the best way to fix skill ambiguity and restore correct agent behavior?

The best way to fix skill ambiguity is to classify the root cause, apply corrective actions to the skill in your repo, or file an upstream bug report, generating a structured report to verify alignment.