Skill UI

Guide for building high-quality MCP servers that let LLMs interact with external APIs via workflow-focused tools, SDKs, validation, and error handling in Python or TypeScript.

This guide provides a production-ready, layered architecture pattern for integrating Mistral AI into TypeScript/Node.js projects. It implements best practices including singleton client management, Zod-validated configuration, custom error handling, caching mechanisms, and robust service layer design (e.g., RAG pipelines). Use this when setting up new Mistral AI applications or needing standardized, reliable project structure.

This guide provides production-ready patterns for integrating the Mistral AI SDK in both TypeScript and Python. It covers essential best practices such as singleton client management, handling structured JSON output, implementing streaming responses, concurrent asynchronous processing, and robust error handling with exponential backoff. Use this when establishing team coding standards or refactoring Mistral API usage.

Catalogs proven n8n workflow architectural patterns for webhook handling, APIs, database syncing, AI agents, and scheduled tasks, helping teams pick structures, plan nodes, and handle triggers, data paths, and error strategies during workflow design and troubleshooting.

Guides you through diagnosing Next.js getServerSideProps, getStaticProps, and API route failures by checking terminal logs, adding explicit try-catch handling, and reviewing hosting logs or common causes like env vars, DB, or serialization issues.

This comprehensive guide helps developers make critical architectural decisions in modern Node.js development. It covers framework selection (Fastify, Hono, Express), implementing layered architecture, mastering async patterns, robust error handling, and essential security protocols. The focus is on teaching architectural thinking and problem-solving skills, ensuring the development of scalable, high-performance, and maintainable backend APIs.

This guide provides comprehensive error handling and debugging steps for the OpenEvidence API. It covers common failure points—including authentication issues (401, 403), query validation errors (422), rate limiting (429), and service timeouts (408). Users can learn how to diagnose the root cause of connection failures and refine their clinical queries to maximize data retrieval accuracy.

This SDK provides comprehensive, production-ready patterns for interacting with the OpenEvidence clinical evidence API. It enables developers to efficiently query medical literature, retrieve clinical guidelines, and generate evidence-based recommendations. Key features include a singleton client for consistent authentication, robust error wrappers (handling retries, invalid keys), and structured data models designed to ensure audit compliance and detailed citation provenance in complex healthcare applications.

This comprehensive guide helps users diagnose and fix common OpenRouter API errors, including authentication failures (401), rate limiting (429), and bad requests (400). It provides a complete reference table, detailed root causes, and executable code examples in Bash and Python to ensure stable API integration and robust error handling.

A comprehensive guide on handling API rate limits and throttling errors (429) when building high-throughput systems, particularly for LLM APIs like OpenRouter. This skill covers best practices, including using exponential backoff, implementing custom client-side rate limiters (Token Bucket), and managing concurrent requests for stable, reliable performance.

This guide provides a comprehensive reference for diagnosing and fixing common errors and exceptions encountered when interacting with the Perplexity Sonar API. Use this when troubleshooting API integration issues, handling specific HTTP status codes (like 401, 429, 402), or debugging failed requests. It covers best practices for rate limiting, key validation, and implementing robust error handling logic.

This comprehensive runbook provides step-by-step procedures for rapidly responding to Perplexity API outages and service degradations. It covers initial triage (checking models, auth, DNS), handling common errors (401, 429, 500/503), implementing fallbacks, and structured post-incident activities, including evidence collection and postmortem documentation.