القائمة
Analyzes LLM provider error messages to determine retry strategy, failover candidates, and root cause. Supports multiple providers (OpenAI, Anthropic, Google, local models).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | provider-error-analyzer |
| description | Analyzes LLM provider error messages to determine retry strategy, failover candidates, and root cause. Supports multiple providers (OpenAI, Anthropic, Google, local models). |
| version | 1 |
| metadata | {"category":"reliability","author":"auto-workflow","evolution-stats":{"total-experiments":870}} |
| level | atom |
Different LLM providers return different error formats. This skill maps error messages to categories and determines the best recovery strategy.
Pattern: usage limit exceeded, rate_limit_error, too many requests
Providers:
RateLimitError, 429 Too Many Requestsoverloaded_error, 529 OverloadedResourceExhausted, 429Strategy:
Pattern: insufficient_quota, allocated quota exceeded, billing_hard_limit_reached, hard limit reached, quota exceeded
Providers:
insufficient_quota (1004)quota_exceeded (429)QuotaExceeded (429)Strategy:
Pattern: invalid_api_key, unauthorized, token is unusable, Authentication failed
Providers:
invalid_api_key (401)authentication_error (401)Unauthenticated (401)Strategy:
Pattern: content_filter, invalid_request_error, Bad request
Strategy:
Pattern: server_error, bad_gateway, service_unavailable, overloaded, cluster overloaded
Providers:
server_error (500)overloaded_error (529)InternalServerError (500)Strategy:
Pattern: timeout, Request timeout, Gateway timeout
Strategy:
Pattern: Connection refused, Network error, DNS resolution failed
Strategy:
Primary: kimi (cost-effective)
Fallback 1: openai (reliable)
Fallback 2: anthropic (high quality)
Fallback 3: google (backup)
Local: ollama/lmstudio (always available)
scripts/classify_error.py - Classify error message into categoryscripts/recommend_strategy.py - Recommend retry/failover strategyscripts/update_patterns.py - Learn new error patterns from logs;; Classify error
(let ((error-msg "usage limit exceeded (2056)"))
(provider-error-classify error-msg))
;; => (:category 'rate-limit :retryable t :backoff 2)
;; Get failover candidate
(provider-error-failover-candidate 'kimi)
;; => (:provider 'openai :model 'gpt-4)
When encountering new error formats:
references/error-patterns.mdscripts/update_patterns.py🔄 update provider-error patternsBased on analysis of experiment errors.
| Pattern | Category | Action | Frequency | Regex |
|---|
Transforms research paper analysis from extraction to narrative storytelling. Uses 7-beat narrative spine (protagonist/dilemma/old-path/turning-point/solution/ending/core) to make papers understandable to non-experts. Includes speed-read card, PhD advisor review, and real-world testing. Use when researcher encounters a research paper and needs to extract deep understanding, not just surface facts. Triggers on "paper", "research paper", "analyze paper", "tell me about this paper", "讲论文", "读论文".
Workflow chain: researcher → paper-storytelling. When researcher encounters a research paper, automatically invoke paper-storytelling to transform extraction into narrative understanding. Use when user says "research paper", "analyze this paper", "tell me about this paper", or when researcher detects arxiv/PDF links.
Prompt template for external research specialist subagent. Auto-evolves based on experiment outcomes.
Inspect and operate OV5 (Ouroboros V5) through the live Emacs daemon. Use when checking auto-workflow status, starting guarded runs, reviewing experiment results, or querying researcher and evolution state.
Clojure REPL client (nREPL-based, Babashka). Use for evaluating Clojure code, loading Clojure files, fixing unbalanced brackets, and interactive nREPL work. Not the Elisp daemon-repl.
Daemon REPL for Elisp — evaluate Elisp code in a running Emacs daemon via emacsclient, validate brackets before save, auto-evaluate .el files on change. Use when you need to run Elisp from outside Emacs, check daemon status, or validate Elisp syntax.