Skip to content
Skills Library
Programming · Analysis

error-reading

/error-reading

Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis

Author
tspry ↗
Licence
MIT
Last repository change
20.10.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis

Original author description

Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis

How it works

  1. Works In Both Modes
  2. Process
  3. Quick Reference: Common Errors
Original SKILL.md headings · 89 lines, 639 words
SKILL.md preview
---
name: error-reading
description: Use when the user pastes any error output, stack trace, log, or failure message — structured interpretation before diagnosis
---

# Error Reading

## Works In Both Modes

This skill works entirely from pasted content. No local files needed.

## Process

### Step 1 — Identify the error type

Classify what you're looking at:
- **Stack trace** (application crash — Python, Node, Java, Go, etc.)
- **Build/compile failure** (CI, Docker build, npm/pip/cargo error)
- **K8s/container error** (CrashLoopBackOff, OOMKilled, ImagePullBackOff, etc.)
- **Infrastructure error** (Terraform, Ansible, Pulumi)
- **Cloud provider error** (AWS, GCP, Azure API error codes)
- **Network/proxy error** (502, 503, 504, connection refused, timeout)
- **CI pipeline failure** (GitHub Actions, GitLab CI, Jenkins)

### Step 2 — Read the full output

Never stop at the first error line. Scan for:
- The **actual root error** (often buried after a chain of caused-by lines)
- The **line number or resource** where it originated
- Any **preceding warnings** that hint at the cause

### Step 3 — Extract key facts

State clearly:
- What failed
- Where it failed (service, file, line, resource)
- What the error code or message means
- What it implies about the root cause

### Step 4 — Hand off to systematic-debugging

Error reading identifies the problem. Systematic debugging finds the root cause and fixes it. After reading the error, invoke `systematic-debugging` if a fix is needed.

## Quick Reference: Common Errors

### Kubernetes
| Error | Meaning |
|---|---|
| `CrashLoopBackOff` | Container keeps crashing on start — check `kubectl logs --previous` |
| `OOMKilled` | Container exceeded memory limit |
| `ImagePullBackOff` | Can't pull the image — wrong name, tag, or registry auth |
| `Pending` | No node has enough resources or matching node selector |
| `CreateContainerConfigError` | Bad env var, missing secret or configmap |

### Docker
| Error | Meaning |
|---|---|
| `no space left on device` | Capacity exhausted somewhere in the storage path — inspect filesystem, Docker object usage, container writable layers, and logs before authorized cleanup |
| `port is already allocated` | Port conflict — find and stop the other process |
| `exec format error` | Wrong architecture (e.g., ARM image on AMD64) |

### Nginx / Proxy
| Error | Meaning |
|---|---|
| `502 Bad Gateway` | Upstream is down or not responding |
| `503 Service Unavailable` | No healthy upstream servers |
| `504 Gateway Timeout` | A configured request deadline expired — identify whether time was spent in DNS, connect, TLS, queueing, application code, a dependency, or response reads |
| `upstream connect error` | Wrong upstream address, port, or firewall blocking |

### Terraform
| Error | Meaning |
|---|---|
| `Error acquiring the state lock` | Another process holds the lock — check for stuck runs |
| `ResourceAlreadyExists` | The remote object already exists — establish its owner and state before deciding whether import is correct |
| `UnauthorizedOperation` | Authorization failed — identify the principal, action, resource, conditions, and controlling policy layer |
| `InvalidInstanceType` | Instance type not available in that region |

### AWS
| Error | Meaning |
|---|---|
| `AccessDenied` | Authorization failed — distinguish explicit/implicit denial and evaluate every applicable policy layer before changing permissions |
| `ThrottlingException` | API rate limit — add retry logic with backoff |
| `InvalidClientTokenId` | Wrong AWS credentials or region |

Quick-reference entries classify evidence; they do not authorize a fix. Do not jump from disk pressure to pruning, an existing object to import, a timeout to a larger timeout, or an authorization error to broader permissions.

### GitHub Actions
| Error | Meaning |
|---|---|
| `Process completed with exit code 1` | A step failed — read that step's logs |
| `Context access might be invalid` | Wrong secret name or env var reference |
| `Resource not accessible by integration` | Missing permissions in workflow YAML |

Versions

RepositoryScoreLicence
This page · tspry/superpowers-devops90MIT
nikospavlopoulos/devops-mutant-powers100MIT

Database snapshot: 13.11.2026 · package version d71846fbe206 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100debug-triage
    Use when triaging a pasted error, stack trace, or terminal transcript. Activates on "debug this", "fix this", "why is this broken", or when a user pastes red terminal output. Produces a tight cause-fix-test report, not a lecture.
  • 100debug-detective
    Find the root cause of a bug, crash, error message or failing test, then fix it. Use when the user says "this is broken", "why does this fail", "I get this error", "the test is failing", "it worked yesterday", or pastes a stack trace.
  • 100debug-issue
    Systematic debugging workflow for any code error, crash, test failure, or unexpected behavior. Use this skill whenever a user mentions an error, bug, exception, crash, test failure, or says something "isn't working", "is broken", "keeps failing", or "isn't behaving as expected"…
  • 100verify-and-fix
    This skill should be used when the user reports an error, bug, or unexpected behavior and wants it diagnosed and fixed. Trigger on phrases like "check this error", "check this bug", "here's an error", "here's a bug", "I have an error", "I have a bug", "found a bug", "got an…
  • 95fixatlas-diagnose-error
    Diagnose compiler, package-manager, runtime, Git, and build errors with FixAtlas evidence. Use when a developer shares an error message, build log, stack trace, or failed command output.
  • 90stack-trace-reading
    Read a stack trace to find the cause frame instead of stopping at the symptom on top. Use when an exception, panic, or error dump lands and you need to locate the line that is actually wrong.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.