Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Search the community-driven Agent Failure Registry for known agent errors, solutions, and lessons to debug issues or submit new failure post-mortems.
Search the community-driven Agent Failure Registry for known agent errors, solutions, and lessons to debug issues or submit new failure post-mortems.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Search and learn from the Agent Failure Registry โ a community-driven database of agent failures, solutions, and lessons learned. When you hit a wall, check if someone else already climbed it.
Search for similar failures: ./scripts/search-registry.sh --category api_failure ./scripts/search-registry.sh --keyword "puppeteer" ./scripts/search-registry.sh --tag twitter --tag auth Search everything: ./scripts/search-registry.sh --all
When you encounter an error, search the registry before reinventing the wheel: By Category: api_failure, auth_expiry, rate_limit, silent_failure, data_corruption, timeout, logic_error, dependency_break, permission_denied, other By Keywords: Tool names, error messages, symptoms By Tags: Platform, service, technology The registry contains post-mortems from examples/ (curated) and submissions/ (community). Search Results Include: Summary of what went wrong Root cause analysis Fix that worked Prevention strategies Lessons learned
When you solve a new failure, help the community: Document the failure following the schema Submit via GitHub PR (script can help generate template) Include context โ what you tried, what worked, what didn't Required Fields: Title, category, tags Summary, root_cause, fix Prevention steps, lessons learned Confidence level (1-5)
Periodically browse recent submissions to learn from others' failures before you hit them yourself.
The search-registry.sh script handles all the heavy lifting: Arguments: --category CATEGORY โ Search specific failure category --tag TAG โ Search by tag (repeatable) --keyword KEYWORD โ Free-text search in all fields --all โ Show all entries (for browsing) Examples: # Find authentication issues ./scripts/search-registry.sh --category auth_expiry # Find Twitter-related failures ./scripts/search-registry.sh --tag twitter # Find Puppeteer issues ./scripts/search-registry.sh --keyword "puppeteer" # Multiple criteria ./scripts/search-registry.sh --category api_failure --tag openai # Browse everything ./scripts/search-registry.sh --all
The Agent Failure Registry contains: examples/ โ Curated failure post-mortems submissions/ โ Community submissions template.yaml โ Template for new submissions schema/postmortem.yaml โ Schema validation
api_failure โ API errors, timeouts, invalid responses auth_expiry โ Authentication/token expiration issues rate_limit โ Rate limiting, quota exceeded silent_failure โ No error thrown, but wrong behavior data_corruption โ Data integrity, parsing failures timeout โ Operation timeouts, hanging processes logic_error โ Flawed reasoning, incorrect assumptions dependency_break โ External service/lib failures permission_denied โ Access control, file permissions other โ Miscellaneous failures
Before Searching: Extract key error messages or symptoms Identify the failing component (API, tool, process) Note the context (what were you trying to do?) When Submitting: Be specific about the fix that worked Include what you tried that didn't work Rate your confidence in the solution (1-5) Tag with relevant technologies/services For Prevention: Review failures in your domain periodically Update your error handling based on lessons learned Share edge cases and gotchas with the community
Registry cloned to /tmp/agent-failure-registry Uses PyYAML for parsing (with grep fallback) Searches both examples/ and submissions/ Output formatted for readability Handles multiple search criteria Remember: Every failure is a lesson. Document it, share it, learn from it.
Workflow acceleration for inboxes, docs, calendars, planning, and execution loops.
Largest current source with strong distribution and engagement signals.