Paste a stack trace, get the actual cause
We publish the whole catalogue before we build it, so you can see where this is going and tell us what to prioritise. This page will become the working tool - the URL will not change, so a bookmark now still works later.
Email me when it's live
One email, for this tool only. Signups are also how we decide what to build next - so this is the most direct vote you have.
Your text is redacted before it reaches any AI model: name, email, phone, address and date of birth are replaced with tokens first. The model reads your document and writes the explanations; it never chooses a number - every score is arithmetic over a fixed rubric in our own code. One input to that arithmetic is the model's reading of which skills you evidence, so we store your result and re-running the same input returns it rather than a fresh one. We never invent a figure your own material does not contain.
Credits are a licence to use these tools - not money, not transferable. Full detail in our privacy policy and AI policy.
More from Developer, or browse the full catalogue.
Most stack traces are a known failure mode wearing an unfamiliar message. An engineer who works in your stack will usually name it in the first ten minutes, and spend the rest of the hour on why it happened.
Talk to an engineer from ₹200/hr