PremiumEmail Triage Automation
- Read full threads
- Sort into 3 buckets
- Draft in your voice
- Approve & send
← All skills · Automation · Bug Diagnosis

Premium
Premium
Free
PremiumAn example of what this Skill produces. Sample content, shown for illustration.
Bug diagnosis — sample
Errors: 1 | Symptoms: 2 | Contexts: 2 | Hypotheses: 3 | Gaps: 0 | Errors: 0 | Warnings: 0
Ranked: 1. Null or undefined value at runtime — 3 signals ('cannot read propert', 'undefined', 'typeerror'); 2. Regression from a recent change — 2 signals ('worked yesterday', 'broke after'); 3. Race condition or ordering problem — 1 signal ('works locally').
Flags: Intermittent: no signal; Regression: yes — it worked before and broke after a change.
What this report is not: a hypothesis is a guess to verify, not a diagnosis — the report never names a root cause, only the check that would prove each guess.
Checkout crashes after the deploy with a TypeError about undefined 'email' — what should I check first?Read https://skillu.dev/install/agent.md, then install the Bug Diagnosis skill (bug-diagnosis)./bug-diagnosis, and describe what you want in plain words.No. It means that hypothesis matched the most signals in your error, symptoms, and context — it is the most worth checking first, not the most likely to be right. A real root cause with no signal in your text will not appear at all. Run the verification step; if it rules the guess out, move to the next one.
The report says so plainly and asks for the exact error text and more context. Add the full error message — pasted as it is, not paraphrased — plus what changed and where it runs, then re-run.