Agent skill

Runtime Error Explainer

by ArabelaTso in ArabelaTso/Skills-4-SE

Explains runtime errors and compilation failures with actionable debugging guidance.

Apache-2.0Auto-check passedDevelopment

Install Runtime Error Explainer

skills CLI
$ npx skills add ArabelaTso/Skills-4-SE --skill runtime-error-explainer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ArabelaTso/Skills-4-SE runtime-error-explainer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ArabelaTso/Skills-4-SE.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/runtime-error-explainer .claude/skills/runtime-error-explainer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
runtime-error-explainer
GitHub stars
253
Token cost
~4.8k tokens
SKILL.md length
1,027 words
Files
3 (incl. references)
Skills in repo
151
Repo updated
First seen
Licence
Apache-2.0

At a glance

Explains runtime errors and compilation failures with actionable debugging guidance.

  • Works in 5 steps: Gather Error Context → Categorize the Error → Extract Key Information → …
  • Java code throws runtime exceptions (NullPointerException
  • SKILL.md covers Core Capabilities, Error Analysis Workflow, Verification and Prevention, plus 8 more sections
  • Calls python, java and javac

What it does

Runtime Error Explainer is an agent skill from ArabelaTso/Skills-4-SE. Explains runtime errors and compilation failures with actionable debugging guidance. Use when Python or Java code throws runtime exceptions (NullPointerException, TypeError, AttributeError, etc.), compilation errors (syntax errors, type mismatches, import failures), or dependency issues. Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples. Distinct from test-related errors - focuses on errors during normal code execution and build processes.

Its SKILL.md is about 4.8k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/debugging_guide.md` and `references/error_catalog.md`).

It sits in Development, covering Debugging and Root cause analysis. It works with Python and Java. The repository describes itself as: A curated list of 180+ useful Claude Skills for Software Engineering and resources for customizing AI for SE workflows. The licence is Apache-2.0.

When your agent uses it

  • Java code throws runtime exceptions (NullPointerException
  • Compilation errors (syntax errors
  • Type mismatches
  • Import failures)

Example prompts

  • “Use the runtime-error-explainer skill to explain runtime errors and compilation failures with actionable debugging guidance”
  • “/runtime-error-explainer”

Requirements

  • Python 3

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Gather Error Context
  2. Categorize the Error
  3. Extract Key Information
  4. Identify Root Cause
  5. Provide Explanation

What it can do on your machine

Read from SKILL.md and the folder at commit 4f38503. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • python
    • java
    • javac
    • pip
    • pip3

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pip and pip3, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Runtime Error Explainer loads about 4.8k tokens when it runs, and up to ~14k if it reads all its reference files. Until then it costs about 135 tokens; SKILL.md has 1,027 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~135
When it runs · the whole SKILL.md, loaded when a task matches
~4.8k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~14k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from ArabelaTso/Skills-4-SE at commit 4f38503, republished under its Apache-2.0 licence (© ArabelaTso). 1,027 words, ~4,750 tokens.

Download SKILL.mdSave it as .claude/skills/runtime-error-explainer/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
runtime-error-explainer
description
Explains runtime errors and compilation failures with actionable debugging guidance. Use when Python or Java code throws runtime exceptions (NullPointerException, TypeError, AttributeError, etc.), compilation errors (syntax errors, type mismatches, import failures), or dependency issues. Analyzes error messages, stack traces, and code context to identify root causes and provide concrete fixes with examples. Distinct from test-related errors - focuses on errors during normal code execution and build processes.

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:

  1. Parsing error output - Extract key information from error messages and stack traces
  2. Identifying root causes - Determine why errors occur during execution or compilation
  3. Explaining clearly - Translate technical errors into understandable language
  4. Providing fixes - Suggest concrete code changes with before/after examples
  5. 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:

bash
# 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:

  1. Syntax/Compilation Errors

    • Python: SyntaxError, IndentationError
    • Java: Compilation errors (missing semicolons, type errors)
  2. Runtime Errors

    • Python: TypeError, AttributeError, ValueError, KeyError, IndexError
    • Java: NullPointerException, IllegalArgumentException, ArrayIndexOutOfBoundsException
  3. Import/Dependency Errors

    • Python: ImportError, ModuleNotFoundError
    • Java: ClassNotFoundException, NoClassDefFoundError
  4. Type Errors

    • Python: TypeError (wrong types in operations)
    • Java: Type mismatch compilation errors
  5. Name/Reference Errors

    • Python: NameError, UnboundLocalError
    • Java: Variable not initialized, cannot find symbol
Step 3: Extract Key Information

Pull out critical details from the error.

From Error Message:

  • Error type and name
  • Error description
  • Line number where error occurred
  • File name
  • Variable names or values involved

From Stack Trace:

  • Execution path leading to error
  • Function/method call chain
  • Origin of error in your code vs. library code

Example Python Error:

Traceback (most recent call last):
  File "app.py", line 45, in <module>
    result = process_user(None)
  File "app.py", line 12, in process_user
    return user.name.upper()
AttributeError: 'NoneType' object has no attribute 'name'

Extracted Information:

  • Error type: AttributeError
  • Problem: Tried to access .name on None
  • Location: app.py line 12, in process_user function
  • Root cause: user parameter is None
Step 4: Identify Root Cause

Analyze why the error occurred.

Common Root Causes:

Syntax/Compilation:

  • Missing or mismatched parentheses/brackets
  • Incorrect indentation (Python)
  • Missing semicolons (Java)
  • Typos in keywords or variable names

Runtime:

  • Null/None values where objects expected
  • Wrong data types in operations
  • Index out of bounds
  • Missing dictionary keys
  • Division by zero
  • File not found

Import/Dependency:

  • Module/package not installed
  • Incorrect import path
  • Circular imports
  • Classpath issues (Java)

See references/error_catalog.md for detailed root cause analysis for each error type.

Step 5: Provide Explanation

Structure the explanation with clear sections.

Explanation Template:

markdown
## Error Summary

[One-sentence description of what went wrong]

## What Happened

[Explain the error in plain language]

**Error Type:** [Error name and category]
**Location:** [File and line number]
**Problem:** [What specifically failed]

## Root Cause

[Explain why this happened - the underlying issue]

## How to Fix

### Solution 1: [Most common fix] ⭐

[Specific code change or action]

```[language]
# Before
[problematic code]

# After
[fixed code]

Why this works: [Brief explanation]

Solution 2: [Alternative approach]

[Another fix if Solution 1 doesn't apply]

Verification

[How to verify the fix works]

bash
[command to test]

Prevention

[How to avoid this error in future]

  • [Best practice 1]
  • [Best practice 2]
  • [Tool or technique recommendation]

### Step 6: Suggest Next Steps

Provide actionable debugging guidance.

**If fix is straightforward:**
- Show exact code change
- Provide command to verify
- Mention related code to review

**If more investigation needed:**
- Suggest adding print/logging statements
- Recommend debugging tools
- Propose simplification to isolate issue

**If environmental issue:**
- Suggest checking installation/versions
- Recommend environment verification
- Propose configuration review

## Common Error Patterns

### Python: AttributeError - NoneType

**Error:**

AttributeError: 'NoneType' object has no attribute 'method_name'


**Explanation:**

```markdown
## Error Summary
Attempted to call a method on None instead of an object instance.

## What Happened

**Error Type:** AttributeError
**Problem:** Code tried to access an attribute or method on `None`

Python functions return `None` by default if no explicit return statement is
used. When you try to call a method on `None`, you get this error.

## Root Cause

Common causes:
1. Function didn't return a value but you expected an object
2. Variable not initialized before use
3. Database/API query returned no result
4. Method called before object creation

## How to Fix

### Solution 1: Add None check ⭐

```python
# Before
result = get_user(user_id)
name = result.name  # Crashes if result is None

# After
result = get_user(user_id)
if result is not None:
    name = result.name
else:
    name = "Unknown"

Why this works: Defensively handles the case where get_user returns None.

Solution 2: Fix the source function to always return a value
python
# Before
def get_user(user_id):
    if user_id in users:
        return users[user_id]
    # Implicitly returns None

# After
def get_user(user_id):
    if user_id in users:
        return users[user_id]
    return User(id=user_id, name="Guest")  # Return default user
Solution 3: Use walrus operator with conditional (Python 3.8+)
python
# Assign and check in one line
if (result := get_user(user_id)) is not None:
    name = result.name

Verification

bash
python script.py

Prevention

  • Always check return values before using them
  • Use type hints: def get_user(user_id: int) -> Optional[User]:
  • Add assertions: assert result is not None, "User not found"
  • Use Optional type and handle None explicitly

### Python: ImportError / ModuleNotFoundError

**Error:**

ModuleNotFoundError: No module named 'requests'


**Explanation:**

```markdown
## Error Summary
Python cannot find the module you're trying to import.

## What Happened

**Error Type:** ModuleNotFoundError (Python 3) or ImportError (Python 2)
**Problem:** The module is not installed or not in Python's path

## Root Cause

1. Package not installed via pip
2. Wrong virtual environment activated
3. Typo in module name
4. Package installed in different Python version

## How to Fix

### Solution 1: Install the missing package ⭐

```bash
# Install package
pip install requests

# Or if using Python 3 explicitly
pip3 install requests

# Or with specific Python version
python -m pip install requests

Why this works: Makes the package available to your Python environment.

Solution 2: Activate correct virtual environment
bash
# Check current environment
which python

# Activate virtual environment
source venv/bin/activate  # Linux/Mac
venv\Scripts\activate     # Windows

# Install package in virtual environment
pip install requests
Solution 3: Check for typos
python
# Wrong
import reqests  # Typo

# Correct
import requests

Verification

bash
python -c "import requests; print('Success')"

Prevention

  • Use requirements.txt: pip install -r requirements.txt
  • Use virtual environments for project isolation
  • Document all dependencies
  • Use pip freeze > requirements.txt to capture dependencies

### Java: NullPointerException

**Error:**

Exception in thread "main" java.lang.NullPointerException at com.example.MyClass.process(MyClass.java:25)


**Explanation:**

```markdown
## Error Summary
Attempted to use an object reference that is null.

## What Happened

**Error Type:** NullPointerException
**Location:** MyClass.java, line 25
**Problem:** Tried to access a method or field on a null object

## Root Cause

Common causes:
1. Object not initialized before use
2. Method returned null unexpectedly
3. Array element is null
4. Forgotten to instantiate object

## How to Fix

### Solution 1: Add null check ⭐

```java
// Before
String name = user.getName().toUpperCase();

// After
if (user != null && user.getName() != null) {
    String name = user.getName().toUpperCase();
} else {
    String name = "UNKNOWN";
}

Why this works: Prevents accessing methods on null references.

Solution 2: Use Optional (Java 8+)
java
// Before
public User getUser(int id) {
    return userMap.get(id);  // Returns null if not found
}

String name = getUser(123).getName();  // NPE if user not found

// After
public Optional<User> getUser(int id) {
    return Optional.ofNullable(userMap.get(id));
}

String name = getUser(123)
    .map(User::getName)
    .orElse("Unknown");
Solution 3: Initialize objects properly
java
// Before
private User user;  // Field is null by default

public void process() {
    user.getName();  // NullPointerException
}

// After
private User user = new User();  // Initialize at declaration

// Or in constructor
public MyClass() {
    this.user = new User();
}
Solution 4: Use Objects utility (Java 7+)
java
import java.util.Objects;

// Throw meaningful exception if null
Objects.requireNonNull(user, "User must not be null");
String name = user.getName();

Verification

bash
javac MyClass.java && java MyClass

Prevention

  • Initialize all object fields
  • Use Optional for potentially null values
  • Add @Nullable/@NonNull annotations
  • Enable null-safety warnings in IDE
  • Consider using Objects.requireNonNull() for critical parameters

### Java: ClassNotFoundException

**Error:**

java.lang.ClassNotFoundException: com.example.MyClass at java.net.URLClassLoader.findClass(URLClassLoader.java:382)


**Explanation:**

```markdown
## Error Summary
Java cannot find the specified class at runtime.

## What Happened

**Error Type:** ClassNotFoundException
**Problem:** Class exists in source code but not found when running

## Root Cause

1. Class not in classpath
2. Package name doesn't match directory structure
3. .class file not compiled
4. Typo in class name
5. JAR file not included

## How to Fix

### Solution 1: Check classpath ⭐

```bash
# Compile with source files in correct package structure
javac -d bin src/com/example/MyClass.java

# Run with classpath pointing to bin directory
java -cp bin com.example.MyClass

Why this works: Ensures compiled .class files are in classpath.

Show full SKILL.md (402 more words)Show less
Solution 2: Verify package structure matches directories
Project structure should be:
src/
  com/
    example/
      MyClass.java
java
// MyClass.java must declare matching package
package com.example;

public class MyClass {
    public static void main(String[] args) {
        System.out.println("Hello");
    }
}
Solution 3: Include JAR files in classpath
bash
# If MyClass is in external JAR
java -cp "lib/mylib.jar:." com.example.MyClass

# Windows (use semicolon)
java -cp "lib/mylib.jar;." com.example.MyClass

Maven automatically manages classpaths.

xml
<!-- pom.xml -->
<dependencies>
    <dependency>
        <groupId>com.example</groupId>
        <artifactId>my-library</artifactId>
        <version>1.0.0</version>
    </dependency>
</dependencies>

Verification

bash
# Check if class file exists
ls bin/com/example/MyClass.class

# Verify package declaration matches
head -1 src/com/example/MyClass.java

Prevention

  • Use build tools (Maven, Gradle) to manage dependencies
  • Follow Java package naming conventions
  • Keep package declarations synchronized with directory structure
  • Use IDE features to auto-manage imports and packages

### Python: SyntaxError

**Error:**

File "script.py", line 10 if x == 5 ^ SyntaxError: invalid syntax


**Explanation:**

```markdown
## Error Summary
Code has syntax error preventing Python from parsing it.

## What Happened

**Error Type:** SyntaxError
**Location:** Line 10
**Problem:** Missing colon at end of if statement

## Root Cause

Python syntax violated - common causes:
- Missing colons after if/for/while/def/class
- Unmatched parentheses/brackets
- Incorrect indentation
- Invalid operator usage

## How to Fix

### Solution 1: Add missing colon ⭐

```python
# Before
if x == 5
    print("Five")

# After
if x == 5:
    print("Five")

Why this works: Python requires colon to start code blocks.

Solution 2: Check for unmatched brackets
python
# Before
result = calculate(a, b, (c + d)
print(result)

# After
result = calculate(a, b, (c + d))
print(result)
Solution 3: Fix indentation
python
# Before (mixing tabs and spaces)
def my_function():
    x = 5
  return x  # Indentation error

# After (consistent spaces)
def my_function():
    x = 5
    return x

Verification

bash
# Python will parse file without running
python -m py_compile script.py

# Or just run it
python script.py

Prevention

  • Use IDE with syntax highlighting
  • Enable linting (pylint, flake8)
  • Use auto-formatters (black, autopep8)
  • Configure editor to show whitespace characters

### Java: Type Mismatch Compilation Error

**Error:**

MyClass.java:15: error: incompatible types: int cannot be converted to String String result = 42; ^


**Explanation:**

```markdown
## Error Summary
Trying to assign value of wrong type to variable.

## What Happened

**Error Type:** Compilation error - type mismatch
**Location:** Line 15
**Problem:** Assigning int (42) to String variable

## Root Cause

Java is statically typed - variables can only hold values of declared type
or compatible types.

## How to Fix

### Solution 1: Convert type explicitly ⭐

```java
// Before
String result = 42;

// After
String result = String.valueOf(42);
// or
String result = Integer.toString(42);
// or
String result = "" + 42;  // Concatenation with empty string

Why this works: Explicitly converts int to String.

Solution 2: Change variable type
java
// Before
String result = 42;

// After
int result = 42;
Solution 3: Use correct literal type
java
// Before (assigning int to double)
double price = 10;  // Works but not ideal

// After (use double literal)
double price = 10.0;

Verification

bash
javac MyClass.java

Prevention

  • Use proper type conversions
  • Be aware of implicit type casting rules
  • Use IDE suggestions for quick fixes
  • Understand primitive types vs object types (int vs Integer)

## Language-Specific Notes

### Python Error Characteristics

**Common Patterns:**
- Runtime errors only (no compilation phase)
- Clear stack traces with file/line numbers
- Descriptive error messages
- Exception hierarchy (all inherit from BaseException)

**Key Files to Check:**
- Module `__init__.py` for package imports
- `sys.path` for import resolution
- Virtual environment activation

**Debugging Tools:**
```bash
# Interactive debugging
python -m pdb script.py

# Print traceback programmatically
import traceback
traceback.print_exc()
Java Error Characteristics

Common Patterns:

  • Compilation errors vs runtime errors
  • Less descriptive error messages than Python
  • Line numbers in stack traces
  • Checked vs unchecked exceptions

Key Files to Check:

  • pom.xml (Maven) or build.gradle (Gradle)
  • Package structure matches directory structure
  • CLASSPATH environment variable

Debugging Tools:

bash
# Verbose compilation
javac -verbose MyClass.java

# Show detailed exception messages (Java 14+)
java -XX:+ShowCodeDetailsInExceptionMessages MyClass

# Using debugger
jdb MyClass

Quick Reference: Error Categories

CategoryPython ExamplesJava ExamplesCommon Fix
Null/None errorsAttributeError on NoneNullPointerExceptionAdd null checks
Type errorsTypeErrorType mismatch errorFix types or convert
Import errorsModuleNotFoundErrorClassNotFoundExceptionCheck imports/classpath
Syntax errorsSyntaxErrorCompilation errorsFix syntax
Index errorsIndexErrorArrayIndexOutOfBoundsExceptionCheck array bounds
Name errorsNameErrorCannot find symbolFix variable names
Key errorsKeyError-Check dict keys exist

Resources

  • references/error_catalog.md - Comprehensive catalog of Python and Java errors with detailed examples, root causes, and solutions
  • references/debugging_guide.md - Systematic debugging strategies, tools, and techniques for complex errors

Best Practices

  1. Read the full error message - Don't skip stack traces
  2. Identify error location - Line number and file are critical
  3. Understand the error type - Each type has typical causes
  4. Check recent changes - Often errors relate to recent edits
  5. Reproduce consistently - Ensure error happens reliably
  6. Simplify to isolate - Remove code until error disappears
  7. Use debugging tools - Debuggers are more powerful than print statements
  8. Fix root cause, not symptoms - Adding try/except without understanding hides problems
  9. Add defensive code - Null checks, type validation prevent errors
  10. Learn from errors - Understand why it happened to prevent recurrence

© ArabelaTso, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in skills/runtime-error-explainer of ArabelaTso/Skills-4-SE.

  • SKILL.md
  • references/debugging_guide.md
  • references/error_catalog.md

Open the folder on GitHubat commit 4f38503

Compare with similar skills

Runtime Error Explainer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Runtime Error Explainer compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Runtime Error Explainer this skillArabelaTso/Skills-4-SE253—~4.8kAutomated safety check: PassApache-2.0
Git History Bug Auditben-manes/caffeine18k—~3.3kAutomated safety check: PassApache-2.0
The Art of Debuggingstas00/the-art-of-debugging1.7k—~6.1kAutomated safety check: NotesCC-BY-SA-4.0
MCP Debuggerdebugmcp/mcp-debugger171—~3.8kAutomated safety check: PassMIT
Dbgtheodo-group/debug-that158—~1.9kAutomated safety check: PassMIT
WxJava Troubleshooterbinarywang/WxJava33k—~135Automated safety check: PassApache-2.0

Similar skills

  • Git History Bug Audit

    ben-manes/caffeine

    Audits a module by walking its git history commit by commit, tracking unresolved issues forward, and reporting the ones that survive to HEAD as findings.

    18k GitHub stars~3.3k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • The Art of Debugging

    stas00/the-art-of-debugging

    Condensed debugging method and tool recipes for Unix, Python and PyTorch programs: crashes, hangs, segfaults, wrong output, CUDA OOM, NaN values and slowness.

    1.7k GitHub stars~6.1k tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • MCP Debugger

    debugmcp/mcp-debugger

    A skill your agent uses when investigating a bug, failing test, or unexpected runtime behavior and the mcp-debugger MCP server is available — drives real step-through debuggers (breakpoints, stack…

    171 GitHub stars~3.8k tokensUpdated yesterday
    DevelopmentAuto-check passed
  • Dbg

    theodo-group/debug-that

    Debug applications using the dbg CLI debugger. An agent skill from theodo-group/debug-that.

    158 GitHub stars~1.9k tokensUpdated 4 mo ago
    DevelopmentAuto-check passed
  • WxJava Troubleshooter

    binarywang/WxJava

    排查 WxJava 在配置初始化、access token、签名验签、支付证书、回调通知、序列化、网络请求和多账号隔离方面的问题。适用于用户提供异常、日志、请求响应或“WxJava 为什么不能调用”的场景。

    33k GitHub stars~135 tokensUpdated 11 days ago
    DevelopmentAuto-check passed
  • Problem Solving Pro

    HoangTheQuyen/think-better

    Systematic problem-solving toolkit: root cause analysis, hypothesis testing, debugging strategies, critical thinking frameworks.

    122 GitHub stars~2.8k tokensUpdated 6 mo ago
    DevelopmentAuto-check: notes

More from ArabelaTso/Skills-4-SE

All 151 skills in this repo
  • Framework Migration Assistant

    ArabelaTso/Skills-4-SE

    Automatically migrate Python web applications between frameworks (Flask → FastAPI, Django → FastAPI).

    253 GitHub stars~1.9k tokensUpdated 1 mo ago
    Auto-check passed
  • Metamorphic Test Generator

    ArabelaTso/Skills-4-SE

    Generate test cases using metamorphic testing by applying transformations based on metamorphic properties.

    253 GitHub stars~798 tokensUpdated 1 mo ago
    Auto-check passed
  • Reproduction Trace Instrumenter

    ArabelaTso/Skills-4-SE

    Instruments programs to capture execution traces specifically for reproducing reported bugs, enabling consistent replay and diagnosis of failures.

    253 GitHub stars~2.4k tokensUpdated 1 mo ago
    Auto-check passed
  • Spring Mvc To Boot Migrator

    ArabelaTso/Skills-4-SE

    Automatically migrate Spring MVC applications to Spring Boot.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed
  • State Snapshot Instrumenter

    ArabelaTso/Skills-4-SE

    Instrument programs (Python, C/C++, Java) to capture snapshots of key program states at runtime, including variables, memory, and call stacks.

    253 GitHub stars~2.2k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Runtime Error Explainer

What does Runtime Error Explainer do?

Explains runtime errors and compilation failures with actionable debugging guidance. Runtime Error Explainer is an agent skill from ArabelaTso/Skills-4-SE. Explains runtime errors and compilation failures with actionable debugging guidance.

When should I use Runtime Error Explainer?

Runtime Error Explainer fits situations like: java code throws runtime exceptions (NullPointerException; compilation errors (syntax errors; type mismatches; import failures).

How do I install Runtime Error Explainer in Claude Code?

Run `npx skills add ArabelaTso/Skills-4-SE --skill runtime-error-explainer -a claude-code`. Or copy the skill folder (skills/runtime-error-explainer in ArabelaTso/Skills-4-SE) into .claude/skills/runtime-error-explainer in your project. Claude Code loads it when a task matches its description.

How do I install Runtime Error Explainer in Codex?

Run `npx skills add ArabelaTso/Skills-4-SE --skill runtime-error-explainer -a codex`. Or copy the skill folder (skills/runtime-error-explainer in ArabelaTso/Skills-4-SE) into .agents/skills/runtime-error-explainer in your project. Codex loads it when a task matches its description.

Can I use Runtime Error Explainer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ArabelaTso/Skills-4-SE --skill runtime-error-explainer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/runtime-error-explainer, .gemini/skills/runtime-error-explainer, .github/skills/runtime-error-explainer and .opencode/skills/runtime-error-explainer in your project.

What does Runtime Error Explainer need to run?

Going by SKILL.md and its folder, Runtime Error Explainer needs the command-line tools its instructions call (python, java, javac, pip and pip3). Our summary lists: Python 3.

Does Runtime Error Explainer access the network?

SKILL.md contains no URLs. Its commands use pip, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Runtime Error Explainer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Runtime Error Explainer use?

Runtime Error Explainer is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Runtime Error Explainer use?

About 4.8k tokens (SKILL.md is roughly 19k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 8.8k tokens, read only when the agent opens those files.

What are the alternatives to Runtime Error Explainer?

Skills that share tags, products or a category with Runtime Error Explainer: Git History Bug Audit (ben-manes/caffeine, 18k stars), The Art of Debugging (stas00/the-art-of-debugging, 1.7k stars), MCP Debugger (debugmcp/mcp-debugger, 171 stars) and Dbg (theodo-group/debug-that, 158 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Runtime Error Explainer?

ArabelaTso (a GitHub user) maintains it in ArabelaTso/Skills-4-SE, which has 253 GitHub stars. The repository holds 151 skills in this directory. The repository was last updated on August 21, 2026.

Source: ArabelaTso/Skills-4-SE on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.