Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add ArabelaTso/Skills-4-SE --skill runtime-error-explainergit clone --depth 1 https://github.com/ArabelaTso/Skills-4-SEWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/arabelatso/skills-4-se/runtime-error-explainer)<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/runtime-error-explainer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/runtime-error-explainer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/arabelatso/skills-4-se/runtime-error-explainer"><img src="https://agentmods.dev/badge/skills/arabelatso/skills-4-se/runtime-error-explainer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.04476 |
| Opus 5.5 | $0.00039 | $0.01790 |
| Sonnet 5.5 | $0.00020 | $0.00895 |
| Haiku 4.5 | $0.00010 | $0.00448 |
Grade A, and why
runtime-error-explainer scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 850 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Runtime Error Explainer
Analyze runtime and compilation errors with clear explanations and actionable fixes.
Core Capabilities
This skill helps debug runtime and compilation errors by:
- Parsing error output - Extract key information from error messages and stack traces
- Identifying root causes - Determine why errors occur during execution or compilation
- Explaining clearly - Translate technical errors into understandable language
- Providing fixes - Suggest concrete code changes with before/after examples
- Preventing recurrence - Recommend best practices to avoid similar errors
Error Analysis Workflow
Step 1: Gather Error Context
Collect all relevant information about the error.
Essential Information:
- Complete error message and stack trace
- Programming language and version
- Code that triggered the error
- How the error was triggered (command, action, input)
Additional Context (if available):
- Recent code changes
- Environment details (OS, IDE, dependencies)
- Input data or parameters that caused error
- Configuration files
How to Gather:
# Python - Run with full traceback
python script.py
# Python - More verbose error output
python -v script.py
# Java - Compile with verbose output
javac -verbose MyClass.java
# Java - Run with stack trace
java -XX:+ShowCodeDetailsInExceptionMessages MyClass
Step 2: Categorize the Error
Identify the error type using references/error_catalog.md:
Error Categories:
-
Syntax/Compilation Errors
- Python: SyntaxError, IndentationError
- Java: Compilation errors (missing semicolons, type errors)
-
Runtime Errors
- Python: TypeError, AttributeError, ValueError, KeyError, IndexError
- Java: NullPointerException, IllegalArgumentException, ArrayIndexOutOfBoundsException
-
Import/Dependency Errors
- Python: ImportError, ModuleNotFoundError
- Java: ClassNotFoundException, NoClassDefFoundError
-
Type Errors
- Python: TypeError (wrong types in operations)
- Java: Type mismatch compilation errors
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 850 lines · 98 tokens per session scan A 0747239ab130
runtime-error-explainer is a skill published in the GitHub repository ArabelaTso/Skills-4-SE (258 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 98 tokens to every session and 4,476 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
diagnose
Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.
skill-incident-management
Incident response, postmortem facilitation, root cause analysis (RCA), blameless culture, incident timeline documentation, and incident classification. Use when responding to production incidents, writing incident reports, facilitating postmortems, or improving incident response processes.
triage
Triage issues through a state machine driven by triage roles. Use when user wants to create an issue, triage issues, review incoming bugs or feature requests, prepare issues for an AFK agent, or manage issue workflow.
skill-performance-optimization
Profile systems, identify bottlenecks, optimize code and infrastructure for speed, throughput, and resource efficiency.
skill-code-quality
This skill should be used when implementing code quality standards, setting up linting/testing/security scans, enforcing coverage thresholds, or establishing CI/CD guardrails.
skill-pr-review
Comprehensive code review for pull requests using parallel multi-agent analysis. Audits CLAUDE.md compliance, checks for bugs, analyzes git history, reviews comments, and filters by confidence score. Use when reviewing a GitHub PR, mentions "code review", "review this PR", or "/code-review".