Extract Errors
Identifies and categorizes error messages from logs or text to aid in debugging and issue resolution.
Install on your platform
We auto-selected Claude Code based on this skill’s supported platforms.
Run in terminal (recommended)
claude mcp add extract-errors npx -- -y @trustedskills/extract-errors
Or manually add to ~/.claude/settings.json
{
"mcpServers": {
"extract-errors": {
"command": "npx",
"args": [
"-y",
"@trustedskills/extract-errors"
]
}
}
}Requires Claude Code (claude CLI). Run claude --version to verify your install.
About This Skill
What it does
The extract-errors skill identifies and extracts error messages from code or logs, helping developers quickly pinpoint issues in their applications. It is particularly useful for parsing verbose output and isolating relevant error information.
When to use it
- Debugging a failing test suite where the console output contains multiple errors.
- Analyzing server logs that include mixed content of warnings and errors.
- Parsing build or compilation outputs from tools like Babel, TypeScript, or Webpack.
Key capabilities
- Parses error messages from text logs or code outputs.
- Extracts relevant stack traces and error codes.
- Filters out non-error information for clarity.
Example prompts
- "Extract all errors from this log file."
- "Find the most recent error in the build output."
- "List all error messages from the last test run."
Tips & gotchas
- Ensure logs or code outputs are provided in a clear, text-based format for best results.
- This skill may not work well with highly obfuscated or minified code.
Tags
TrustedSkills Verification
Unlike other registries that point to live repositories, TrustedSkills pins every skill to a verified commit hash. This protects you from malicious updates — what you install today is exactly what was reviewed and verified.
Security Audits
| Gen Agent Trust Hub | Pass |
| Socket | Pass |
| Snyk | Pass |
🏢 Official
Published by the company or team that built the technology.