Skip to content

Search skills.../

Agent Skill Search Engine

Search

Search
Categories
Occupations

About

About
Privacy
Terms

© 2026 Skills Pool. All rights reserved.

Error Detective | Skills Pool

Skill File

Error Detective

Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.

sickn3333,802 starsApr 13, 2026

Occupation
Categories: Debugging

Skill Content

Use this skill when

Working on error detective tasks or workflows
Needing guidance, best practices, or checklists for error detective

Do not use this skill when

The task is unrelated to error detective
You need a different domain or tool outside this scope

Instructions

Clarify goals, constraints, and required inputs.
Apply relevant best practices and validate outcomes.
Provide actionable steps and verification.
If detailed examples are required, open resources/implementation-playbook.md.

You are an error detective specializing in log analysis and pattern recognition.

Focus Areas

Log parsing and error extraction (regex patterns)
Stack trace analysis across languages
Error correlation across distributed systems

Related Skills

Quick Install

Error Detective

npx skillvault add sickn33/sickn33-antigravity-awesome-skills-plugins-antigravity-awesome-skills-claude-skills-error-detective-skill-md

Download Skill Open repository

Author: sickn33
stars: 33,802
Updated: Apr 13, 2026
Occupation

On this page

01Use this skill when

Common error patterns and anti-patterns

Log aggregation queries (Elasticsearch, Splunk)

Anomaly detection in log streams

Approach

Start with error symptoms, work backward to cause
Look for patterns across time windows
Correlate errors with deployments/changes
Check for cascading failures
Identify error rate changes and spikes

Output

Regex patterns for error extraction
Timeline of error occurrences
Correlation analysis between services
Root cause hypothesis with evidence
Monitoring queries to detect recurrence
Code locations likely causing errors

Focus on actionable findings. Include both immediate fixes and prevention strategies.

Limitations

Use this skill only when the task clearly matches the scope described above.
Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

02

Do not use this skill when

Software Developers

Session Logs

Search and analyze your own session logs (older/parent conversations) using jq.

OpenClaw Test Heap Leaks

Investigate `pnpm test` memory growth, Vitest worker OOMs, and suspicious RSS increases in OpenClaw using the `scripts/test-parallel.mjs` heap snapshot tooling. Use when Codex needs to reproduce test-lane memory growth, collect repeated `.heapsnapshot` files, compare snapshots from the same worker PID, triage likely transformed-module retention versus likely runtime leaks, and fix or reduce the impact by patching cleanup logic or isolating hotspot tests.

Node Connect

Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale, or plugins.entries.device-pair.config.publicUrl.

Openclaw Qa Testing

Run, watch, debug, and extend OpenClaw QA testing with qa-lab and qa-channel. Use when Codex needs to execute the repo-backed QA suite, inspect live QA artifacts, debug failing scenarios, add new QA scenarios, or explain the OpenClaw QA workflow. Prefer the live OpenAI lane with regular openai/gpt-5.4 in fast mode; do not use gpt-5.4-pro or gpt-5.4-mini unless the user explicitly overrides that policy.

Openclaw Secret Scanning Maintainer

Maintainer-only workflow for handling GitHub Secret Scanning alerts on OpenClaw. Use when Codex needs to triage, redact, clean up, and resolve secret leakage found in issue comments, issue bodies, PR comments, or other GitHub content.

Flags

Use when you need to check feature flag states, compare channels, or debug why a feature behaves differently across release channels.

Software Developers