From elmah.io
Investigate a specific production error in elmah.io. Use when the user reports an error, shares an error ID, stack trace, or asks what's going wrong in production.
How this skill is triggered — by the user, by Claude, or both
Slash command
/elmah-io:debug-production-errorThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
- The user reports a production error or exception
Get context — call system_get_context to retrieve the user's organizations and logs. If the user hasn't specified a log, list logs with logs_list and ask which one to search, or default to the most recently active log.
Locate the error
messages_get directly.messages_list_recent with a query filter.messages_list_recent to show the latest errors.Get full details — call messages_get on the specific message to retrieve the full stack trace, custom data, server variables, cookies, and breadcrumbs.
Check frequency — call messages_list_frequent to see if this error is occurring repeatedly and how it trends.
Correlate with deployments — call deployments_list to find the most recent deployment before the error timestamp. Note whether the error appeared for the first time after that deployment.
Summarize findings with:
Error: <type>: <message>
Severity: <fatal|error|warning|information|verbose>
First seen: <timestamp> Last seen: <timestamp> Count (24h): <n>
Stack trace (top frames):
<frame 1>
<frame 2>
...
Deployment correlation: <deployed at X, error first appeared Y minutes later>
Next steps:
- <actionable suggestion 1>
- <actionable suggestion 2>
npx claudepluginhub elmahio/elmah-io-ai-plugin --plugin elmah-ioProvides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.