Use when erlang's concurrency model including lightweight processes, message passing, process links and monitors, error handling patterns, selective receive, and building…
Score 70/100
Use when erlang distributed systems including node connectivity, distributed processes, global name registration, distributed supervision, network partitions, and building…
Score 70/100
Erlang-style message passing via /tmp file system. Use when simulating actor model with actual message synchronization between processes.
Score 70/100
Use when oTP behaviors including gen_server for stateful processes, gen_statem for state machines, supervisors for fault tolerance, gen_event for event handling, and building…
Score 70/100
Extract and analyze data from construction ERP systems. Pull project data for analytics, reporting, and integration.
Score 70/100
Crea scripts de migració per a mòduls OpenERP quan es modifiquen models o fitxers XML. Automatitza: generar estructura, plantilla, executar migració.
Score 70/100
Complete guide for ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.
Score 70/100
Intelligent agent for interpreting vague ERPNext development requests and producing concrete technical specifications.
Score 70/100
Error handling patterns for ERPNext/Frappe API development (v14/v15/v16). Covers whitelisted method errors, REST API errors, client-side handling, external integrations, and…
Score 70/100
Error handling patterns for ERPNext Document Controllers. Use when implementing try/except, validation errors, permission errors, and transaction management.
Score 70/100
Error handling patterns for ERPNext/Frappe database operations. Use when handling DoesNotExistError, DuplicateEntryError, transaction failures, and query errors.
Score 70/100
Error handling patterns for ERPNext/Frappe permissions and access control. Use when handling PermissionError, has_permission failures, role issues, and document access problems.
Score 70/100
Implementation workflows and decision trees for ERPNext Client Scripts. Use when determining HOW to implement client-side features: form validations, dynamic UI, server…
Score 70/100
Implementation workflows and decision trees for Frappe Document Controllers. Use when determining HOW to implement server-side DocType logic: lifecycle hooks, validation patterns,…
Score 70/100
Implementation workflows and decision trees for Frappe hooks.py configuration. Use when determining HOW to implement doc_events, scheduler_events, override hooks, permission…
Score 70/100
Implementation workflows and decision trees for Jinja templates in ERPNext/Frappe. Use when determining HOW to implement Print Formats, Email Templates, Portal Pages, or custom…
Score 70/100
Implementation workflows for Frappe scheduled tasks and background jobs (v14/v15/v16). Covers hooks.py scheduler_events, frappe.enqueue, queue selection, job deduplication, and…
Score 70/100
Implementation workflows and decision trees for ERPNext Server Scripts. Use when determining HOW to implement server-side features: document validation, automated calculations,…
Score 70/100
Implementation workflows and decision trees for Frappe Whitelisted Methods (REST APIs). Use when determining HOW to implement API endpoints: public vs authenticated, permission…
Score 70/100
Complete guide for Frappe/ERPNext permission system - roles, user permissions, perm levels, data masking, and permission hooks
Score 70/100
Deterministic syntax for building Frappe custom apps including app structure, pyproject.toml, modules, patches and fixtures
Score 70/100
Deterministic syntax for Frappe hooks.py configuration. Use when Claude needs to configure app events, scheduler tasks, document events, fixtures, boot session, jenv…
Score 70/100
Deterministic Jinja template syntax for ERPNext/Frappe Print Formats, Email Templates, and Portal Pages
Score 70/100
Scheduler and background jobs syntax for Frappe/ERPNext v14/v15/v16. Use for scheduler_events in hooks.py, frappe.enqueue() for async jobs, queue configuration, job deduplication,…
Score 70/100
Create error boundaries, error handling, and fallback UIs for React applications. Use when implementing error handling, creating fallback components, or setting up error reporting.
Score 70/100
設計一致的錯誤碼，遵循 PREFIX_CATEGORY_NUMBER 格式。 使用時機：定義錯誤碼、建立錯誤處理、設計 API。 關鍵字：error code, error handling, error format, API errors, 錯誤碼, 錯誤處理。
Score 70/100
Expert error coordinator specializing in distributed error handling, failure recovery, and system resilience.
Score 70/100
Analyzes errors, searches past solutions in memory, provides immediate fixes with code examples, and saves solutions for future reference.
Score 70/100
Search logs and codebases for error patterns, stack traces, and anomalies. Correlates errors across systems and identifies root causes.
Score 70/100
Advanced error analysis and pattern detection specialist for identifying, analyzing, and preventing software errors
Score 70/100
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions.
Score 70/100
Proactively reviews error handling patterns and suggests improvements using Result types, proper error propagation, and idiomatic patterns.
Score 70/100
Error Handler Middleware - Auto-activating skill for Backend Development. Triggers on: error handler middleware, error handler middleware Part of the Backend Development skill…
Score 70/100
Use when implementing structured error handling in backend or frontend code. Triggers for: try-catch patterns, custom exception classes, global error handlers, error logging,…
Score 70/100
Production-ready API error handling for Next.js with standardized error codes, request tracking, user-friendly messages, and automatic error wrapping.
Score 70/100
Audits Go code for error handling best practices - proper wrapping with %w, preserved context, meaningful messages, no error swallowing.
Score 70/100
Find and fix unsafe error handling in Leavn - try! force unwraps, empty catch blocks, silent try? failures
Score 70/100
Evaluates if error handling is sufficient for new code - checks try-catch coverage, logging, user messages, retry logic. Focuses on external calls and user-facing code.
Score 70/100
Use when designing or implementing a cross-cutting Apex error handling framework: custom exception hierarchies, rollback-safe logging via Platform Events, BatchApexErrorEvent…
Score 70/100
Auto-invoke when reviewing try/catch blocks, API error responses, async operations, or user feedback patterns. Enforces graceful degradation and meaningful error messages.
Score 70/100
Verify errors are handled gracefully with meaningful user feedback. Issues result in WARNINGS.
Score 70/100
Master error handling patterns across languages including exceptions, Result types, error propagation, and graceful degradation to build resilient applications.
Score 70/100
Design error states and recovery workflows that guide users to resolution. Learn context-aware error messages, graceful degradation, and recovery patterns.
Score 70/100
Review test cases for OAuth/OIDC error handling. Covers authorization endpoint errors, token endpoint errors, error response formats, HTTP status codes, and all error codes per…
Score 70/100
**AUTO-TRIGGER:** Invoked by yolo1 skill after every commit to analyze session errors.
Score 70/100
Error Mapping Helper - Auto-activating skill for API Integration. Triggers on: error mapping helper, error mapping helper Part of the API Integration skill category.
Score 70/100
Use when: making a mistake, breaking build/tests, realizing wrong approach, misunderstanding requirements, using wrong patterns, forgetting conventions, receiving correction from…
Score 70/100
Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.
Score 70/100
Create custom 404 and 500 error pages with brand styling. Use at project end before release. Triggers on "404", "error pages", "not found", "500 error".
Score 70/100
Use when an operation fails, an error occurs, or a warning needs to be communicated to the user
Score 70/100
Strategies for handling subagent failures with retry logic and escalation patterns.
Score 70/100
Engineer resilient UI systems with layered error boundaries, retries, and fallback orchestration.
Score 70/100
Error recovery and failure handling patterns for distributed systems including rollback strategies, circuit breakers, retry logic with exponential backoff, graceful degradation,…
Score 70/100
Systematic error diagnosis and resolution using first-principle analysis. Use when encountering any error message, stack trace, or unexpected behavior.
Score 70/100
Production-safe error handling that logs full details server-side while exposing only generic, safe messages to users.
Score 70/100
Standard error response taxonomy and envelope for services, including error codes, categories, retryability, correlation IDs, safe messaging, and validation error details
Score 70/100
[STATUS: confirmed] [CONFIDENCE: high] [VALIDATED: 2026-04-18] После исправления бага или инцидента — структурирует урок в переиспользуемый паттерн с причиной, fix-ом, и kill…
Score 70/100
Implement error tracking with Sentry for automatic exception monitoring, release tracking, and performance issues.
Score 70/100
Query ESC (European Society of Cardiology) Guidelines by automatically locating the relevant PDF from the TOC and extracting cited answers.
Score 70/100
Use when stuck in circles and want to hand off to another agent (Codex CLI) with full context
Score 70/100