Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From aeon-flux
Activates when errors occur during execution. Provides self-correction patterns for immediate error fixing without verbose explanations or apologies.
npx claudepluginhub theglitchking/aeon-flux --plugin aeon-fluxHow this skill is triggered — by the user, by Claude, or both
Slash command
/aeon-flux:error-recoveryThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
An error has occurred. Apply these recovery patterns.
Use when repeated fix attempts fail, the agent appears stuck in a loop, or complexity is increasing without progress
Guides structured recovery from errors and failures by assessing, logging root cause, and applying safe fixes with rollback plans. Prevents cascading mistakes via forbidden patterns and escalation rules.
Quickly analyzes errors from logs or args, applies minimal fixes with Edit/Write tools, verifies via tests or re-runs, and reports results concisely without explanation.
Share bugs, ideas, or general feedback.
An error has occurred. Apply these recovery patterns.
# Try with sudo if appropriate
sudo command
# Or fix permissions
chmod +x script.sh
# Check if installed
which command || apt-get install package
# Or use full path
/usr/bin/command
# Verify path
ls -la parent/directory/
# Create if needed
mkdir -p path/to/directory
touch path/to/file
# Check syntax first
bash -n script.sh
python -m py_compile script.py
# Then fix and retry
# Check connectivity
ping -c 1 host
# Retry with timeout
timeout 30 command
# Or use alternative endpoint
# Merge conflicts: resolve then
git add . && git commit
# Detached HEAD
git checkout main
# Uncommitted changes blocking
git stash && git pull && git stash pop
[silent fix attempt]
[if works: continue task]
[if fails: try alternative]
[only explain if asked or stuck after 3 attempts]
After 3 failed fix attempts on the same error:
<!-- ATTENTION --> tag<!-- ATTENTION -->
Blocker: Cannot connect to database after 3 attempts
Tried: localhost:5432, docker network, environment variables
Need: Database connection details or alternative approach
<!-- /ATTENTION -->